After following the advice given here...

http://talk.maemo.org/showpost.php?p...8&postcount=41

...my net connection returned to life, but then I noticed quirky behavior with SSH.

At first I attempted to just uninstall/reinstall SSH and reboot - this seemed to fix things....I could SSH to my N900 from my PC just fine.

Later, I noticed that the sshd seemed to have timed-out, and was inaccessible from the outside. I opened a terminal on my N900 and "ssh root@localhost", which worked fine and seemed to kick sshd back into life, and I could connect again from my PC. Very odd behavior.

After leaving it alone for a while, I tried to SSH into my N900 from my PC - failure. This time I simply opened a browser bookmark...the network activity seemed to kick sshd into life, as I could SSH into my N900 once again.

Does anyone with deeper knowledge of sshd have any insight into what is causing this unreliable behavior? When I'm at my desk I like to just SSH into my N900 while it's stashed in my jacket.....I don't want to have to retrieve it and give it a virtual kick....kinda kills the whole point.

EDIT: Thanks to egoshin's suggestion, troubleshooting the actual WiFi connection seems to reveal the culprit. Apparently a change has been made to the "maximum" power saving profile for the internet connections (a consequence of fixing the WiFi power drain bug perhaps?) that powers down the Tx/Rx radio hardware after it has been idle for x minutes. Normally this isn't a problem for most people (or me for the majority of the time) but for those of us that use SSH to hack around inside our N900s it's a real Painus In The Anus.

Setting the power saving setting to "intermediate" does not seem to cure the problem, and looking at my router's "connected devices" page reveals that my N900 has vanished. Looking at my N900 desktop, however, shows the WiFi connection up and my wlan0 IP is still set.

If I ping google.com from my N900 terminal, my router sees the N900 again and all is well.

Unsurprisingly, turning off WiFi power saving completely 'fixes' the problem...but not really Man that thing sucks the battery dry in a hurry.

Clearly there's an issue here - we absolutely need power saving for WiFi, but it mustn't drop the connection...

Most people won't be affected by this, I reckon, because as soon as you try to reach out from the N900 onto the net, it wakes up and everything is OK - you don't notice the flaw. But for developers like me that are shoving stuff back and forth via SSH or SCP etc...it's a total rectal prolapse.

Quick temp hackery fix - set email to check every 5 mins?

It is definitely not sshd issue. It seems like you lose low-level (WiFi or 3G) Internet connection over time and your ping, ssh, web - any kind of activity from N900 - wakes it up.

Which provider do you have and what setup? Because it is common for some kind of "broadband dial-up" connection. If it is WiFi it has sense to test with another router (come to friend or starbacks or whatever). You also may try to log on WiFi router logs if any.

EDIT: look into "Connect automatically" in "Settings", if it is not Auto, then you may just lose connection because of some reason and it doesn't restore automatically.

Exact same problem here, anyone with a solution??

1. Please report this ASAP to bugs.maemo.org

2. Can you install package 'sysklogd' (which includes 'klogd') and repeat? After repeat - copy the file /var/log/syslog in compressed form to that bug report. You may edit out your IMEI and WiFi network name for privacy reason first.

I have had this issue from day dot. Others too.

http://talk.maemo.org/showpost.php?p...5&postcount=21

are you sure this is not a psm issue with your router


http://wiki.maemo.org/Wifi_power_saving_mode

egoshin, I don't think we have to open a new bug for it. Have a look at Bug #7277. I think that's it. We should probably reopen that one, IMNSHO.

I mentioned the issue in the PR1.1 Feedback? thread, and timperi seems to have the same problem.

I'll try and gather more information as well tomorrow, time permitting (for me, the issue happens 'just' at work) and add it to the aforementioned bug report.

Regards,

Chris.

OK, I think I know that is it - do you see in /var/log/syslog the repeating messages "wlan0: driver reports beacon loss from AP cf1bb52c - sending probe request" ?

Can't say yet, won't be back in the office until tomorrow and didn't have sysklogd installed yesterday. I'll keep you posted A.S.A.P..

Regards,

Chris.

Nope, just getting the deauthenticated/authenticated/associated messages:

... ad infinitum.

Access point is a funkwerk W2002 in my case. No idea about its firmware version, though.

Fact is, if you keep up network traffic by some means (i.e. running a ping -f from an external node towards the N900), things do stay smooth even with power management enabled. Once the ping interval is increased to something beyond 100 ms, I am beginning to see packets being dropped. Once it reaches the default 1 second, the N900 will essentially begin to drop all packets unless there is some network operation performed on the device itself. So it really appears as if the RX of the WLAN hardware is turned off completely in this case.

Regards,

Chris.