I'm running a 450 Mhz IBM thinkpad with Slack 10, 2.4.26 kernel, iptables 1.2.10 for firwalling and I for the life of me can't figure out how to get it to NAT DCC traffic from my internal computers. I've read quite a bit on the IP-Masquerading-HOWTO and it only says that ip_nat_irc.o will handle DCC traffic for me.

Now I did read a bit further on and noticed it saying that I should be using ip_masq_irc.o. I could be assuming incorrectly on this, but I think these are the same files, only ip_nat_irc.o is a bit stricter.

I know the DCC packets are being sent and recieved because I've monitored my network traffic with iptraf 2.7.0. But what's happenning to them at the router level is a mystery at this point. Well I can pretty much guess what's happenning, but a DROPped packet isn't the desired outcome.

I read on the internet in another forum a long time ago in a galaxy far, far away and I saw that there was need to update/patch the ip_nat_irc.c, but it was a 4-year-old posting. So I would chance to say that Slack has, since then, updated it's modules and packages as Slack 10 was just recently released. Just an assumption though.

Basically to save myself the headache of tracking down this patch and finding out that it was never needed in the first place, could someone please advise me if I need to add a specific rule to my IPTABLEs to get DCC traffic to route to my internal network.

Just for information sake, I have turned on IPPORTFW(arding) and forwarded every port to one of my internal machines and it still does not allow DCC traffic through. When I try a dcc chat from one IRC client to another, on the same computer, it just tells me "Unable to connect". I've had a friend of mine test this out from the internet and to no avail have I got it to work.

Also all my other routing is working. My router works just fine except for the DCC thing. Any help would be greatly appreciated.

zr0