<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Ah, Robert beat me to it! <br><br>--- On <b>Thu, 9/10/08, Robert Ladyman <i><it@file-away.co.uk></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">From: Robert Ladyman <it@file-away.co.uk><br>Subject: Re: [dundee] ipw2200, unlucky for some, i would say<br>To: "Tayside Linux User Group" <dundee@lists.lug.org.uk><br>Date: Thursday, 9 October, 2008, 1:05 PM<br><br><pre>Channel 13 is not legal in some countries: check the country the driver thinks <br>it is in.<br><br>On Thursday 09 October 2008 12:35:29 Arron Finnon wrote:<br>> Hi Guys,<br>><br>> Just encountered a pretty random bug/issue not too sure if it is a<br>> elonex webbook issue or if it is with the ipw2200 wireless card. Its<br>> one of those bugs which was pretty hard to get to the bottom of (when<br>>
i say that what i mean get my laptop connected to my home wireless)<br>><br>> NetworkManager and iwlist both could see my wireless network and i had<br>> no prevoius problems connecting to my wireless network, i changed some<br>> network configurations, and i also altered some wireless network<br>> configurations nothing major though. Just essid, and IP address<br>> pools. Banged up the AP, and every single one of my devices connected<br>> fine without issue a part from one. It could see it but it would not<br>> do the hand shake, it was like it would not associate.<br>><br>> At this point i was about to jump of the deep end, as you can imagine<br>> it worked fine, then it stopped. I was left scratching my head, i<br>> started to think their was a bug in NetworkManager (wouldn't be the<br>> first time).<br>><br>> Then i noticed that whatever i did, iwconfig would always indicate<br>> that it was on
channel 0 (there was a numerous wifi spots in the area,<br>> and 13 hadn't been taken, so being clever i went for the one no one<br>> was using and a about 5 channels away from anyone else, also could i<br>> really be that unlucky).<br>><br>> I tired to set it manually, and then it dawned on me. It woulnd't set<br>> to channel 13. Changed the AP to channel 10, seconds later i was<br>> connected.<br>><br>> So i thought i would post it to you guys, there isn't much of an<br>> issue, but i thought it was an interesting bug, and maybe newer users<br>> may have had this issue, and put it down to "oh linux wireless is<br>> naff"<br>><br>> So if anyone is running 8.04, and has ipw2200 card, might be worth<br>> changing your channel to 13 and seeing if you get the same issue or<br>> not, just curious i suppose.<br>><br>> Anyways catch you all tonight<br>><br>> Finux<br>><br>>
_______________________________________________<br>> dundee GNU/Linux Users Group mailing list<br>> dundee@lists.lug.org.uk http://dundee.lug.org.uk<br>> https://mailman.lug.org.uk/mailman/listinfo/dundee<br>> Chat on IRC, #tlug on dundee.lug.org.uk<br><br>-- <br><br>Robert Ladyman<br>File-Away Limited, 32 Church Street, Newtyle<br>Perthshire, PH12 8TZ SCOTLAND<br>Registered in Scotland, Company Number SC222086<br>Tel: +44 (0) 1828 898 158<br>Mobile: +44 (0) 7732 771 649<br>http://www.file-away.co.uk<br><br><br>_______________________________________________<br>dundee GNU/Linux Users Group mailing list<br>dundee@lists.lug.org.uk http://dundee.lug.org.uk<br>https://mailman.lug.org.uk/mailman/listinfo/dundee<br>Chat on IRC, #tlug on dundee.lug.org.uk<br></pre></blockquote></td></tr></table><br>