From: Nicholas Clark Date: 20:12 on 14 Feb 2006 Subject: The Internet $ scp -p saigo.etla.org:bin/assimilate ~/bin ssh: connect to host saigo.etla.org port 22: No route to host What do you mean "No route to host"? I'm only fucking logged in here from saigo.etla.org. There must be a route for that error message to have reached my terminal. And attempting to route from 1 machine (in France) to another (also in France) via Seattle (not in France, not even in Europe) considered, well, brain dead. Please just be working. Thanks in advance. Nicholas Clark
From: Rob Scovell Date: 20:21 on 14 Feb 2006 Subject: Re: The Internet This reminds me of the day that IPv6 came to the rescue. I was working with 2 servers next to each other in a rack across the planet, using ssh. I was creating an IP alias using ifconfig ... and had a 'balding grey-haired moment' and forgot to put alias in the command. Killed my ssh connection and stuffed up IPv4 routes somehow. By a miracle, I suddenly thought 'IPv6' and got back in that way from the neighbouring server ... without that neighbouring server, would have been stuffed, and would have had to send client physically round to the rack to recover ... not good ... On 15/02/2006, at 9:12 AM, Nicholas Clark wrote: > $ scp -p saigo.etla.org:bin/assimilate ~/bin > ssh: connect to host saigo.etla.org port 22: No route to host > > > What do you mean "No route to host"? > I'm only fucking logged in here from saigo.etla.org. > There must be a route for that error message to have reached my > terminal. > > And attempting to route from 1 machine (in France) to another (also in > France) > via Seattle (not in France, not even in Europe) considered, well, > brain dead. > > Please just be working. Thanks in advance. > > Nicholas Clark > --- Rob Scovell 7A Brooklyn Road Hamilton 2001 New Zealand NZ phone: 07 853 9143 UK phone: 0845 229 2290/7025
From: Nicholas Clark Date: 20:24 on 14 Feb 2006 Subject: Re: The Internet On Wed, Feb 15, 2006 at 09:21:13AM +1300, Rob Scovell wrote: > This reminds me of the day that IPv6 came to the rescue. I was working Oh, I'm hating IPv6 too. It's all broken. 65% packet loss and up to 15 second ping times between two machines over IPv6, whereas IPv4 is working just fine. Nicholas Clark
Generated at 10:26 on 16 Apr 2008 by mariachi