irc DCC sends and routers

Message

Lockup · Post by **Lockup** » Sat Feb 22, 2003 11:53 pm

i have a D-Link DI-614+ router, and my linux box is connected to the internet through it, and im getting this weird problem...
i can receive files through DCC sends on irc, but i cant SEND files(which seems pretty weird, as the router is supposed to allow everything out)
i looked a bit on google for info about that, and on dlink.com too and only found vague allusions to some port forwarding(anyways, wasnt really able to make something intelligent out of it:P
im guessing its some rule id have to add, any suggestions?

krt · Post by **krt** » Sun Feb 23, 2003 7:27 am

There shouldn't be anything that you have to do with your firewall .. its probably your irc client. When you preform a dcc send, the irc client is using your boxes IP address. The receipient of the DCC packet will see your private IP address and not the routeable IP address from your firewalls public side. You can alleviate this problem in modern IRC clients by setting your DCC IP address to your public address. I know that xchat has support for this.

You can verify that this behavior is happening by asking the receipient of your DCC what IP address their seeing your send come from. You'll probably see that its coming from your private address.

puddpunk · Post by **puddpunk** » Sun Feb 23, 2003 9:46 am

No, It's not anything to do with your hardware, It's the way EVERY IRC client has DCC implimented.

When someone wants to send a file, they send a CTCP (Client to Client Protocol) message to the reciever (with information such as IP and port, then the reciever opens a connection to the sender. Which can't happen since you are behind a firewall.

Have a look at KVIrc, It has a new feature called RDCC (Reverse DCC) and it's the only way short of hacking my firewall to send files.

Lockup · Post by **Lockup** » Sun Feb 23, 2003 2:30 pm

and yes...just tested with a friend and my ip was at 192.168.0.100 for him

thanks for the tip:) ill look into irssi to see if theres a var i can set for that...worst case ill just switch client

Lockup · Post by **Lockup** » Sun Feb 23, 2003 4:07 pm

(11:04) [dcc]
(11:04) dcc_autorename = OFF
(11:04) dcc_autoresume = ON
(11:04) dcc_timeout = 300
(11:04) dcc_autoget = OFF
(11:04) dcc_upload_path = ~
(11:04) dcc_autoget_masks =
(11:04) dcc_autoget_max_size = 0
(11:04) dcc_send_replace_space_with_underscore = OFF
(11:04) dcc_own_ip = [xx.xx.xx.xxx]
(11:04) dcc_download_path = ~
(11:04) dcc_file_create_mode = 644
(11:04) dcc_port = 0
(11:04) dcc_autochat_masks =
(11:04) dcc_mirc_ctcp = OFF
(11:04) dcc_autoaccept_lowports = OFF

thats the list of set-able dcc stuff in irssi.... as you can see, i set dcc_own_ip to my ip (censored)...it still times out though, any ideas? theres no logs on the router so i cant check if its a prob with that
port 0 simply means a random port for this client btw

Tuna · Post by **Tuna** » Mon Feb 24, 2003 12:15 pm

iptables/kernel related.

you need ip_conntrack_irc and ip_nat_irc either as a module or compiled in the kernel. if it is a module, load it of course.

no special rules are needed for iptables as far as i know, connections should beeing rejected of course.

as for irssi - i set my dcc_own_ip to my local maschine ip (192.168.0.x) and it works. i dont know if that is even neccesary.
as for irssi part2: while testing, dont try to send files with spaces in filenames as for me this was heavily broken and thus doesnt work. also dont use dcc_send_replace_space_with_underscore, as it seems to be broken too :/