| View previous topic :: View next topic |
| Author |
Message |
Achilles Voice
Joined: 10 Mar 2005 Posts: 8
|
Posted: Tue Aug 16, 2005 3:36 pm Post subject: timed-out userfile transfer |
|
|
I am running a botnet with 5 eggdrops. I have been running for for over a year now but recently had to move the eggs to another machine. I have been trying to setup the eggs on a new machine and all works fine until they start sharing files and they time out.
These are echo's I get from the hub:
| Code: |
#ach# link [bot]
Linking to [bot] at 192.168.1.107:5907 ...
Received challenge from [bot]... sending response ...
Linked to [bot].
*** Linked to [bot]
Creating resync buffer for [bot]
Sending user file send request to [bot]
|
This is the echo from the same time from the bot:
| Code: |
Telnet connection: 192.168.1.107/52039
Challenging [hub]...
Linked to [hub].
*** Linked to [hub]
Downloading user file from [hub]
Failed connection; aborted userfile transfer.
|
Shortly after this (300 seconds to be exact (the timeout lenght I set)) I get this on the hub:
| Code: |
Timeout on userfile transfer.
*** Disconnected [bot] (timed-out userfile transfer)
Telnet connection: 192.168.1.107/52054
Challenging [bot]...
|
And this on the bot:
| Code: |
Disconnected from: [hub]. No reason (lost 4 bots and 1 user)
*** Disconnected from: [hub]. No reason (lost 4 bots and 1 user)
Received challenge from [hub]... sending response ...
Linked to [hub].
*** Linked to [hub]
|
I cannot get the bots to share files. I have edited the configs to the best of my knowledge, I have tried older versions of eggdrop and I have tried recompling the eggs many times. If anyone has any info on how I might fix this please let me know.
Thank you |
|
| Back to top |
|
 |
demond Revered One

Joined: 12 Jun 2004 Posts: 3073 Location: San Francisco, CA
|
Posted: Tue Aug 16, 2005 4:36 pm Post subject: |
|
|
hmm it's about time for someone to come up with DCC/userfile transfer (and possibly NAT/firewall) FAQ
you likely have firewall problem, talk to your shell admin, tell them you need at least one port open and listening, and refer to reserved-portrange in eggdrop.conf |
|
| Back to top |
|
 |
Achilles Voice
Joined: 10 Mar 2005 Posts: 8
|
Posted: Tue Aug 16, 2005 4:44 pm Post subject: |
|
|
I have the reserved portrange set:
set reserved-portrange 5900:5950
And I have ports 5900 to 6000 open and listening.  |
|
| Back to top |
|
 |
demond Revered One

Joined: 12 Jun 2004 Posts: 3073 Location: San Francisco, CA
|
Posted: Tue Aug 16, 2005 5:55 pm Post subject: |
|
|
| Failed connection; aborted userfile transfer. -- that means the leaf can't connect to hub's port, 5900:5950 or whatever (technically, in eggdrop's terminology, that's EOF, i.e. write() on that DCC socket has returned < 0, meaning either reset or never established connection), a typical firewall problem |
|
| Back to top |
|
 |
Achilles Voice
Joined: 10 Mar 2005 Posts: 8
|
Posted: Tue Aug 16, 2005 6:04 pm Post subject: |
|
|
| All of the bots are on the same box, all using local (behind the nat/firewall) ips (ie. 192.168.1*) Would the firewall issue still be an issue? Should they not be all local IP? |
|
| Back to top |
|
 |
demond Revered One

Joined: 12 Jun 2004 Posts: 3073 Location: San Francisco, CA
|
Posted: Tue Aug 16, 2005 6:10 pm Post subject: |
|
|
on the same box but using different local IPs? that doesn't make sense at all
anyway, make sure you have my-ip set properly on all bots (and bot userrecords of course) |
|
| Back to top |
|
 |
Achilles Voice
Joined: 10 Mar 2005 Posts: 8
|
Posted: Tue Aug 16, 2005 6:19 pm Post subject: |
|
|
| Sorry, I wrote that wrong, they are all on the same local IP, differant ports. |
|
| Back to top |
|
 |
demond Revered One

Joined: 12 Jun 2004 Posts: 3073 Location: San Francisco, CA
|
Posted: Tue Aug 16, 2005 6:25 pm Post subject: |
|
|
| if the problem persists, set your console to +thd and show us the log from the moment of linking, also the output of .dccstat |
|
| Back to top |
|
 |
Achilles Voice
Joined: 10 Mar 2005 Posts: 8
|
Posted: Tue Aug 16, 2005 7:29 pm Post subject: |
|
|
It would appear that it is working now. I had my-ip set to the external IP and not the internal and it seems to have fixed it. Way to go me.
Thanks for your help |
|
| Back to top |
|
 |
|