The Critical Setup: 1) Connect your router's WAN port to port 1 (or 5GbE port) of the BGW320. 2) Open
http://192.168.1.254 in your browser. 3) Navigate to Firewall → IP Passthrough. 4) Set Allocation Mode to DHCPS-fixed. 5) Select your personal router from the Device List using its MAC address. 6) Disable Wi-Fi and Packet Filter on the BGW320, then reboot both devices.
Why AT&T Gateways Cannot Use True Bridge Mode
AT&T requires 802.1X certificate authentication between the fiber ONT/gateway and the Central Office (OLT). Because the BGW320 holds the cryptographic certificates in its hardware security module, you cannot simply unplug the BGW320 and plug your Ethernet directly into the wall. You must keep the BGW320 in the loop and enable IP Passthrough.
Detailed Step-by-Step Configuration Protocol
- Prevent Subnet Collision: The BGW320 defaults to LAN subnet
192.168.1.0/24. If your personal router also uses192.168.1.1, your network will crash. Log into your personal router first and change its LAN IP to192.168.50.1or10.0.0.1. - Access BGW320 Web GUI: Connect directly to the BGW320 via Ethernet or its factory Wi-Fi. In your browser, navigate to
http://192.168.1.254. When prompted for changes, enter the Device Access Code printed on the gateway label. - Configure IP Passthrough:
- Go to Firewall → IP Passthrough.
- Set Allocation Mode:
Passthrough - Set Passthrough Mode:
DHCPS-fixed - Click Device List and select your personal router's WAN MAC address.
- Turn Off Gateway Wi-Fi: Navigate to Home Network → Wi-Fi → Advanced Options. Turn Wi-Fi Operation to
Offfor both 2.4 GHz and 5 GHz radios. - Disable Gateway Firewall Rules: Under Firewall → Firewall Advanced, disable Packet Filtering and DoS protection (your personal router's firewall will now handle security).
- Reboot Both Units: Power cycle the BGW320 first. Once it displays a solid white light, power cycle your third-party router. Your router will now receive AT&T's public IP directly.
Beware the 8,192 NAT State Table Limit
Hardware Limitation: Even in IP Passthrough mode, all packets still traverse the BGW320 SoC state table, which is capped at 8,192 concurrent NAT sessions. Torrenting, heavy peer-to-peer applications, or large family streaming can fill this table and cause latency spikes. Keep torrent client maximum connection limits below 500.
🛡️ Router Portal Verification & Safety Standard
Our networking steps are lab-tested against standard RFC 1918 private networking protocols across Windows 11 (24H2), macOS Sequoia (15.1), iOS 18, and Android 15. We verify physical device labels and firmware release documentation before publishing gateway instructions. Router Portal is strictly read-only and never requests, intercepts, or logs router passwords.