Skip to main content

WAN Configuration

The WAN Configuration page allows users to configure the type of connection their device uses to connect to the internet. Available options include Dynamic IP (DHCP Client), Static IP Address, and PPPoE Client.

image.png

How to Configure

  1. Login to Admin Panel and  Navigate to WAN/LAN > WAN Configuration page

  2. Use the Connection Type Dropdown to choose your desired connection type:
    • Dynamic IP (DHCP Client)
    • Static IP Address
    • PPPoE Client


Dynamic IP (DHCP Client)

  • Click Enable DHCP Client to activate automatic IP assignment.

  • Once enabled, the following information is displayed:
    • IP Address: Automatically assigned IP.
    • Gateway: The gateway address provided by the DHCP server.
    • Primary DNS: The primary DNS server assigned by the DHCP server.
    • Secondary DNS: The secondary DNS server (if available).
    • Lease Time Left: Remaining time before the DHCP lease expires.



Static IP Address

  • Fill in the fields below with the required information:

    • IP Address: Specify the static IP address for the device (e.g., 192.168.100.2).
    • Subnet Mask: Define the subnet mask (e.g., 255.255.255.0).
    • Default Gateway: Enter the gateway IP (e.g., 192.168.100.1).
    • Primary DNS: Input the primary DNS server (e.g., 8.8.8.8).
    • Secondary DNS: Input the secondary DNS server (e.g., 8.8.4.4).

  • Click Save to apply the settings.



PPPoE Client

  • Input the following details provided by your ISP:
    • PPPoE Username: The username provided by your ISP.
    • PPPoE Password: The corresponding password.
    • Service Name: (Optional) Specify the PPPoE service name if required.

  • Click Save to enable PPPoE connection.

  • Once connected, the following status details will be displayed:

    • Status: Connection status.
    • AC Name: Access concentrator name.
    • MTU: Maximum Transmission Unit size.
    • Local Address: IP address assigned to the local device.
    • Remote Address: The remote server's IP address.
    • Uptime: The duration of the active PPPoE session.




ControlX Dual-WAN Configuration

The ControlX CTRX-110 Dual-WAN Hotspot Gateway model supports additional WAN configurations, including dual WAN setups for Load Balancing and Failover.

image.png


Select Connection Type
Use the Connection Type Dropdown to choose your desired connection type:

      • Dual WAN - Load Balance (Static IP Address)
      • Dual WAN - Failover (Static IP Address)

Dual WAN - Load Balance mode

  • Configure both WAN1 and WAN2 with static IP settings:

    • WAN1 IP Address, Subnet Mask, Default Gateway, and DNS settings.
    • WAN2 IP Address, Subnet Mask, Default Gateway, and DNS settings.

  • The device intelligently distributes traffic across both WAN connections using PCC (Per Connection Classifier), ensuring each connection is routed through the most available gateway for optimal bandwidth utilization. 

You can customize the distribution ratio percentage using the slider, selecting from 25/75, 50/50, or 75/25 to match your specific network requirements.



Dual WAN - Failover mode

  • Configure WAN1 as the primary connection and WAN2 as the backup:
    • WAN1 IP Address, Subnet Mask, Default Gateway, and DNS settings.
    • WAN2 IP Address, Subnet Mask, Default Gateway, and DNS settings.

  • The device will switch to WAN2 if WAN1 becomes unavailable.

     

Considerations for Dual-WAN Configuration

For both Load-Balance and Failover modes, it is essential to ensure that the networks for WAN1 and WAN2 are not within the same subnet. Configuring both networks in the same subnet can cause routing conflicts and lead to connectivity issues.

Example:

  • WAN1 Configuration:

    • IP Address: 192.168.1.2
    • Subnet Mask: 255.255.255.0
    • Gateway: 192.168.1.1

  • WAN2 Configuration:

    • IP Address: 192.168.2.2
    • Subnet Mask: 255.255.255.0
    • Gateway: 192.168.2.1

By ensuring WAN1 and WAN2 are in different subnets (e.g., 192.168.1.x and 192.168.2.x), the device can effectively manage traffic and avoid conflicts during Load-Balance or Failover operations.






Back to top