Not super familiar with AWS, but can you move instances to a new hypervisor? I've seen similar issues with VMware and XEN where the network stack at the hypervisor gets a bit goofed up and moving the VM to a different hypervisor fixes the issue. Rather than stop/start and get a new IP if you can keep the IP, but move the instance somewhere and the problem goes away that would be quite telling.
On Mon, Oct 6, 2014 at 11:41 AM, Yves Dorfsman <y...@zioup.com> wrote: > > We've run into this weird AWS issue 3 times now in a week, never seen it > before: > > A Linux instance becomes unreachable via ssh from some ip addresses. If you > try to ssh from those addresses, it just hangs, for ever, until to ctrl-c > out > of it. Yet you can ssh from other ip addresses without any problem. > > The ip addresses that work and that don't seem random, some are outside > AWS, > some inside, even on the same subnet. When we run in DEBUG3 mode, we see > that > the client sent it's key, while the server waits for the said key, and sits > there waiting. The few similar issues (ssh hanging at key exchange) we > found > when googling were solved by changing MTU! > > The only resolution we have found so far is to stop/start the instance and > get > a new ip (tbh, we haven't tried to just reboot). > > Has anybody run into this? Any idea what's going on? > > -- > Yves. > _______________________________________________ > Tech mailing list > Tech@lists.lopsa.org > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/ >
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
