Connected to AP: Difference between revisions
Jump to navigation
Jump to search
m (Reverted edits by 69.41.185.162 (Talk); changed back to last version by Xavi) |
No edit summary |
||
| Line 1: | Line 1: | ||
===Getting into the Configuration=== |
|||
'''Either''' |
|||
# Go to a location where it occurs naturally. |
|||
## No [[School server]]. |
|||
# Force the laptops into it manually. |
|||
## Go to the mesh view, and connect to an AP. |
|||
## Go to the root menu in one of the terminals |
|||
## Create/Edit file <tt>/etc/NetworkManager/mesh-start</tt> on all laptops (tests should be done with at least 2 XO's and preferably 3) |
|||
## w/ text: |
|||
##* <tt>infra</tt> |
|||
## Reboot the laptop. |
|||
## The laptops will try to connect to the latest AP they were connected to each time they boot. |
|||
===Checking that laptops are in the AP Configuration=== |
|||
# The file <tt>/etc/resolve.conf</tt> should have the text: |
|||
#:: <tt>search AP_Name</tt> |
|||
#:: <tt>nameserver IP address</tt> |
|||
#:: <tt>nameserver IP address</tt> |
|||
# The laptop should have a good IP address: other checks |
|||
## Type <tt>ifconfig</tt> in a terminal. |
|||
## Second line of <tt>eth0</tt> has the address. |
|||
## If it starts with <tt>18.xx.yy.zz</tt>, or <tt>172.xx.yy.zz</tt> it is good. (<tt>169.xx.yy.zz</tt> is bad) |
|||
## The second line of <tt>msh0</tt> should have a bad IP address. |
|||
## Alternatively: the laptop should be able to browse the internet. |
|||
# The laptop should only see other XO's, which are nearby, in the mesh view. |
|||
#* in the future: should only see nearby laptops also connected to the same AP, and not those [[Connected to AP|connected to another AP]], local mesh, or [[School server]]. |
|||
[[Category:Network]] |
|||
[[Category:HowTo]] |
|||