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.

SOLVED: [Userfile sharing] Botnet issues

General support and discussion of Eggdrop bots.
Post Reply
F
Fill
Halfop
Posts: 80
Joined: Sun Jan 18, 2009 6:08 pm

SOLVED: [Userfile sharing] Botnet issues

Post by Fill »

Hi everyone,

I linked two bots and I wanted to make them share userfile. I have double-checked everything but they won't send the userlist each other :/

I have transfer and share modules loaded. Here's what I get in the partyline:

Code: Select all

<ePlusY> [18:42] Sending user file send request to ePlusX
<ePlusY> [18:43] CAN'T OPEN A LISTENING SOCKET -- can't send userfile
<ePlusY> [18:43] Sending user file send request to ePlusX
And this is the one that should receive userfile

Code: Select all

<ePlusX> [18:44] Downloading user file from ePlusY
<ePlusX> [18:44] Ending sharing with ePlusY (Can't send userfile to you (internal error)).
<ePlusX> [18:44] (Userlist download aborted.)
They're hosted on the same box and on the same ip. Ports are correctly configured. Here's the whois output for each one of the bots:

Code: Select all

<Fill> .whois ePlusY
<ePlusX> [18:45] #Fill# whois ePlusY
<ePlusX> HANDLE    PASS NOTES FLAGS           LAST
<ePlusX> ePlusY    yes      0 b               18:15 (linked)
<ePlusX>   BOT FLAGS: ghp
<ePlusX>   ADDRESS: 94.23.89.217
<ePlusX>      users: 31312, bots: 43500
<ePlusX>   HOSTS: *!ePlusY@1223AEAD.26D4B4E0.3F6C4BC1.IP

Code: Select all

<Fill> .whois ePlusX
<ePlusY> [18:46] #Fill# whois ePlusX
<ePlusY> HANDLE    PASS NOTES FLAGS           LAST
<ePlusY> ePlusX    yes      0 b               18:15 (linked)
<ePlusY>   BOT FLAGS: gls
<ePlusY>   HOSTS: *!ePlusX@1223AEAD.26D4B4E0.3F6C4BC1.IP
<ePlusY>   ADDRESS: 94.23.89.217
<ePlusY>      users: 31112, bots: 43121
What's going on :?: :roll:
F
Fill
Halfop
Posts: 80
Joined: Sun Jan 18, 2009 6:08 pm

Post by Fill »

Found the error! I was using reserved-portrange 1026:1026 on both, which means that they were using the exact same ports, so they couldn't send userfile in an already used port :lol:
Post Reply