next »

[Lightfoot]

Been running on build 703 for several months. Finally, was able to get the jabber to allow me to see "Neighbors". One day the local router was asking for password to log on (it apparently it loss the info after all this time?).

Instead of keying it in every session I tried to reflash the XO using an empty USB with

http://download.laptop.org/xo-1/os/official/703/jffs2/fs.zip

http://download.laptop.org/xo-1/os/official/703/jffs2/os703.img 

only on the USB.

Now the XO does not even see the local router (still setting in the same room). Radio is on, jabber is set to xochat.org and nothing. 

So I decided to reset the XO to build 656 using the empty USB with only the zip & img file. Still no router is seen. What am I missing?

[Lightfoot]

Ran /sbin/iwconfig and found:

lo         no wireless extensions
msh0   IEEE 802.11b/g    Nickname: "Mesh"
            mode: Repeater
eth0     IEEE 802.11b/g    ESSID:"olpc-mesh"    Nickname: "MRVL-USB8388"
            mode: Ad-Hoc

Does this mean the configuration is not correct?

Have run:
rm /home/olpc/.sugar/default/nm/networks.cfg

restarted sugar & no AP except the three meshes.

will keep researching.....

[BoBraxton]

I am interested in what you work out.

[Lightfoot]

As of yet no solution. Tried to reset local router per suggestion by several post and crashed my home network, YUK....

We have two routers acting as master & slave to reach across the house. When I went to reset the one router, somehow both reset and now can not see the internet connections. Today I by-passed the routers & connected directly to the cable modem to check my email!!!

Need to travel to a Hot-Spot to see if the XO will pickup. Still unsure if it is hardware or software. Will post more later.

[Lightfoot]

I am at my wits end. - Someone please help.

My XO cannot see any hot spots. I sat in a hot spot and only saw mesh 1,6,11 in the neighborhood.

I have tried every trick I could find on these forums, both at olpcnews.com/forum & wiki.laptop.org.

Tried the following:
rm /home/olpc/.sugar/default/nm/networks.cfg
rm /home/olpc/.sugar/default/:
       config
       owner.key
       owner.key.public
/etc/init.d/network stop
/etc/init.d/network restart
sugar-control-panel -s jabber xochat.org
sugar-control-panel -s radio on
manually reset WEP:
/sbin/iwconfig eth0 essid <name> mode managed key <long number>
/sbin/dhclient eth0

What else is there to do? I really enjoyed working on the XO. When it stopped seeing my Linksys Router I reset the router. Upgraded the firmware on the router. My three PCs can get out on the WEB. The XO does not see the router. I can not tell if it is even looking.

Being new to linux, though can work with most low level PC problems, this is a real struggle to learn the ins & outs. Is there a simple list of criteria required to have the XO see access points? Who would know that the XO jabber setting needed to be changed from the null setting it comes with in order for others to show up in the network? All of the forums & wiki.laptop.org discussions assume when you turn on an XO there are people in the neighborhood. What else should we know to make things work?

If anyone has suggestion I am all ears.  Thanks in advance.

[Dinky]

I don't have an answer, but let me give you my settings and what  I see (build 650).

I am running a Linksys WAP11, version 2.8.  This is an old a/b system but information may be useful.

When xo connected, I see (with /sbin/iwconfig) both mesh0 and  eth0.  For eth0:

eth0       801.11 b/g       ESSID:  kitty  Nickname: MRVL-UB8388  (kitty is my access point)
              mode:  managed
              security mode : open

When xo NOT connect, I see  both mesh0 and eth0, but the eth0 ESSID is "olpc-mesh", mode: Ad-Hoc, and  receive status Rx:  invalid . (note: eth0 may appear since previously connected to Linksys -  uncertain if present if never connected)

For my Linksys:

             AP mode:  access point                        (other choices are AP client,
                                                                           bridge,  Bridge - multipoint, repeater)
             Authentication type:   open system
             SSID Broadcast:   enabled
             Channel:   11

I use WEP with 128 hex generated with the passphrase (128 hex menu choice on xo)
I use the default speed (11 Mhz).   (note:  password is a separate parameter from passphrase)
SSID broadcast must be enabled for the xo to see wireless.
My router (address 192.168.1.1) is set to supply dhcp.
The xo does not work with my old Linksys BEFW11S4 wireless router.

I have summarized my previous comments under the Jabber topic: G1G1 first time jabber user. 

PS:  If nothing works, will send you USB to LAN adapter (loan) to eliminate possible bad xo radio.
     

[Dinky]

Came across wiki article that notes problem with Linksys WRT54G with later firmware versions. Reposting it here since it may bear on this problem.

http://wiki.laptop.org/go/Mesh_and_WDS

This was also referenced in:

 http://olpcnews.com/forum/index.php?topic=207.msg1897#msg1897

Use iwlist to look at local wireless nodes:

http://olpcnews.com/forum/index.php?topic=2151.msg19458#msg19458

These may be helpful:

 http://olpcnews.com/forum/index.php?topic=2026.msg22107#msg22107
 http://olpcnews.com/forum/index.php?topic=2217.msg17449#msg17449
 http://olpcnews.com/forum/index.php?topic=2746.msg15844#msg15844

Recent post:  (which refers to wiki with comments about problems with WRT54G):

http://olpcnews.com/forum/index.php?topic=3198.msg24844#msg24844

Seaching on "WRT54G"  gives exampes of user problems with this wireless router.

[mary]

Being new to linux, though can work with most low level PC problems, this is a real struggle to learn the ins & outs.

Lightfoot, I feel your pain. It's very frustrating to know that you could easily solve the same problem on a PC, and you know the Linux answer can't be out of your grasp - but it seems there's one tiny piece of information that's eluding you - you know what you need to do - you just don't know how to do it.

Anyway - I'm having connectivity problems myself. I've managed to completely confuse myself with all the different advice on the forums and in the wiki.

However, for a little info on troubleshooting the network config,  I found an obscure (to me - I hadn't seen it before, and I've looked at lot) wiki page. It's at http://wiki.laptop.org/index.php?title=Test_Network_Configuration.

It functions as a kind of checklist, along with a little info on what you are checking for. In my case, it at least gave me some idea of what and/or where the problem might be, so that I know what - from the plethora of information and advice out there - might help. It sure seems like there are a lot of pieces that need to go together just right for things to work - and since every setup and situation is different, it's hard to know exactly what to try, especially since I don't like running commands unless I have some idea of what they do. 

I'm suspecting you may have a combination of things going on. I have a couple of thoughts, but why don't you read that page and see if it helps any. Let me know - I have a lot of notes on what I've done. I just haven't had the time to consolidate the information into any kind of helpful (even to me) list.

BTW
My problem is I can get my wifi working and then somehow manage to break it again - seems everytime I change an access point, things go haywire. So I get a lot of practice restoring it. (although currently I've lost all the mesh people)

[Dinky]

Mary:

Have you looked at:

http://wiki.laptop.org/go/Mesh_and_WDS

the section : Interactions Between XO's and Other WDS Other nodes

which talks about problems with newer wireless nodes using "lazy WDA"   ?

Thought it was worth mentioning.

[mary]

Hi Dinky -

Thanks for the link. It was an interesting read - now I have even more info tumbling around in my brain! I hadn't even heard about "WDS" - and of course I have the (common) Linksys router. Need to mull on this a bit - the info seems to fit in with something I read or did earlier. The puzzle pieces are spread around me - I just can't seem to get them to fit consistently!

I'm going to go back through some of the other links you posted above.

m