Overview

The operational mode of a customer ONT (Optical Network Terminal) fundamentally dictates how traffic is handled at the network edge. Bridge Mode passes traffic transparently to a downstream router, while Router Mode enables the ONT to perform Layer 3 functions such as NAT, DHCP, and firewall duties. For B2B telecom deployments, selecting the correct mode impacts optical module compatibility, maximum throughput, backplane capacity, and overall network architecture. This FAQ addresses the most common pre-sales and post-sales questions from network architects and engineers.

Frequently Asked Questions

Q1: What is the core difference between Bridge Mode and Router Mode on a customer ONT?

Bridge Mode makes the ONT a transparent Layer 2 device that forwards all traffic directly to a downstream router or firewall without performing NAT, DHCP, or routing. Router Mode enables the ONT to act as a Layer 3 gateway, handling NAT, DHCP, DNS, and firewall functions itself. In Bridge Mode, the downstream router receives the public WAN IP, while in Router Mode the ONT owns the WAN IP and assigns private IPs to LAN devices. For B2B environments requiring advanced routing, VPN termination, or granular firewall policies, Bridge Mode is typically preferred.

Q2: Which mode supports higher maximum throughput in Gbps?

Bridge Mode generally delivers higher maximum throughput because it avoids the CPU-intensive NAT and routing overhead of Router Mode. In Router Mode, throughput is limited by the ONT's CPU and NAT session table size, often capping at 1-2 Gbps for many enterprise ONTs. Bridge Mode can achieve line-rate performance up to the optical interface speed, such as 10 Gbps or 40 Gbps, depending on the ONT model and backplane capacity. For multi-gigabit B2B services, Bridge Mode is the recommended configuration.

Q3: How does the ONT backplane capacity differ between Bridge Mode and Router Mode?

The physical backplane capacity remains identical in both modes, but the usable throughput differs significantly. In Bridge Mode, the backplane is used purely for Layer 2 switching, achieving near-theoretical maximum. In Router Mode, the backplane must handle Layer 3 lookups, NAT translations, and session tracking, which reduces effective capacity by 30-60% depending on packet size and traffic profile. Network architects should verify the ONT's forwarding rate in Mpps for Router Mode to ensure it meets B2B SLA requirements.

Q4: What is the difference between this generation of ONT modes and previous generations?

Previous-generation ONTs often had limited Router Mode capabilities, such as single NAT session tables and no IPv6 support, while Bridge Mode was the only viable option for high-throughput B2B services. Current-generation ONTs now support hardware-accelerated NAT, IPv6 dual-stack, and advanced QoS in Router Mode, narrowing the performance gap. Additionally, modern ONTs offer dynamic mode switching via CLI or TR-069, whereas legacy units required firmware re-flashing or manual hardware jumper changes.

Q5: How do I configure Bridge Mode or Router Mode via CLI on a customer ONT?

To configure Bridge Mode via CLI, enter the ONT's console or SSH interface and issue commands such as 'interface gpon 0/1' followed by 'mode bridge' and 'no ip address' to disable Layer 3 processing. For Router Mode, use 'mode router', then 'ip address dhcp' or 'ip address static ' and enable 'nat enable' and 'dhcp server enable'. Always save the configuration with 'write memory' and reboot the ONT. Exact syntax varies by vendor, so consult the CLI reference guide for your specific ONT model.

Q6: Can I stack multiple ONTs in Bridge Mode for redundancy and higher throughput?

Yes, multiple ONTs in Bridge Mode can be stacked using link aggregation (LACP) or virtual chassis technologies if the ONT hardware supports stacking interfaces. This provides redundant uplinks and increases aggregate throughput beyond a single ONT's capacity. However, stacking in Router Mode is generally not supported because each ONT would require its own WAN IP and NAT domain. For B2B high-availability designs, deploy ONTs in Bridge Mode behind a pair of stacked core switches or routers.

Q7: How does redundant power failover work on an ONT in Bridge Mode versus Router Mode?

Redundant power failover operates at the hardware layer and is independent of Bridge or Router Mode. If the ONT has dual AC/DC power supplies, a failure of one supply automatically switches to the other without dropping traffic, regardless of mode. However, in Router Mode, a power failover may still cause a brief NAT session table flush, leading to temporary session drops. In Bridge Mode, failover is transparent to the downstream router, minimizing downtime. Always verify the ONT's MTBF and power failover specifications for B2B SLAs.

Q8: What optical module compatibility considerations exist for Bridge Mode versus Router Mode?

Optical module compatibility is identical in both modes because the physical optical interface and transceiver negotiation occur at Layer 1. However, in Router Mode, the ONT's CPU may limit throughput if the optical module exceeds the routing capacity, such as a 10G SFP+ module in a 1G-capable Router Mode ONT. In Bridge Mode, the same module can achieve full line rate. Always verify that the ONT's optical module compatibility list includes your specific SFP, SFP+, or QSFP28 transceiver and that the mode supports the required throughput.