Eggdrop still uses wrong port ranges

2002-06-19T14:49:00-04:00

reserved portrange applies to dynamically assigned listen ports (ie, ports that eggdrop opens to listen to external connections, as when initiating a dcc send). the second line of your netstat refers to an outgoing connection. Outgoing connection ports are assigned by the operating system. By default most os's assign 1024-5000. Most firewalls should allow this behaviour if proper stateful rulesets have been made.

Statistics: Posted by Petersen — Wed Jun 19, 2002 2:49 pm

Eggdrop still uses wrong port ranges

2002-06-19T12:17:00-04:00

Hi.
Even if I've set up the conf to use some reserved portrange (I'm running a firewall which allows portrange 46600-46730 ), it keeps trying connecting to lower ports (see below: 3985, 4004 and so on). Therefore it can't link/connect
I'm running eggdrop 1.6.8, since dcc-portrange seems to be removed in eggdrops >1.6.7 , I've tried also with 1.6.6 but it doesn't work as well.

=== from my conf ===
listen 46621 bots
listen 46641 users
#set nat-ip "127.0.0.1"
set reserved-portrange 46700-46730
set dcc-portrange 46700-46730
===

from "netstat -tp":

===
tcp 3 0 myhost:46621 myhost:3985 ESTABLISHED 4864/eggdrop-1.6.8
tcp 0 1 myhost:4004 otherhost:50505 SYN_SENT 4864/eggdrop-1.6.8
===

Thanks in advange.

Statistics: Posted by Guest — Wed Jun 19, 2002 12:17 pm

egghelp/eggheads community

Eggdrop still uses wrong port ranges

Eggdrop still uses wrong port ranges