Tried just about everything i can think of, am totally at a loss.
Read every faq i could get my hands on, and have scoured this message board. Any suggestions would be greatly appreciated.
Thanks for the reply, it doesn't work for anyone. I've tested it with a good dozen+ people thusfar, and they all are unable to recieve from it. Definately not a firewall issue
mabus wrote:Thanks for the reply, it doesn't work for anyone. I've tested it with a good dozen+ people thusfar, and they all are unable to recieve from it. Definately not a firewall issue
I think demond was refering to a firewall on the shell.
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born
what makes you think it's not your firewall which prevents people receiving files from you?
if they all can't receive a file from you via DCC, that means it's you that are unable to serve them - most likely because your app (bot or IRC client) can't open a random listening port for them to connect to (which is required by DCC protocol) - and the usual suspect is your firewall
Ah ok i misunderstood. Well the reason is that it's running off a commercial shell, and they are assuring me that the problem isn't with them. So it's definately a problem with the eggdrop itself somewhere. Any other suggestions?
that log doesn't show anything relevant.. where's the timeout?
anyway; you need to do 2 things:
ensure that you can open a listening port; talk to your shell admin about that - he/she has to allocate such port(s) for you in the system firewall's configuration (if there is a firewall)
include that port(s) in your reserved-portrange (see eggdrop.conf)
then you should be able to initiate DCC from your shell