On some Wifi routers (Sitecom WL-114, WL-141, Siemens SX-551) the following occurs:

1 Connect to WIFI and then from a Windows PC via WinSCP or putty to the N810.
2 if (connection fails)
step 5
else
step 3
3 Wait > 10 minutes
4 Do something in SSH / SCP session
if (Connection lost, cannot reconnect anymore.)
step 5
else
step 2
5 Disconnect N810 and reconnect to same network
6 Goto step 1.

This problem occurs anyway when the N810 has either a DHCP assigned IP address or a fixed one.
In all cases a WPA key is used.
The interesting thing is that OUTbound connection from the N810 (web surfing, MSN, etc. has no rpoblems when the SSH/SCP session freezes.
Other computers in the same network do not have this problem, so it is a problem of the N810.

Is this a N810 firmware bug ?

Hey have this problem at work too. But luckily we have two wireless routers and the second one works. You need to turn power saving off in the wireless settings to fix it (though you do get lower battery life).

I tried this and it worked better (ping from a pc yields now <10ms was previously >100ms) but after a few minutes inactivity I have to 'activate' the connection, see the log below.
With putty, the first time I have to reset the terminal and then it connects.
It seems that after a certain period of time the SSH connection 'falls asleep' and has to be woken up.

It is on a Sitecom WL-114.
On the Linksys WRT160N the problem does not occur so I left the setting to power saving on (is configurable per connection).


Pinging 192.168.1.171 with 32 bytes of data:

Request timed out.
Reply from 192.168.1.171: bytes=32 time=18ms TTL=64
Reply from 192.168.1.171: bytes=32 time=5ms TTL=64
Reply from 192.168.1.171: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.1.171:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 18ms, Average = 9ms

C:\Documents and Settings\klaas>ping 192.168.1.171

Pinging 192.168.1.171 with 32 bytes of data:

Reply from 192.168.1.171: bytes=32 time=4ms TTL=64
Reply from 192.168.1.171: bytes=32 time=4ms TTL=64
Reply from 192.168.1.171: bytes=32 time=5ms TTL=64
Reply from 192.168.1.171: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.1.171:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:

Also, Have you also changed the idle time to 5 min in connectivity?

It's a bit of a nusance i grant you.

Richard

Some older routers don't support the power saving element of the protocol. Fon router is an example. You can tell the N810 not to use power saving and it will work with Fon but it uses battery power faster. The parameter is deep in Control Panel. Select Conectivity-> Connections button-> Connection SSID you want to change for-> Edit button-> Next button until the last screen-> Advanced button-> Other tab-> change power saving.

I already changed that and now it works.
On a Linksys WRT160N I can let the power save mode on as this router supports power save mode.
Thanks !