Oki buds, here's the bug... Bots within my local network can link and share userfile, but bots can't share userfile from remote locations (tho they still link...)...
They're all 1.6.8 windrops with Netbots 4.05 hosted on WinXP pcs, and I already tried setting the my-ip and timeout settings, with no result...
[19:52] (Wolf): [19:52] Challenging Fox...
[19:52] (Wolf): [19:52] Linked to Fox.
[19:52] (Wolf): *** Linked to Fox
[19:52] (Wolf): [19:52] Compressing user file for Fox.
[19:52] (Wolf): [19:52] Creating resync buffer for Fox
[19:52] (Wolf): [19:52] Sending user file send request to Fox
[19:52] (Wolf): [19:52] Timeout/EOF ident connection
Leaf side:
[19:56] (Fox): [19:58] Received challenge from Wolf... sending response ...
[19:56] (Fox): [19:58] Linked to Wolf.
[19:56] (Fox): *** Linked to Wolf
[19:56] (Fox): [19:58] Downloading user file from Wolf
[19:56] (Fox): [19:58] Failed connection; aborted userfile transfer.
[19:57] (Fox): *** Disconnected from: Wolf. No reason (lost 3 bots and 1 user)
Could it have something to do with the hub being on a dsl connection (need passive mode to connect to a dsl) ? If yes, how the **** can I set the leaf bot to use it ?
You can't change the way eggdrop does it linking, and sharing connections, and yes, the DSL is liely the problem.
A lot of DSL providers use NAT, to house multiple computers behind a single IP. This means that if some1 tries to connect to your IP, the NAT router doesn;t know which one of the many computers behind it, to forward the connection onto.
the hub has to be on a connection where you can forward ports to it. Hub always creates its listen sockets for file transfers to those defined by $reserved-portrange, so as long as you set this and forward ports appropriatly it will work.