egghelp/eggheads community

Eggdrop, port forwarding, and DCC

2004-05-28T00:10:14-04:00

also make sure you enabled the reserved-portrange setting in the config file

set reserved-portrange 2010:2020

are you able to do ctcp chats to the bot ?

Statistics: Posted by greenbear — Fri May 28, 2004 12:10 am

Eggdrop, port forwarding, and DCC

2004-05-24T10:24:37-04:00

What is the exact error?

I'm going to assume that the bot conf isn't set with the
#set nat-ip "127.0.0.1"

When the external user tries to dcc chat your bot, the dcc window will prolly load up with your internal ip, therefor the external user will be out of luck.

Statistics: Posted by j0n — Mon May 24, 2004 10:24 am

Eggdrop, port forwarding, and DCC

2004-05-21T14:42:11-04:00

Okay, I seem to be having the opposite problem of other users here.

First box running Eggdrop, behind a router, listening on 3334, it plus DCC ports of 2010 - 2020 are forwarded from the outside world to its internal IP addy

Second box behind a router running mIRC, DCC port range set to 2070-2080. the outside world also forwards those ports to the internal IP addy. mIRC is configured to report the outside IP when connecting.

Second box sends and recieves DCCs to/from the outside world fine. Second box can initiate DCC chat with First box without a problem.

Everyone in the outside world however, cannot DCC chat the bot on the First machine. Any idea on what gives?

Statistics: Posted by Wildfire — Fri May 21, 2004 2:42 pm