Configuring Local Subnets
When a Local Subnet is enabled, the standalone AP serves as a gateway router with the ability to manage its own subnets, providing DHCP server and DNS cache functions for both wired and wireless clients. These clients can be assigned private IP addresses from a user-defined address pool. Traffic from the client station in private address space appears on the outside as if generated by the AP itself.
In this way, the AP performs Layer 3 packet forwarding not only for Hotspot/WISPr usage, but for standard usage as well.
Up to four IP subnets can be configured per AP, each with its own address range, which cannot conflict with one another.
- Go to Configuration > Local Subnets. The four tabs at the top (Local Subnet 1 - 4) allow you to configure each of the four subnets independently.
- Click Enabled next to Subnet. The local subnet configuration options appear.
- In Local IP Address, enter an IP address for the gateway. The default address for Subnet 1 is 192.168.40.1. This address can be used to access the AP's web interface for configuration and monitoring from devices connected to this subnet.
- In Subnet Mask, typically you would want to leave the setting at its default value (255.255.255.0) for a Class C subnet with an address pool of up to 254 addresses. An error appears if you enter an invalid IP/netmask combination.
- In DHCP Server, click Enabled if you want to enable DHCP for this subnet. Starting Address and Maximum DHCP Users fields appear.
- In Starting Address, enter an address in the same subnet as the Local IP Address (e.g., 192.168.40.2).
- In Maximum DHCP Users, enter the maximum number of clients that can be assigned addresses by DHCP in this subnet (valid values are 1-253 if the default subnet mask is used).
- In Access VLAN, enter a VLAN ID to segment client traffic arriving from this subnet from other network traffic. (Example: if you use the default 192.168.40.1 address range, you may want to use "40" as the VLAN for this subnet.)
- Click Update Settings to save your changes. The local subnet is created immediately and can now be applied to WLANs or Ethernet ports from their respective configuration pages.
_v5_GUID-29E84B4F-3F96-4605-BF2E-5DF9B244D4F4/Config-LocalSubnet=GUID-6BAA5631-5E0F-48E4-9D71-8A56DC224338=1=en-US=Low.png)