I have recently installed Eggdrop from ports on a FreeBSD 5.3-STABLE system. I created the config file and have put in all settings for the bot to use my external ip as i am behind a router using NAT. When i try and dcc chat the bot i get the following errors:
This tells me that it is using the correct nat information but i still can't get it to work. /ctcp bot chat will not work either - i can telnet to the bot though but i really need to be able to use dcc chat and i have gone through the readme's and how-to's and i believe i am doing everything correct. Any help would be much appreciated.
this topic has been discussed many times as of late
search the forums for "nat-ip" and "reserved-portrange" and you'll find multiple articles on the subject, basically saying the same (or at least I repeat that DCC stuff again & again, it's really simple and comes down to setting these two variables correctly, as well as your firewall/NAT)
I realise this has been discussed that is why i said i had done all the relevant things in trying to get this to work.
I have set both these 2 variables correctly as shown below:
set nat-ip "144.132.2.189"
set reserved-portrange 60000:65000
On my router running NAT i have port forwarded those ports above to the ip which the eggdrop is running off and i still get this problem. I don't know what else to do?
anyhow, try acceping outside DCC CHAT request with some IRC client running on the bot's machine; if you are successful with that, it's a bot problem; if not, most likely a firewall problem
I found out the problem. KVIRC was trying to initiate outside dcc connections but because the bot was on the local lan it would try and lookup my external ip address, i fixed this by taking out the external ip address i configured, now i have a problem that i can't dcc chat anyone external to my lan though, ahh well that is what /msg is for
Isn't there a DMZ setting with your router? A friend of mine with a router couldn't DCC anything for ages until they stumbled across setting the DMZ and now they DCC everything.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM