Justin Hammond wrote:
Hi all
We have a problem on one of our servers. Its running:
Linux 2.4.17 on a Sparc Box with IPtables 1.2.4
The Kernel support for IPtables was compiled into the kernel, not as
loadable modules, and now we have some problems.
We recently setup a IRC server for a customer, and they came back and
told us that DCC sending was not working for any client connected to
this IRC server. A quick check of the logs revealed:
Forged DCC command from 218.103.157.103: 1.154.254.169:0
Forged DCC command from 218.103.157.103: 1.154.254.169:0
Forged DCC command from 218.103.157.103: 1.154.254.169:0
Forged DCC command from 218.103.157.103: 1.154.254.169:0
Throughout the entire kernel log.
(I believe the problem has been fixed in later releases of iptables, so
I'm not after a fix)
Now here is my problem. The Server is in Sydney, Australia, and I'm in
Singapore, around 8000Miles away, so doing a remote kernel compile and
reboot to remove the contrack_irc module is not something that I fancy.
I'm wondering if there is a Rule or way that I can disable the contrack
module from operating?
Thanks :)
Justin
Unfortunately, I believe that once a module is compiled into the kernel
it's present, end of discussion. And besides. thats not quite what you
want is it? removing ip_conntrack_irc would kill ALL irc abilities, not
just DCC. After all, doens't IRC operate on multiple ports, similiar to FTP?
