next »

[Oski]

Thanks Ben, you were right. I re-installed everything and it's working now! It was easy... 

I'll try again with Wpa.sh, hopefully I won't corrupt the files again...

[Oski]

I asked before how to get the MAC address, but I got it: \sbin\ifconfig (the one associated to eth0)....

[dwgsp]

I am having zero success getting this to work.  I installed the Wpa.sh script on the XO, and I ran the hex converter to get my passcode.  But I still cannot connect to my AP.  I tried using both the hex and text versions of the passcode, as well as both WPA types.  I did notice that in three of the four cases, when I rebooted and looked at my AP in the Neighborhood the circle icon has a padlock, however in once case it did not. 

I then tried to connect to my neighbor's AP, which has no security, and that also did not work.  Or at least I am assuming that it did not work, since I could not browse to www.google.com.  I'm not sure what the icon in the Neighborhood should look like if I am connected.

I guess that one potential issue is that both me and my neighbors have Linksys hardware, which I guess the XO may not be compatible with.

I set up wireless networks at work (for product compatibility testing), so this is all very frustrating.  Should I consider upgrading to the 653 build?  Any suggestions will be greatly appreciated.

Thanks!
/Don

[jefeliz]

Don -

Just from my experience, updating to build 653 made all the difference in the world. I did it at work this afternoon, just fired it up at home now, located my AP in the neighborhood view (and it still had the lock!), clicked it a few times, entered my network key, and it connected just fine. I'm posting from my XO now, in fact! Sorry for the run-on sentence, just too excited!

Please note that I DID NOT have to run the Wpa.sh command at all for this to happen. . .

F.Y.I - I have a Motorola wireless router, using WPA-PSK with TKIP. The network key that I entered was the 'PSK' of the WPA-PSK set up, entered in plaintext, and I chose Tkip from the drop-down menu.

Hope this helps,or at least gives you encouragement to try the 653 update.

Jeff. . .

EDIT: Well, maybe my unbridled enthusiasm was a little premature. Since first writing this post I have only been able to connect to my AP twice, but I think I might have an idea of what is going on, but not WHY. The first time (after the initial post), it just connected right away, by itself. The second time, i had to reboot several times AND re-enter my network key. The third time I tried, I wasn't able to connect at all.

Finally, completely discouraged, I went in and deleted the entry for my SSID in .sugar/default/nm/network.cfg file. After another reboot, I was able to reconnect as described above.

So, in all, I guess it DOES  work, and considerably better than with the 650 build (since I was never able to connect with the 650 build), and I didn't have to use the Wpa.sh program. and, I guess it is a small price to pay to have to go in edit the network.cfg file if it means that I can connect to my home network (somewhat) consistently. This was written, again, on the XO.

Jeff.  . .

[BradJudy]

I haven't had luck with wireless at home either (Actiontec GT701W using WPA with 8 character password).  In fact, the SSID only appeared in the neighborhood once.  I tried the wpa.sh and played with wireless settings on my access point (channel, g vs b/g mode, etc), including trying WEP instead of WPA.  Nothing gets it to even show up in the neighborhood. 

At work today, it connected fine to the unprotected wireless.  I went ahead and updated it to 653 while at work, brought it home and my home SSID still doesn't show up.  I just re-ran wpa.sh with no luck. 

I've made sure my SSID is broadcasting and I removed the MAC address restriction on my wireless. 

On the plus side, the antenna must be better than my notebook, because it sees a lot more other SSIDs of my neighbors. 

[BradJudy]

Okay, no sooner did I post then I cleared out the networks.cfg and rebooted again.  This time my SSID appeared in the neighborhood, I clicked on it, entered my password in regular text and it connected. 

I'm online using build 653 and WPA. 

[Oski]

Here things are great too, everything works and I was able to connect to my home network with WPA2 encryption, also using the newest built of the OS... Santa is ready to come to town!!!! 

[eightbt]

