I have setup my eggdrop on a unix redhat 9 machine with APF firewall. My firewall blocks incoming and outgoing ports. I have setup everything correctly in the config file of the bot, but apparently it is not possible for the bot to establish a DCC chat connection without blocking the outgoing ports scanning of the firewall.
I have specified the reserved portrange, opened the ports in the firewall, but this didn't help, as I suppose the reserved portrange is only for file transfers.
So, isn't there a way to specify a limited amount of outgoing ports the bot uses to connect to the user? I can't turn outgoing ports blocking off in the firewall. I have been asking this question in all eggdrop help channels on IRC, and nobody seemed able to help.
# You need to un-comment this line and change the port number in order to open
# the listen port. You should not keep this set to 3333.
listen 3333 all
this should allow you to /dcc chat <botnick> or /ctcp <botnick> chat depending on how stuborn your firewall is
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
because that will be an incoming connection rather than an outgoing?
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
If you want to change the outgoing port, you must make the bot to connect to one that is reserved.
in exp., if the bot may make a conntion to 21000-21020 then set your mIRC dcc port ranges to these values, so you client will give your bot a port from this range when doing a /dcc chat . As DooM said, another work around would be to use the ctcp command, so the connection initiation is done from your irc client using one of the in .conf reserved dcc ports.