<br><br><div><span class="gmail_quote">2008/2/14, Kalle Valo <<a href="mailto:kalle.valo@nokia.com">kalle.valo@nokia.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>><br> >> Most probably the connection would recover after a while, and the<br> >> while here being several minutes with the default TCP settings.<br> ><br> ><br> > You think those time outs are really that long ?<br>
<br> <br>Yeah, they are quite long. I have heard about long timeouts with other<br> applications using TCP.<br> <br> An easy way to confirm, if this is a TCP problem or something else, is<br> to run ping in the background and see how long timeouts (ie. how much<br>
you see packet loss) you get with it. ICMP ping does not have any of<br> problems that TCP has.</blockquote><div><br>Yes I did and indeed ping works much better.<br>i tried ping -s 1024 mylocalgatewayip <br>(1024 byte long packets)<br>
and indeed it works ok. sometimes it loses 1-4 packets while roaming<br>but afterwards the number of packet loss is usually small.<br>when roaming around the wlan it is about 3-4%<br>but the nokia wlan lockup remains, see below.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > the strange thing is if I go around the area with my Dell Laptop<br> > (under Windows) with VNC open it does not suffer from those extreme<br>
> slow downs.<br> <br>I'm guessing that the laptop is roaming more aggressively than the<br> N800 and TCP works fine because of that.<br> yes could be.<br><br><br> <br>I usually run 'iwevent &' to get it running in the background so<br>
that I can easily see what's happening. Very handy.</blockquote><div><br>thanks. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Sorry, I made a mistake here! Unit of bgscan_interval is milliseconds,<br> not seconds as I say above. So the correct way to set background scan<br> interval is this:<br> <br><br> gconftool-2 --set --type int \<br> <br>
'/system/osso/connectivity/IAP/bgscan_interval' '20000'<br> <br> I'm sorry about this.</blockquote><div><br>no problem, thanks, i will try it out.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> As for the network lock ups we are experiencing (you have to<br> > disable,enable wlan on the n800 to make it work again)<br> <br> <br>Does ping work when that happens? For example, you could try to ping<br> your gateway. Also can you send me the output from dmesg after you<br>
experience this, please?</blockquote><div><br>when it locks up even ping stops responding, I get a message connection lost (from maemo).<br>I just tested it today with an xterm open running a constant ping and walking around the area.<br>
after 10min it stopped working (I was out of coverage area and returning)<br>I did unfortunately not look at the dmesg output, I will try again and report my findings.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> other users reported it too as Luca Olivetti pointed out. and it<br> > seems like the problem and fix is described here:<br> ><br> > <a href="http://internettablettalk.com/forums/showpost.php?p=134914&postcount=15">http://internettablettalk.com/forums/showpost.php?p=134914&postcount=15</a><br>
><br> > at least for the 770 the fix seems to exist,<br> <br> <br>What I read from the link, someone had written a workaround to try<br> again whenever the chip is responding. That would good a feature, but<br> I would like to get more information about what's happening in this<br>
case.</blockquote><div><br>i will investigate this issue and will look at the sources of the patch and see if <br>it can be adapted to the n800 wlan driver (I can ask for help on the project's mailinglist)<br>i hope it will solve the issue as this problem occurs several times per day in my wlan environment.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br>770 has quite old software, so I would prefer if you can send me more<br> information with N800.</blockquote>
<div><br>of course, I will do it, we will buy more n800,n810 for our purposes certainly not 770 :<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br> <br>With WLAN driver changes ASAP usually means quite a long time due to<br> all the risks, testing and certification involved.</blockquote><div><br>Yes, but I am willing to run my patched driver if needed, this is not a problem.<br>
I will investigate all the issues and report all my findings.<br></div><br>PS:<br>meanwhile in order to automate WLAN lockup recovey, how could I write<br>a script which basically does the same like clickingon the connectivity icon,<br>
basically bring down wlan and then bring it back up.<br>I tried with <br>ifdown wlan0 ; ifup wlan0 <br>but it does not work it says no such device.<br>any hints ? some commands to send to wcond ?<br><br>thanks and best regards,<br>
Benno<br><br></div><br>