Hmm, looks like this message never got through to the list, someone was asking about it off-list just now... FWIW my solution was to use the keepalive options (just -o BatchMode=yes actually) in the sshfs mounting that I have routinely up in the environment where I'd care about reaching the N800 from the network, to keep the AP happy.
Tuukka Tolvanen wrote: > Kalle Valo wrote: >> "ext Tuukka Tolvanen" <[EMAIL PROTECTED]> writes: > >>> ip=x.x.x.x; s=290; while date -Is; ping -c 1 $ip; do sleep $s; >>> s=$((s+10)); done >>> >>> In my case, taps don't matter, if after network use the device is >>> pinged at an interval increasing by 10s, it responds to the ping after >>> the 5min0s interval regardless of when blanking happened, but not >>> after the subsequent 5min10s interval. >>> >>> WLAN disconnect timeout not enabled, scan interval 10min (defaults). >>> Same effect regardless of different dim/blank timeouts. AP is dlink >>> DI-524, WPA-PSK (AES). No presence stuff is configured (I'd >>> guesstimate that is the relevant difference between back when I didn't >>> see this and now), no email polling. > >> Can you try with WLAN PSM disabled? Run the command below to do that. >> >> gconftool-2 --set --type int >> '/system/osso/connectivity/IAP/wlan_sleep_timeout' '120000' > > This didn't appear to make any difference. > >> Also could you try without AES? Could you try without encryption at >> all? > > Same issue with WPA-PSK (TKIP). I couldn't get the two to work together > with any other settings. > > Hmm. The AP's logs have this to say: > Disassociated: xx-xx-xx-xx-xx-xx because idle 300 seconds > I'm not sure if that indicates bug or feature, that timeout certainly > doesn't appear configurable on that side. > > 't. > _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
