egghelp/eggheads community

bots stoped linking to eachother

2002-02-07T01:53:00-04:00

I dont know why the hubbot accepts the telnets. but if I or any other bot tries to telnet in everything works...just the two bots on the same shell cannot talk to eachother. I can telnet to both and i can link bots to both (all outside connections). No one I have talked to can figure out why those two bots on the same shell refuse to talk and everyone so far says its a shell problem.

Statistics: Posted by Guest — Thu Feb 07, 2002 1:53 am

bots stoped linking to eachother

2002-02-06T18:05:00-04:00

if the loopback is not working, then why does the hub receive the telnet in the first place?

Statistics: Posted by Petersen — Wed Feb 06, 2002 6:05 pm

bots stoped linking to eachother

2002-02-06T15:01:00-04:00

Well seing how i did not change any of my settings and the provider did, I think its a provider problem. And the provider finally replied and said they have looping prooblems and some other issues from the upgrade to freebsd 4.5.
I recognized all the problems you mentioned and ther causes. I just thought i was missing something. dont be so harsh.
ohh and anything, bot or user, can telnet to the bots on the dorked up shell.(as long as there from outside that provider).but the two bots on that shell can not talk to each other. That is the real problem..and its still unresolved

Statistics: Posted by Guest — Wed Feb 06, 2002 3:01 pm

bots stoped linking to eachother

2002-02-06T08:24:00-04:00

I donno why you can't work this out for yaself. The bot has written the reason exactly why it isn't allowing the link.

(hubbot) Telnet connection: leafbot/1635
(hubbot)Timeout/EOF ident connection
(hubbot)Denied telnet: telnet@leafbot, No Access

1635 is the port the linking bot initiated its tcp connect from (not the port the hub is listening on). This is always randomly assigned by the os (within various range criteria) and 1635 is quite normal, and isn't your problem.

(hubbot)Timeout/EOF ident connection

This is your problem. Identd is not running, or is firewalled/broke. Thus you get this error

(hubbot)Denied telnet: telnet@leafbot, No Access

which means exactly as it says - telnet@leafbot has no access.

Either get someone to fix ident, or add the host telnet@leafbot to its userrecord on the hub.

Statistics: Posted by Petersen — Wed Feb 06, 2002 8:24 am

bots stoped linking to eachother

2002-02-06T00:06:00-04:00

my botnet was happy. My provider updated to freebsd 4.5 now the two bots on that provider wont link to eachother anymore. One of those bots is the hub. But all my other bots link just fine to the hub(all from other providers). the error i get is :
(hubbot) Telnet connection: leafbot/1635
(hubbot)Timeout/EOF ident connection
(hubbot)Denied telnet: telnet@leafbot, No Access

How is it that the port magicaly changed itselfto 1635 when it should be 46001?I deleted the bots on each and tried to add them with no success.

Statistics: Posted by Guest — Wed Feb 06, 2002 12:06 am