Test Config Notes: Difference between revisions
Jump to navigation
Jump to search
m (wikify link) |
|||
Line 1: | Line 1: | ||
===Turn on All logs=== |
===Turn on All logs=== |
||
[[OLPC Trial-2 Software Release Notes#Enabling logging|Enable logging]] |
|||
[http://wiki.laptop.org/go/OLPC_Trial-2_Software_Release_Notes#Enabling_logging Enable logging] |
|||
===Modify the Mesh Discovery Sequence=== |
===Modify the Mesh Discovery Sequence=== |
Revision as of 16:32, 6 September 2007
Turn on All logs
Modify the Mesh Discovery Sequence
You can put the following values in /etc/NetworkManager/mesh-start
- school-mpp
- infra
- xo-mpp
- local
These will control where the _mesh_ device starts. Since the mesh device is the first device that gets picked at startup, this affects the immediate connection search of the laptop.
Remember, the current automatic connection cycle is this. You can jump to a specific step in this cycle by putting the string above into mesh-start.
/* Steps: * * 1. For each channel in [1, 6, 11]: * a. try DHCP * b. if DHCP times out, try next channel * c. if DHCP response includes a non-link-local IP address, * then CONNECTED/DONE * * 2. Try last successful AP connection * a. if success then CONNECTED/DONE * * 3. For each channel in [1, 6, 11] * a. try DHCP * b. if DHCP times out, try next channel * c. if DHCP response includes a link-local IP address, * then acquire autoip address and apply DHCP settings (except for * IP address), CONNECTED/DONE * * 4. Jump to channel 1 * a. acquire autoip address, CONNECTED/DONE */