diff --git a/arednGettingStarted/_images/wifi-as-wan.png b/arednGettingStarted/_images/wifi-as-wan.png index ead533a..8417cd2 100644 Binary files a/arednGettingStarted/_images/wifi-as-wan.png and b/arednGettingStarted/_images/wifi-as-wan.png differ diff --git a/arednGettingStarted/_images/wifi-internet.png b/arednGettingStarted/_images/wifi-internet.png new file mode 100644 index 0000000..7eaf1bf Binary files /dev/null and b/arednGettingStarted/_images/wifi-internet.png differ diff --git a/arednGettingStarted/_images/wifi-noConn.png b/arednGettingStarted/_images/wifi-noConn.png new file mode 100644 index 0000000..b924ac5 Binary files /dev/null and b/arednGettingStarted/_images/wifi-noConn.png differ diff --git a/arednGettingStarted/_images/wifi-noInternet.png b/arednGettingStarted/_images/wifi-noInternet.png new file mode 100644 index 0000000..6770e4e Binary files /dev/null and b/arednGettingStarted/_images/wifi-noInternet.png differ diff --git a/arednGettingStarted/advanced_config.rst b/arednGettingStarted/advanced_config.rst index 8766e96..de28a09 100644 --- a/arednGettingStarted/advanced_config.rst +++ b/arednGettingStarted/advanced_config.rst @@ -117,19 +117,32 @@ The :abbr:`WAN (Wide Area Network)` interface on your node is typically used to If you are not going to use the WAN interface on your node, you can select *disabled* from the *Protocol* dropdown list. If you will be using your node as a *Tunnel Server*, you should reserve an IP address on your router for the node's WAN interface. This will be explained in the *Tunnel Server* section below. -When a node has Internet access on its WAN interface, that access is available to the node itself and to any computers connected via the LAN port. Checking the *Allow others to use my WAN* box will allow this node to route traffic from *all* its interfaces to/from the Internet or other external network. This box is unchecked by default because it is not desirable to route Internet traffic over the radio interface. AREDN |trade| is an FCC Part 97 amateur radio network, so be sure that any traffic which will be sent over the radio complies with FCC Part 97 rules. If you want local wireless Internet access, consider using an FCC Part 15 access point instead of the node's WAN gateway. - -The *Prevent LAN devices from accessing WAN* checkbox will tell the node not to advertise that it can be used as a default gateway. This means that computers on the LAN network will lose their route to the Internet or other networks via your mesh node. This checkbox is deselected by default. If this checkbox is selected your LAN hosts will have no access to the Internet even if your node has Internet access on its WAN interface. You may need to disable the default route if your node needs to be connected to two networks at once, such as being wired to the mesh and connected to a local served agency WiFi network. - .. image:: _images/wifi-as-wan.png :alt: WiFi as WAN :align: right -As mentioned above in the *Mesh RF* section, if your node has a radio on which you have *disabled* Mesh RF and you are not using it as a LAN AP, you can enable this available radio as a WAN interface by checking the **WAN Wifi Client** checkbox. Enter the SSID and authentication string for the wifi AP that you want to connect through for Internet access. +When a node has Internet access on its WAN interface, that access is available to the node itself and to any computers connected via the LAN port. Checking the *Allow others to use my WAN* box will allow this node to route traffic from *all* its interfaces to/from the Internet or other external network. This box is unchecked by default because it is not desirable to route Internet traffic over the radio interface. AREDN |trade| is an FCC Part 97 amateur radio network, so be sure that any traffic which will be sent over the radio complies with FCC Part 97 rules. If you want local wireless Internet access, consider using an FCC Part 15 access point instead of the node's WAN gateway. -The mesh node uses "WPA2 PSK" encryption to connect to the wifi AP. The password length must be a minimum of 8 and maximum of 64 characters. If the key length is 64, it is treated as hex encoded. If the length is 0, then no encryption will be used to connect to an open AP. A single quote character must not be used in the passphrase. +The *Prevent LAN devices from accessing WAN* checkbox will tell the node not to advertise that it can be used as a default gateway. This means that computers on the LAN network will lose their route to the Internet or other networks via your mesh node. This checkbox is deselected by default. If this checkbox is selected your LAN hosts will have no access to the Internet even if your node has Internet access on its WAN interface. You may need to disable the default route if your node needs to be connected to two networks at once, such as being wired to the mesh and connected to a local served agency WiFi network. + +WAN WiFi Client + As mentioned above in the *Mesh RF* section, if your node has a radio on which you have *disabled* Mesh RF and you are not using it as a LAN AP, you can enable this available radio as a WAN interface by checking the **WAN Wifi Client** checkbox. Enter the SSID and authentication string for the wifi AP that you want to connect through for Internet access. + + The mesh node uses "WPA2 PSK" encryption to connect to the wifi AP. The password length must be a minimum of 8 and maximum of 64 characters. If the key length is 64, it is treated as hex encoded. If the length is 0, then no encryption will be used to connect to an open AP. A single quote character must not be used in the passphrase. + + To the right of the *WAN WiFi Client* label is an icon with hover text indicating the status of the WAN WiFi connection. |icon1| indicates no wifi connection to the local access point. |icon2| indicates a wifi connection but no Internet connection. |icon3| indicates both a wifi connection to the local access point and a connection to the Internet. + + After you *Save Changes* and reboot, the node will have Internet access via wifi rather than requiring a cable plugged into the node's WAN port. In fact, enabling the *WAN Wifi Client* will disable VLAN1, so Internet access will no longer be possible through the physical WAN port. Also, on the *Node Status* display you will see the **WiFi WAN Address** label and IP address to indicate that your WAN connection is using the WAN WiFi Client. + + .. |icon1| image:: _images/wifi-noConn.png + :alt: No WiFi onnection + + .. |icon2| image:: _images/wifi-noInternet.png + :alt: WiFi connection without Internet + + .. |icon3| image:: _images/wifi-internet.png + :alt: WiFi connection and Internet access -After you have saved changes and rebooted, the node will have Internet access via wifi rather than requiring a cable plugged into the node's WAN port. In fact, enabling the *WAN Wifi Client* will disable VLAN1, so Internet access will no longer be possible through the physical WAN port. Node VLANs ^^^^^^^^^^