net: eof!(write) socket 8 (No route to host,113)

[Nettworkz]

Yes, I did SEARCH.

I run four bots on my own dedicated box. Last night all of them, 3 on Undernet and one on another network, all pinged out simultaenously.

I'm getting various errors for some reason but all of them seem to indicate a network problem. However the network appears to be working fine. I even disabled my firewall to check that, but it didn't help.

[16:20] Trying server Helsinki.FI.EU.Undernet.org:6667
[16:20] DNS resolved Helsinki.FI.EU.Undernet.org to 195.197.175.21
[16:20] [!m] NICK Richy
[16:20] [m->] NICK
[16:20] [!m] USER Richy . . :www.bothouse.com
[16:20] [m->] USER
[16:20] net: connect! sock 8
[16:20] Connected to Helsinki.FI.EU.Undernet.org
[16:20] [@]
[16:20] net: eof!(write) socket 8 (No route to host,113)
[16:20] Disconnected from Helsinki.FI.EU.Undernet.org
[16:21] Staying outside all channels until I am logged into X...
[16:21] Trying server Lelystad.NL.EU.UnderNet.Org:6667
[16:21] DNS resolved Lelystad.NL.EU.UnderNet.Org to 195.47.220.2
[16:21] [!m] NICK Richy
[16:21] [m->] NICK
[16:21] [!m] USER Richy . . :www.bothouse.com
[16:21] [m->] USER

At this poing I'm starting to think it's a network/uplink error more than anything else. Though one bot did return on its own, the others won't.

I should mention, the bots are all connecting to their botnet, just not the servers.

[demond]

not an eggdrop problem, likely Undernet issue

I've noticed that, for some reason, Undernet servers often fail to recognize a valid identd; of course, this might well be irrelevant to your problem

[Nettworkz]

Undernet servers often fail to recognize a valid identd; of course, this might well be irrelevant to your problem

Yeah, irrelevant to my issue, but also annoying at times

I dunno what's up, I'd buy an undernet problem but as I mentioned a bot that I had on a different network also pinged out simultaneously. Funny thing is after rebooting the box it reconnected, but the undernet bots are still a no go.

I even compiled a new bot on a different server in a totally different geographic region to try it out, it's getting the same error.

Odd thing is, if it's an undernet problem, why would a friend of mine's bots be all connected and not having an issue.

Damn perculiar....

[demond]

then the issue is probably on your side - something in your network configuration has changed, firewall setup maybe

check if you can get on irc (Undernet, other networks) with an irc client from the shell

[Nettworkz]

check if you can get on irc (Undernet, other networks) with an irc client from the shell

Oddly enough my bot that's not on undernet came back online after a reboot. Unfortunately I still get get the bots to connect to undernet.

Wierd thing, I moved one of the bots to a different machine across the country from where they are now, and it still won't connect. Hmm.. traceroue is looking interesting...

Code: Select all

root@svr01 [~]# traceroute us.undernet.org
traceroute: Warning: us.undernet.org has multiple addresses; using 66.198.80.67
traceroute to us.undernet.org (66.198.80.67), 30 hops max, 38 byte packets
 1  gateway.hardlink.com (140.186.176.254)  4.993 ms  5.147 ms  3.092 ms
 2  quincycol-cent.cent.net (199.232.74.25)  6.932 ms  7.773 ms *
 3  ge2-3-0-625.br1.qcy1.ma.gnaps.net (199.232.44.45)  17.138 ms  9.744 ms  7.436 ms
 4  POS3-3.GW5.BOS4.ALTER.NET (208.192.182.173)  9.254 ms  10.989 ms *
 5  * 552.at-5-0-0.XR1.BOS4.ALTER.NET (152.63.25.58)  7.652 ms  8.274 ms
 6  0.so-4-0-0.XL1.BOS4.ALTER.NET (152.63.16.121)  12.205 ms  8.252 ms  10.705 ms
 7  0.so-0-3-0.XL1.NYC4.ALTER.NET (152.63.21.17)  15.160 ms *  13.940 ms
 8  0.so-6-0-0.BR1.NYC4.ALTER.NET (152.63.21.77)  14.352 ms  17.137 ms  14.938 ms
 9  if-4-3.core1.NTO-NewYork.teleglobe.net (216.6.82.25)  15.081 ms  20.619 ms  14.357 ms
10  if-10-0.core3.NQT-NewYork.teleglobe.net (216.6.82.2)  37.074 ms  31.762 ms  31.457 ms
     MPLS Label=111 CoS=6 TTL=1 S=0
11  if-9-0.core2.MTT-Montreal.Teleglobe.net (207.45.222.110)  58.861 ms  28.841 ms  28.761 ms
     MPLS Label=643 CoS=6 TTL=1 S=0
12  Vlan3.msfc2.MTT-Montreal.teleglobe.net (207.45.221.167)  23.245 ms *  25.482 ms
13  * * *
14  Vlan3.msfc2.MTT-Montreal.teleglobe.net (207.45.221.167)  24.137 ms !X * *
15  * * *
16  * * Vlan3.msfc2.MTT-Montreal.teleglobe.net (207.45.221.167)  24.391 ms !X
17  * * *
18  * Vlan3.msfc2.MTT-Montreal.teleglobe.net (207.45.221.167)  28.654 ms !X *
19  * Vlan3.msfc2.MTT-Montreal.teleglobe.net (207.45.221.167)  34.127 ms !X *
20  * * *
21  Vlan3.msfc2.MTT-Montreal.teleglobe.net (207.45.221.167)  25.171 ms !X *  45.411 ms !X

[demond]

traceroute usually means nothing to irc; it uses ICMP which is normally filtered by irc servers' firewalls/routers

[Nettworkz]

Though it makes absolutely no sense to me whatsoever...

Playing around tonight trying to figure this out, I changed the port numbers the bots use to 6668 instead of the standard 6667. Lo and behold they all connected right up to Undernet, just like good lil children..

But the WHY is totally beyond me.