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?
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
Eggdrop, port forwarding, and DCC
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.
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.
* j0n!~khronus@wicked.ca *