I finally got my wifi working.  I couldn't get WPA1 to work, even using Wpa.sh, typing the hex string into the popup, and upgrading to build 653.  So I reconfigured my router for "WPA2-Auto" mode (there is a plain "WPA2" mode which I skipped over,) and it seems to work fine now.  I removed the /home/olpc/.sugar/default/nm/network.cfg file, gave it a reboot and connected to my network using the UI.  The AP had a lock on it, but typing in my plaintext key worked fine.

I have a D-Link DI-524 router.  I hope this helps someone else get online.  I know it was pretty frustrating trying to get mine to work.

[BradJudy]

Well, after one night of working wireless, my SSID once again doesn't even show up in the neighborhood view. 

I've rebooted a couple of times and tried removing the section of networks.cfg that references this network. 

It seems like wireless is still hit-or-miss for me, mostly miss at home. 

[mcarver2000]

I have been unable to connect the XO to my wireless router via WPA.....  None of the tricks work (Wpa.sh or build 653).  All other wireless devices I have will connect successfully to the router via WPA except the XO.  I have tried everything other than buying a new router (perhaps it is an issue with my router --- it is an older Dell Truemobile 2300 with the latest firmware update available via Dell's support).

I make successful connections via WEP (and of course no security), just not any flavor of WPA....

Since I must broadcast my wireless to get the XO to connect, I would really like to be able to use WPA for enhanced security,

[Ben James Ben]

FYI, there is a bug in the Wpa.sh script such that if your router's SSID or WPA password contains a space character, the wrong key gets generated in the networks.cfg file. Details are in: http://olpcnews.com/forum/index.php?topic=604.0

[dwgsp]

It sounds like I should upgrade to firmware build 653.  I'm willing to do that, but first I need to save all of the files that my kids have created (they both really like the XO).  Can anyone explain the easiest way to do this?

I asked a similar question earlier (http://olpcnews.com/forum/index.php?topic=517.msg3504#msg3504) but have not received any responses.

Thanks!
/Don

[GlenLivet52]

I am unfortunately in the same boat as the many that are unsuccessful in getting the XO connected.

I have done everything listed in this forum and OLPC Wiki:

• Re-Flash to OS build 653
• Ran Wps.sh (delete network.cfg dozens of times). 
• Change my router config to use WPA then WEP (128 amd 40, ASCII and hex) and completely open.
• Tried connections to other Open networks (that numerous other Windows PCs can connect to).

The XO does see a good number of networks in my area and has always correctly identified my AP as I changed SSIDs and so on.  So the radio part is working, it's very good at finding networks.


In all this troubleshooting on the XO , I ran iwconfig eth0 in the shell repeatedly and noticed something I think might be the problem.

My XO is having numerous / excessive Rx invalid frag: errors - in the order of thousands or tens of thousands.  I can't find many articles online that are *useful* that mention the errors. 

Regarding interference, I have made numerious tries at all times of the day, so I am VERY sure there is low to almost no interference.  iwconfig shows very good signal level(s) at all times.

My AP and XO are of course, set to the RTS of 2347 and Frag to 2346 (or did I get that backwards; either way it works for the Windows PCs without special configuration). 

My hardware is a Cisco 1231 AP.  My XO would not connect to the Cisco 1100 AP's are work either.

Can someone with a working wireless XO run the iwconfig eth0 repeatedly and report whether they have the numerous Rx invalid frag errors?


Thanks and Happy Holidays!!!
Jim.

[Torokun]

ARRGGGG

I updated to the latest build (653) and did the Wpa.sh thing too...

But, my wireless network (WPA2) still shows up as locked and it's asking me for "encryption key".

What am I doing wrong?

This is driving me crazy.

[KayTi]

Another "upgraded to build 653 and all is well in my XO's world" customer here.

Had to format my USB stick first (from XP - control panels/administrative tools/computer management/disk management/CAREFULLY SELECT USB DRIVE, right click, choose format, make sure it's FAT format, go.)

But otherwise, it all worked hunky dory.

Now off to install all those apps that got lost in the upgrade (easy stuff like speak and slider puzzle, no big whoop.)

Could just be me, but the whole system seems to be moving faster...