Motorola 2.1 ユーザーズマニュアル
Chapter 2: Network Setup
• All devices are IAPs
• DHCP
enabled
• VLAN support enabled
• Management configured as VLAN 4095. A management VLAN of 4095 means
untagged. Thus when a MOTOMESH device requests an IP address for the first time
the DHCP request will come in as untagged and will be serviced by VLAN 1. Thus
the device will receive a 10.1.X.X/16 address (e.g. if the small system reference
design defaults are used). The management VLAN can then be changed to another
VLAN e.g. VLAN 24 used in the reference design. (The management VLAN would
be changed to VLAN 24 and the device rebooted. The device would then get a
10.24.x.x address).
the DHCP request will come in as untagged and will be serviced by VLAN 1. Thus
the device will receive a 10.1.X.X/16 address (e.g. if the small system reference
design defaults are used). The management VLAN can then be changed to another
VLAN e.g. VLAN 24 used in the reference design. (The management VLAN would
be changed to VLAN 24 and the device rebooted. The device would then get a
10.24.x.x address).
• Backhaul detection on – If a MOTOMESH Duo device does not detect a wired
backhaul connection it will convert itself from an IAP to an MWR. The Backhaul
detection feature is comprised of active ping and link layer detection. By default, the
IAP will ping the gateway address received in the DHCP reply. If an IAP is statically
configured then an IP address will need to be entered into the backhaul detection
settings (in the One Point Wireless Manager™ application or via the webpage
interface) for the Backhaul Detection feature to operate correctly. Improper
configuration will lead to the IAPs configuring themselves to operate in degraded
mode which is an IAP acting as an MWR.
detection feature is comprised of active ping and link layer detection. By default, the
IAP will ping the gateway address received in the DHCP reply. If an IAP is statically
configured then an IP address will need to be entered into the backhaul detection
settings (in the One Point Wireless Manager™ application or via the webpage
interface) for the Backhaul Detection feature to operate correctly. Improper
configuration will lead to the IAPs configuring themselves to operate in degraded
mode which is an IAP acting as an MWR.
If an IAP is addressed via DHCP, the gateway address received in the DHCP reply
will be used as the logical address the IAP will ping for logical backhaul detection.
If the IAP is statically configured a valid “pingable” IP address must be configured
in the backhaul detection settings or the IAP will enter degraded status and
operate as an MWR.
will be used as the logical address the IAP will ping for logical backhaul detection.
If the IAP is statically configured a valid “pingable” IP address must be configured
in the backhaul detection settings or the IAP will enter degraded status and
operate as an MWR.
Preparing the One Point Wireless Manager Server
This section describes the procedure for the installation of Red Hat Enterprise Linux ES
Version 4, Update 5 (retail box) in a configuration suitable for use with the One Point Wireless
Manager™ application in our small system reference design. While other versions of Red Hat
Linux or another Linux distribution may be suitable to use, discussion of support for other
versions is outside the scope of this section.
Version 4, Update 5 (retail box) in a configuration suitable for use with the One Point Wireless
Manager™ application in our small system reference design. While other versions of Red Hat
Linux or another Linux distribution may be suitable to use, discussion of support for other
versions is outside the scope of this section.
2-14