ssh problems after recent kernel update

[srulop]

Hi,

After the recent kernel update (3.6 --> 3.10) I started to experience really strange problems with ssh access.
When I'm trying to ssh my Pi, I randomly get either "connection timed out" or "no rout to host" or just a very slow connection or a perfectly normal connection. I don't know how this is tied to the kernel update, but it statred occuring right after that. Openssh was updated then also, but I tried downgrading it - with the same results. Didn't try downgrading the kernel though - seems too risky for me.
I didn't change any network configurations nor router configurations from before. Didn't change anyting, apart from updating regularly.

Anyone has an idea of what the problem might be?

Thanks!

[sdjf]

When I was regularly having problems like this many months ago, I created a script that would run diagnostics for me and save them, you might do that if the logs are not helpful.

Can't tell what is going on otherwise, but what I would do is make some sort of daemon that checked to make sure that my ethernet or wlan or whatever was up and, if it was not, bring it back up with ifconfig. If you do not have logs, that daemon could also run and save dmesg output at those points that the interface needed to be brought back up.

Could also be a bad cable, intermittently working properly?

[srulop]

Thanks!
$this->bbcode_second_pass_code('', 'ip addr | grep wlan0\: | sed 's/.*state //;s/ qlen.*//'')
logs "UP" so far all the time, so... I don't know, but good idea though!
By the way, sdjf, what was the source of your problem?

Other pieces of details:
1) The errors, apparently, are not so random: when I try to connect from a wireless network, it says "no rout to host", and from wired - "connection timed out". I tried this on several networks (all have nothing to do with my home network - I'm connecting to it from another city).
2) The only abnormal thing during that kernel update, was that it failed to reboot (just went unresponsive). I had to get back home (about 100km!) for force-rebooting it by unplugging the power. No other problems though.

Next time I'm home, I'll try switching my Pi with a new one - mybe the Pi itself failed? Will update.

[sdjf]

Sorry, accidentally erased long reply, time crunch so just summarizing now.

Wireless I have no experience with, obviously there is not a shared network up.

Wired, check ifconfig at both ends, sounds like that network is up but you are
trying to connect to the wrong IP, most likely Pi has different IP than your
external device is trying to connect to. Do ifconfig, the inet IP is the one
your Pi is on.

I think wired means ethernet, that network IP I think will be different than the
network for wlan. Same Pi but each type of connection is on a different network

I connect to Pi with two different PDAs, one is over ethernet, the other usb.