weird problem when linking the bots!

Alchera · Post by **Alchera** » Tue Sep 14, 2004 9:25 pm

Would appear then that ports are blocked. If the provider doesn't allow then you don't have a botnet.

Escolar · Post by **Escolar** » Sat Sep 18, 2004 8:40 pm

Alchera wrote:Would appear then that ports are blocked. If the provider doesn't allow then you don't have a botnet.

its weird

I will contect them! thank you I will post whatever their reply is.. thx everyone!

Alchera · Post by **Alchera** » Sun Sep 19, 2004 5:32 pm

It could be their firewall settings are set pretty tight to stop DDoS attacks. I have three bots in a similar situation, they cannot directly link to eachother but I can manually link them to another bot on another provider's box. Contacting your shell Admin is a good idea.

sandberg · Post by **sandberg** » Mon Sep 20, 2004 6:40 am

Did you guys find any solution? I got a similar problem.

I got these two bots Britney and Stacie.

12:35:24 <GlassBil> .whois Stacie
12:35:24 <Britney> [12:35] #GlassBil# whois Stacie
12:35:24 <Britney> HANDLE PASS NOTES FLAGS LAST
12:35:24 <Britney> Stacie no 0 bflo never (nowhere)
12:35:24 <Britney> BOT FLAGS: h
12:35:24 <Britney> ADDRESS: 213.214.230.10
12:35:24 <Britney> users: 3399, bots: 3399
12:35:24 <Britney> HOSTS: *!stacie@213.214.230.10

12:35:35 <GlassBil> .whois Britney
12:35:35 <Stacie> [12:35] #GlassBil# whois Britney
12:35:35 <Stacie> HANDLE PASS NOTES FLAGS LAST
12:35:35 <Stacie> Britney no 0 bflo never (nowhere)
12:35:35 <Stacie> BOT FLAGS: h
12:35:35 <Stacie> ADDRESS: 213.214.230.10
12:35:35 <Stacie> users: 3355, bots: 3355
12:35:35 <Stacie> HOSTS: *!britney@213.214.230.10

They find eachother in the channel. But when I do .link:

12:36:30 <GlassBil> .link Britney
12:36:30 <Stacie> [12:36] #GlassBil# link Britney
12:36:30 <Stacie> [12:36] Linking to Britney at 213.214.230.10:3355 ...
12:36:30 <Stacie> *** [Stacie] Couldn't link to Britney.
12:36:30 <Stacie> [12:36] Failed link to Britney.

12:36:46 <GlassBil> .link Stacie
12:36:46 <Britney> [12:36] #GlassBil# link Stacie
12:36:46 <Britney> [12:36] Linking to Stacie at 213.214.230.10:3399 ...
12:36:46 <Britney> *** [Britney] Couldn't link to Stacie.
12:36:46 <Britney> [12:36] Failed link to Stacie.

Any idea what might be wrong? I have forwarded the ports
in my firewall. And I can dcc on the port myself with my user.

Best regards
David

gumbydammit · Post by **gumbydammit** » Mon Sep 20, 2004 7:35 am

make sure "my-ip" is set on your bots... ask your admin for a list of available ports perhaps.. or possibly try linking them via localhost (seeing how they are the same box )

sandberg · Post by **sandberg** » Mon Sep 20, 2004 8:38 am

Im the admin

The ports are available.

I got "set nat-ip "192.168.0.15"". And the config says I shouldn't
set my-ip then.

I tryed using localhost but it didn't work.

14:36:20 <GlassBil> .link Stacie
14:36:20 <Britney> [14:36] #GlassBil# link Stacie
14:36:20 <Britney> [14:36] Linking to Stacie at localhost:3399 ...
14:36:20 <Britney> [14:36] Failed link to Stacie.

14:36:14 <GlassBil> .link Britney
14:36:14 <Stacie> [14:36] #GlassBil# link Britney
14:36:14 <Stacie> [14:36] Linking to Britney at localhost:3355 ...
14:36:14 <Stacie> [14:36] Failed link to Britney.

YooHoo · Post by **YooHoo** » Mon Sep 20, 2004 11:15 am

why do they both have the botflag +h? Only the hub should have the hub flag

sandberg · Post by **sandberg** » Mon Sep 20, 2004 12:29 pm

Oops. Now I changed it so Britney got +hp and Stacie got +s. But they are still not linked...

sandberg · Post by **sandberg** » Mon Sep 20, 2004 1:10 pm

Now they connect when I changed .chaddr to 192.168.0.15.
But I get another error now.

Code: Select all

19:18:00 <Britney> [19:18] Sending user file send request to Stacie
19:19:00 <Britney> [19:19] CAN'T OPEN A LISTENING SOCKET -- can't send userfile


19:19:00 <Stacie> [19:19] Downloading user file from Britney
19:19:00 <Stacie> [19:19] Ending sharing with Britney (Can't send userfile to you (internal error)).
19:19:00 <Stacie> [19:19] (Userlist download aborted.)

Any ideas?

YooHoo · Post by **YooHoo** » Mon Sep 20, 2004 2:50 pm

certainly. change the bot's listening port, located in the conf file. By default, it is set to listen 3333 all, unless you have launched the newest egg, 1.6.17, which in that case it came #commented out. Change this port to any number between 1025 - 65535, assuming that a) your shell provider allows connections within the same range, and b) the port isn't already being used by another user on the same shell.
It is a necessity to read and edit the entire conf file! Your bot's security and stability depend 100% on the information you enter in the variables, and, obviously, the bot won't run unless the conf file has been edited. Included with every eggdrop is a text file that spells out what each setting is used for, and the file path should be something similar to /home/myshell/mybot/doc/settings/core.settings. A similar file can be found here: Setting Up An Eggdrop. Good Luck!

sandberg · Post by **sandberg** » Mon Sep 20, 2004 3:10 pm

I got listen 3399 all on Stacie and listen 3355 all on Britney and both
use eggdrop 1.6.17. The ports are not being used by any other apps.
Im not sure if the ISP have blocked the ports of the bot. The contract
says that your not allowed to use eggdrops. But im not sure if they
have blocked the portrange. Should I try to use a higher port number?

A pice of Stacies config:

Code: Select all

listen 3399 all
set nat-ip "192.168.0.15"
set reserved-portrange 3400:3408

A pice of Britneys config:

Code: Select all

listen 3355 all
set nat-ip "192.168.0.15"
set reserved-portrange 3356:3364

Alchera · Post by **Alchera** » Mon Sep 20, 2004 6:15 pm

sandberg wrote:The contract says that your not allowed to use eggdrops.

Is there something you're not quite grasping? Of course they would have ports blocked and you being in violation of your contract could cause you to lose your account also.

YooHoo · Post by **YooHoo** » Mon Sep 20, 2004 9:47 pm

sandberg wrote:The contract says that your not allowed to use eggdrops.

hahahahaha

sandberg · Post by **sandberg** » Tue Sep 21, 2004 5:12 am

Well, I got it working now

I changed the port to a higher number.
I don't care if the ISP cuts me of. Then I just change to a better one.
I hate the ISP I got now.