WAN Handoffs and Public IP Configuration Explained

WAN & Public IP Setup Guide

For Customers & Reseller Partners

1. General WAN Connection (Private IP)

For most services (without public IPs), we provide a single gigabit copper handoff. This acts as your main WAN connection.

• Connect this to your router/firewall WAN port.

• IP assignment:

  • Dynamic: via DHCP (default)

  • Static: available—refer to your handover document for details

This link handles all standard user internet traffic.

2. Bonding Appliances Overview

We provide dedicated appliances for performance and reliability:

a. General Traffic Bonding Appliance

• Optimised for standard user traffic

• Uses DPI (Deep Packet Inspection) to bond only latency-sensitive applications (e.g., VoIP, video calls)

• Presented via a static, non-routable IP (useful for whitelisting)

b. Public IP Bonding Appliance (if ordered)

• Fully bonds all public IP traffic (e.g., VPNs, remote access)

• Uses a separate appliance to ensure consistent reliability

3. Public IP Setup (Split Tunnel)

Public IP traffic is segregated from general traffic to maximise performance.

• Handoff Options:

  • Separate physical port

  • Or dedicated VLAN in a trunk alongside user traffic

• IP Allocation:

  • Up to 5 x /32 public IPs per service

  • Each IP is presented on a separate VLAN or interface

  • IPs are not part of a contiguous block

4. Why We Separate Public IPs

• General traffic uses load-balancing + selective bonding for performance

• Public IP traffic is fully bonded for maximum reliability

• Full bonding incurs a throughput overhead, so we reserve it for:

  • Sensitive user applications

  • Public-facing services

This hybrid model ensures efficient use of 5G capacity.

5. Router/Firewall Setup Recommendations

To get the most from the service:

• Support a WAN port or VLAN for general user traffic

• Route standard traffic over this interface—DPI will handle sensitive services

• For each public IP:

  • Accept an extra copper port or VLAN in a trunk

  • Route relevant services (e.g., VPNs) to the correct public IP interface

6. Final Notes

We understand this design differs from typical fixed-line setups that use a contiguous IP subnet. However, this model ensures:

• Better performance over 5G

• Lower bonding overhead

• Reliable public IP service when needed

Need help?
Our support team is ready to assist with setup or questions.