[arch-general] Strange network problem
Hello all, I've got a strange problem with a machine that had a fresh install three weeks ago. Nothing new has been installed on it since then. About one time in four, after that machine has been booted, a ssh to it (on a LAN) fails with 'no route to host'. Using ip link and ip addr on it shows everything is OK, it's not a NIC that gets the wrong name or so. The network on that machine is set up using netcfg, in the recommended way (/etc/conf.d/netcfg). Rebooting has solved the problem in all cases. Any hints as to what is going wrong ? TIA, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
On Mon, Oct 22, 2012 at 10:15:18PM +0000, Fons Adriaensen wrote:
Hello all,
I've got a strange problem with a machine that had a fresh install three weeks ago. Nothing new has been installed on it since then.
About one time in four, after that machine has been booted, a ssh to it (on a LAN) fails with 'no route to host'. Using ip link and ip addr on it shows everything is OK, it's not a NIC that gets the
And 'ip r' shows the machine has a default route to the gateway? It's a two way street. Do you have any roblems with outbound connections originating from this machine? d
wrong name or so. The network on that machine is set up using netcfg, in the recommended way (/etc/conf.d/netcfg).
Rebooting has solved the problem in all cases.
Sounds delightfully racy.
Any hints as to what is going wrong ?
I'm not sure there's enough info here for anyone to do anything more than guess.
I've got a strange problem with a machine that had a fresh install three weeks ago. Nothing new has been installed on it since then.
About one time in four, after that machine has been booted, a ssh to it (on a LAN) fails with 'no route to host'.
'no route to host' on a LAN (same ip range, right?) means the ARP resolution didn't work on the *client*. You need to check if ARP reply packets are received by the *client*, possibly with "tcpdump -i any arp" Also check "ip neigh" on the CLIENT to see what neighbours it knows about. -- дамјан
I got a similar problem once and it turned out to be a cable problem, have you tried changing the cables and / or the network cards? On Tue, Oct 23, 2012 at 5:03 AM, Damjan <gdamjan@gmail.com> wrote:
I've got a strange problem with a machine that had a fresh install
three weeks ago. Nothing new has been installed on it since then.
About one time in four, after that machine has been booted, a ssh to it (on a LAN) fails with 'no route to host'.
'no route to host' on a LAN (same ip range, right?) means the ARP resolution didn't work on the *client*.
You need to check if ARP reply packets are received by the *client*, possibly with "tcpdump -i any arp"
Also check "ip neigh" on the CLIENT to see what neighbours it knows about.
-- дамјан
participants (4)
-
Damjan
-
Dave Reisner
-
Fons Adriaensen
-
Juan Diego Tascón