Talk:Wifi Connectivity: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
Line 43: Line 43:
In Gnome, editing of a connection is offered but the Save button is inactive. To change a connection, it should be deleted and recreated? I don't use Sugar and can't offer a suggestion there. Regards, ... [[User:Peasthope|Peasthope]] 14:08, 27 June 2014 (UTC)
In Gnome, editing of a connection is offered but the Save button is inactive. To change a connection, it should be deleted and recreated? I don't use Sugar and can't offer a suggestion there. Regards, ... [[User:Peasthope|Peasthope]] 14:08, 27 June 2014 (UTC)
:I've removed much of the older text, because, as you say, most of it was way out of date. The page isn't for troubleshooting, there's a different page for that. I've checked in Gnome on 13.2.0, the save button is active for any connection. You would need to provide more information about the connection you can't edit; when was it made, what is in it? You can find the underlying file in /etc/NetworkManager/system-connections/ directory. Without knowing the cause of the save button being inactive, I couldn't speculate on what you could do to fix it. --[[User:Quozl|Quozl]] 02:15, 28 June 2014 (UTC)
:I've removed much of the older text, because, as you say, most of it was way out of date. The page isn't for troubleshooting, there's a different page for that. I've checked in Gnome on 13.2.0, the save button is active for any connection. You would need to provide more information about the connection you can't edit; when was it made, what is in it? You can find the underlying file in /etc/NetworkManager/system-connections/ directory. Without knowing the cause of the save button being inactive, I couldn't speculate on what you could do to fix it. --[[User:Quozl|Quozl]] 02:15, 28 June 2014 (UTC)
::The discussion about the save button was moved to [[Talk:Wifi_Troubleshooting_Guide#Editing_a_Connection_in_Gnome.2C_Firmware_q3c16.2C_Release_13.2.0|another talk page]]. --[[User:Quozl|Quozl]] 22:45, 9 July 2014 (UTC)

Latest revision as of 22:45, 9 July 2014

advice for Connecting through Actiontec

We've had trouble connecting through Actiontec. After a lot of trial and error, the following seems to work:

Go to the neighborhood page (the circle with nine dots).

The neighborhood screen will display three solid circles in the same color as your little man icon. These are mesh networks, and the XO conputer will search each one for a connection --- each one will blink in turn. If one of them stops blinking and is outined with a white circle, it is connected. THIS IS NOT WHAT YOU WANT TO DO. So hover the cursor over the white-outlined circle and an option to disconnect should appear. Click on disconnect.

In the mean time, other circles in different colors may appear on your neighborhood screen. Each one represents a wireless network, and most of them will be secured (that is, they will need a password or code). The secured networks are indicated by a tiny padlock. Most of the circles will be only partially filled with color, the amount of color indicating the signal strength.

If you are lucky enough to find a circle without a padlock that is full or nearly full of color, hover over it to make sure it's not a mesh network, then click on it. It will blink awhile, then when it is outlined in white, you are connected. Go to your home page (circle with one dot), and click on the browse icon (the globe.)

If your own Actiontec network has not yet appeared on the neighborhood screen, click on one of the secured networks. You will be asked for a password, (which, of course, you will not know.) Click cancel. At this point, your Actiontec circle should magically appear. Click on it, and if it does not need a password, wait until it stops blinking and is outlined in white. You're connected!

(It seems like clicking on any wireless circle, secured or not, is a signal to your computer to look for other wireless networks, including your Actiontec network, rather than searching only for mesh networks. The searching for mesh networks seems to continue, although supposedly you cannot be connected to a wireless network and a mesh network at the same time.)

If your Actiontec network requires a passcode, type it into the box that appears and check the hex box. Then proceed as above.

Be forewarned that you may need to repeat the search and connect process several times before you have a stable connection through Actiontec. It seems to get easier each time you connect, as if the computer remembers that's what you want to do

This message is written by an OLPC Grandma whose eyes glaze over and whose mind stops working when she collides with Geek Speak.


Baffling Access Point

I'm dismayed at the attitude taken on WiFi connectivity page. Many suggestions seem to start with the assumption that the wireless access point to which one needs to connect is under the direct administrative control of the XO owner and further dedicated to providing wireless access to XO's without regard to the configuration needs of other wireless devices, or administrative policy.

Suggesting a change to access point configuration as a solution to an XO connectivity problem masks the problem with WiFi compatibility.

If the XO was never designed (or never confirmed) to work with a wide variety of consumer-grade wireless access points, why not just say so?

An XO can connect to many access points and routers. Some are listed in Wireless Access Point Compatibility. Googling "site:wiki.laptop.org wireless" will give several links. If none of that information helps you should ask about the specific access point. Regards, ... Peasthope 13:40, 27 June 2014 (UTC)
The early difficulties were due to an immature wireless product industry not following vague standards in the same way. Since then, the standards have been refined, the qualification tests made much better, with the result that most wireless stuff works fine. I've removed much of the early text on this, it remains available in the page history. --Quozl 02:10, 28 June 2014 (UTC)

Proxy Settings do not work

http://en.forum.laptop.org/viewtopic.php?f=2&t=150578#p543444

"Troubleshooting" and "XO Setup"

Those two sections refer to "8.2.1 or earlier only" whereas in 2014, Release 13.2.0 is widely used. Presumeably some bugs were fixed and some capabilities improved since 8.2.1. Brief remarks at least about current troubleshooting and setup are appropriate.

In Gnome, editing of a connection is offered but the Save button is inactive. To change a connection, it should be deleted and recreated? I don't use Sugar and can't offer a suggestion there. Regards, ... Peasthope 14:08, 27 June 2014 (UTC)

I've removed much of the older text, because, as you say, most of it was way out of date. The page isn't for troubleshooting, there's a different page for that. I've checked in Gnome on 13.2.0, the save button is active for any connection. You would need to provide more information about the connection you can't edit; when was it made, what is in it? You can find the underlying file in /etc/NetworkManager/system-connections/ directory. Without knowing the cause of the save button being inactive, I couldn't speculate on what you could do to fix it. --Quozl 02:15, 28 June 2014 (UTC)
The discussion about the save button was moved to another talk page. --Quozl 22:45, 9 July 2014 (UTC)