nanog mailing list archives
Re: the little ssh that (sometimes) couldn't
From: Jon Lewis <jlewis () lewis org>
Date: Mon, 29 Oct 2012 14:54:32 -0400 (EDT)
On Mon, 29 Oct 2012 bmanning () vacation karoshi com wrote:
corruption! http://mina.naguib.ca/blog/2012/10/22/the-little-ssh-that-sometimes-couldnt.html
Bush league. I debugged a similar issue on Sprint's network about 15 years ago, also nailing it down to which router/router hop had the problem (a misconfigured interface that couldn't pass certain bit patterns and was causing a particular file we were hosting for a customer to be non-downloadable by any client who's packets used the bad path), also using ping, but with a pattern much more interesting than large packets of nulls...and I had to figure out the problematic pattern before I could do the ping tests.
But if you want really bizzare, this one never got solved to my satisfaction. http://mailman.nanog.org/pipermail/nanog/2008-August/002788.html
---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Senior Network Engineer | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
Current thread:
- the little ssh that (sometimes) couldn't bmanning (Oct 29)
- Re: the little ssh that (sometimes) couldn't Jon Lewis (Oct 29)
- Re: the little ssh that (sometimes) couldn't Robert Drake (Oct 29)
- Re: the little ssh that (sometimes) couldn't Mike O'Connor (Oct 29)
- <Possible follow-ups>
- Re: the little ssh that (sometimes) couldn't George Herbert (Oct 29)
- Re: the little ssh that (sometimes) couldn't Jon Lewis (Oct 29)