I have 2 eggdrops running.
They both seem to be grabbing ports and releasing them, then they increase port number by 2 and continue: approx 100 ports each per minute.
im not sure, but it seems to be in the 2000-4000 port # range. It's actually quit abusive to the firewall. I figure it has something to do with DCC security; But i was hoping for the official explanation, as maybe i have a problem.
Thx Guys,
Smokey.
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.
PORTS ! Why are my bots racing thru them ??
Hmmm ... what version of eggy are you running for starters?
by defaul eggy uses ports for:
Other than the above, are you running any kind of scripts/modules that do their own port stuff?
by defaul eggy uses ports for:
- Normal Chat
Partyline Chat
Bot messages
Userfile transfers
Normal File Transfers
DNS
Other than the above, are you running any kind of scripts/modules that do their own port stuff?
-
SSmokey
Its the Ident Checking feature on incoming connections!
Hiya its been awhile, but i tracked down what is going on.
Please tell me if its possible to lock the IdentD CLIENT (not server, client) onto a specific port.
This is whats happening:
As soon as bot is loaded, it races thru the ports from 1200-8000, without establishing connections. botlink port set to 35000. userlink port set to 30000.
I discovered that the ports in the 1200-8000 range are being used by the bot to check the IdentD of an incoming connection, regardless of whether the receiving a connection or not. it will continue going extremely fast (20 ports per sec) until it receives an incoming link, at which point it will stay on that port momentarily, then seems to continue from there, continuing to ferociously eat ports up. It does release port immediately, but 40 botsare being run on that box, and it is actually hard on the firewall.
All testing was done using 1 fresh bot. no other bots running. to prevent conflicts.
have tried 1.6.10, 1.6.12, 1.6.13(currently using)
This is DEFINATELY IDENTD related, im pretty sure.
thx,
appreciate time
SMOKEY
Please tell me if its possible to lock the IdentD CLIENT (not server, client) onto a specific port.
This is whats happening:
As soon as bot is loaded, it races thru the ports from 1200-8000, without establishing connections. botlink port set to 35000. userlink port set to 30000.
I discovered that the ports in the 1200-8000 range are being used by the bot to check the IdentD of an incoming connection, regardless of whether the receiving a connection or not. it will continue going extremely fast (20 ports per sec) until it receives an incoming link, at which point it will stay on that port momentarily, then seems to continue from there, continuing to ferociously eat ports up. It does release port immediately, but 40 botsare being run on that box, and it is actually hard on the firewall.
All testing was done using 1 fresh bot. no other bots running. to prevent conflicts.
have tried 1.6.10, 1.6.12, 1.6.13(currently using)
This is DEFINATELY IDENTD related, im pretty sure.
thx,
appreciate time
SMOKEY
-
SSmokey
Incoming Connection's Identd Check
Yes, It is definately the eggdrop's internal little client that verifies the identd of an incoming connection. Its going haywire.
** IS THERE A WAY to specify which port eggdrop will use to connect to a remote identd (113) port ?
I'm looking for a .conf setting i could use like: "set identd-check-port 3000"
Does it exist? Am i the only one who's seen this? Its happening on every bot we have.
** IS THERE A WAY to specify which port eggdrop will use to connect to a remote identd (113) port ?
I'm looking for a .conf setting i could use like: "set identd-check-port 3000"
Does it exist? Am i the only one who's seen this? Its happening on every bot we have.
-
SSmokey
Still No Solution to My port Problems -Anyone else see this?
PPSlim: when u said u didnt have the tools to check out the same thing, I realized, that I have only been able to see this activity on the WINDROPS, as i myself dont have a tool to watch the linux ports closely enough, but, you use netstat @ 2 second intervals and compare them, you will notice one of the ports has been released, and another grabbed with a new time.
Do that a few times, and you'll see that one of the ports has 'moved' to a slightly higher number, everytime u netstat.
Leave it for 24 hours, check again, still cycling thru the same range (approx port 3000-6000)
In the EGGDROP's source code I had noticed some comments about the Ident port and 1 second intervals. I tried to find this to paste here, but cant find it again. I think it was the net.c sourcefile that had comments in it like"The identd port needs to be increased" "I dont know why it's done like this"
Also, these eggdrops are running on 2ghz p4 with 512MB DDR.
I wondered if it's possible the eggdrop is running on ticks and not seconds? could my faster-than-before pc be speeding up the eggdrop unnecessarily? Just like old 386games, when they were put onto a 486 dx100, the game was unplayable. because it was running too fast, could my machine be overclocking the eggdrop? Sounds ridiculus, but its a thought.
Thx for your time.[/b]
Do that a few times, and you'll see that one of the ports has 'moved' to a slightly higher number, everytime u netstat.
Leave it for 24 hours, check again, still cycling thru the same range (approx port 3000-6000)
In the EGGDROP's source code I had noticed some comments about the Ident port and 1 second intervals. I tried to find this to paste here, but cant find it again. I think it was the net.c sourcefile that had comments in it like"The identd port needs to be increased" "I dont know why it's done like this"
Also, these eggdrops are running on 2ghz p4 with 512MB DDR.
I wondered if it's possible the eggdrop is running on ticks and not seconds? could my faster-than-before pc be speeding up the eggdrop unnecessarily? Just like old 386games, when they were put onto a 486 dx100, the game was unplayable. because it was running too fast, could my machine be overclocking the eggdrop? Sounds ridiculus, but its a thought.
Thx for your time.[/b]
