Most Bell Fibre subscribers hit the same wall after plugging in their own router: port forwarding is broken, VPN tunnels drop, gaming latency spikes. The culprit is double NAT — the Giga Hub does NAT on its WAN side, your router does NAT again, and they fight each other. Bell's DNS resolvers also intercept queries from inside the Giga Hub's subnet regardless of what DNS servers your router advertises. Bridge mode collapses this to a single NAT layer, hands your router a real public IP, and removes Bell's DNS from the path. This guide covers the exact Giga Hub firmware steps, DNS implications, and CLI verification.
What Bridge Mode Actually Does on the Giga Hub
Bell's "bridge mode" is not a true Layer 2 bridge — it is IP Passthrough. The Giga Hub still handles the physical WAN connection and the VLAN 35 tagging that Bell Fibre requires. What changes: the Giga Hub stops performing NAT and DHCP for your LAN, and instead forwards the public IP it receives from Bell's DHCP servers directly to a designated downstream device.
Your router then gets a real routable IP on its WAN interface and handles all DHCP, NAT, firewall, and DNS for your internal network. The Giga Hub remains reachable at 192.168.2.1 if you connect directly to it, but is invisible to normal LAN traffic.
Before You Start
- Admin credentials — username admin, password on the label on the back of the Giga Hub (10–12 alphanumeric characters).
- Your router's WAN MAC address — from the router label or its WAN status page. The Giga Hub binds the passthrough IP to this MAC.
- Connect a laptop directly to the Giga Hub via Ethernet before making changes. After bridge mode activates, the Giga Hub stops serving DHCP to your LAN, and 192.168.2.1 becomes unreachable from devices behind your router.
- A phone on cellular as a fallback while your LAN transitions.
Step-by-Step: Enabling Bridge Mode
The Giga Hub admin UI has shipped in several firmware versions. Two paths are documented below — try path A first.
Firmware Path A (late 2024 onward)
- Browse to http://192.168.2.1. Log in with admin and the label password.
- Click Advanced in the top nav.
- Select WAN from the left sidebar.
- Scroll to the section labelled Bridge Mode or Transparent Bridge.
- Toggle Enable Bridge Mode to ON.
- Enter your downstream router's WAN MAC in the Destination MAC or Bridge To field. If the field is absent or optional, leave it blank — the Giga Hub will pass the IP to the first device that sends a DHCP Discover on LAN port 1.
- Click Apply. Allow 60–90 seconds for the Giga Hub to reboot.
Firmware Path B (older builds)
- Log in to http://192.168.2.1.
- Go to My Network in the top nav.
- Click Gateway, then Configure.
- Enable the Bridge Mode toggle under the Connection section.
- Enter the downstream router's MAC if prompted, save, and allow the reboot.
Router and DNS Setup After Bridge Mode
Your router's WAN port should acquire a public IP lease within 30 seconds of the Giga Hub coming online. If it doesn't: force a WAN DHCP renew using the paths above, or power-cycle your router. Also confirm your Ethernet cable runs from your router's WAN port to LAN port 1 on the Giga Hub — the leftmost yellow port. Some firmware versions only deliver the bridged IP through port 1.
With bridge mode active, your router now owns DHCP for your LAN and controls what DNS resolvers get pushed to every device. Do not rely on automatic WAN DNS passthrough — under some router firmware this still pulls Bell's resolver addresses. Set DNS servers explicitly in your router's LAN DHCP settings. Recommended resolvers in 2026:
- Cloudflare: 1.1.1.1 / 1.0.0.1 — fast, no query logging by default
- Google Public DNS: 8.8.8.8 / 8.8.4.4 — consistent global performance
- Quad9: 9.9.9.9 / 149.112.112.112 — blocks known malicious domains
- Local resolver: your router's LAN IP if you run Pi-hole, AdGuard Home, or Unbound
Use our DNS Lookup tool to verify a domain resolves correctly from outside your network after the change, confirming your new resolver is reachable and the old Bell resolver is no longer in the path.
CLI Verification
Confirm your WAN IP is a real public IP
Check which DNS resolver your system is actually using
Test DNS resolution and NXDOMAIN interception
Common Problems and Fixes
Router WAN shows 192.168.2.x after enabling bridge mode
Bridge mode did not activate fully. Most likely cause: wrong LAN port (use port 1 only), MAC not saved, or the Giga Hub needs a full power cycle. Unplug the Giga Hub for 30 seconds, let it fully boot (90 seconds), then recheck your router's WAN IP.
Cannot reach 192.168.2.1 from your LAN
Expected in most firmware versions once bridge mode is on. To access the Giga Hub admin panel: connect a laptop directly to any Giga Hub LAN port via Ethernet, set the laptop IP manually to 192.168.2.2 / 255.255.255.0 / gateway 192.168.2.1, then browse to http://192.168.2.1.
IPv6 lost after bridge mode
Bell Fibre delivers IPv6 via DHCPv6 prefix delegation. In bridge mode your router must request the prefix on its WAN interface. pfSense/OPNsense: Interfaces > WAN > IPv6 Type: DHCPv6, request /56 prefix. Asus: WAN > IPv6 > Connection Type: Native or DHCPv6. Netgear Orbi: Advanced > Advanced Setup > IPv6 > Auto Detect. Without a working prefix delegation, LAN devices fall back to IPv4-only DNS.
Brief outage every 24 hours
Bell's DHCP leases renew roughly every 24 hours. In bridge mode that renewal goes directly to your router. Ensure the router's WAN is set to automatic DHCP renewal, not a static IP or hard-coded lease. On pfSense: Interfaces > WAN — confirm no fixed lease time in the Advanced DHCP options.
Bell support says bridge mode is unavailable
Front-line residential support frequently says this. The feature is in the Giga Hub firmware and configured entirely on your end — no Bell provisioning required. Escalate to Tier 2 or configure it yourself without calling.
Platform-Specific DNS Verification
Windows 10 / 11
macOS (Ventura, Sonoma, Sequoia)
Linux (systemd)
iOS and Android
iOS does not surface the current DNS resolver in Settings — use a network diagnostics app to verify. On Android 9+, a Private DNS (DoT) hostname set at Settings > Network & Internet > Private DNS overrides DHCP-advertised resolvers and persists across network changes. On iOS, per-network DNS profiles installed via Settings > General > VPN & Device Management take precedence over DHCP. Check both places if DNS behaviour is unexpected after the bridge mode change.
2026 Considerations: IPv6, DoH/DoT, and DNSSEC
Bell Fibre is fully dual-stack across its residential network. After restoring IPv6 prefix delegation in bridge mode, your LAN devices receive both addresses and resolvers that support both protocols will be queried over IPv6 first. If you run Pi-hole, AdGuard Home, or Unbound on a local machine, make sure it listens on the router's IPv6 LAN address as well as IPv4 — otherwise IPv6 clients silently bypass it.
DNS-over-TLS (DoT) is a standard option on routers shipping from 2023 onward. In bridge mode the Giga Hub is out of the DNS path entirely, so DoT on your router encrypts all outbound DNS without Bell's involvement. Enable it at: Asus — WAN > DNS Privacy Protocol > DNS-over-TLS; pfSense/OPNsense — Services > Unbound DNS > TLS Upstream; UniFi — Network > Settings > DNS Shield. Bell's infrastructure sees only encrypted port 853 connections.
For DNSSEC, Cloudflare (1.1.1.1) and Google (8.8.8.8) both perform full recursive validation. For local validation, Unbound handles it natively. The authentication chain is defined in RFC 4033 at the IETF, the foundational specification used by every production DNSSEC-aware resolver today.
Common Misdiagnoses
"Bridge mode broke my internet" — in most cases the internet is fine but the router hasn't renewed its WAN DHCP lease yet. Wait two minutes or force a WAN renew before concluding something is broken.
"DNS is still going to Bell after bridge mode" — your router may be relaying WAN-provided DNS automatically. Go into your router's LAN DHCP settings and set DNS servers explicitly rather than using pass-through or automatic mode.
"Bell is hijacking my DNS queries" — if mistyped domains return a Bell search page rather than a browser NXDOMAIN error, at least one device still has a Bell resolver configured at the OS level (a hard-coded DNS server in the adapter settings, or a system DoH profile). Check individual device network settings, not just the router.
"My public IP didn't change" — it may not, and that is fine. Bell draws from the same IP pool for bridged and NAT connections. What matters is that the IP now appears on your router's WAN interface. Verify with curl -s https://api.ipify.org and compare to your router's reported WAN IP — a match confirms bridge mode is working.
Preventing Recurrence
Bridge mode survives most Giga Hub firmware updates, but a Bell-pushed factory reset can restore defaults. Check the toggle at 192.168.2.1 > Advanced > WAN every few months, especially after any Bell maintenance window or unexplained modem LED changes.
When replacing your router, update the destination MAC in the Giga Hub bridge settings to the new router's WAN MAC address. Alternatively, use WAN MAC cloning on the new router to match the old MAC — supported on Asus, pfSense, OPNsense, and most TP-Link routers under their WAN configuration page — and you avoid touching the Giga Hub at all.
To revert to standard mode at any time: log in to 192.168.2.1, navigate to Advanced > WAN > Bridge Mode, toggle it off, and save. The Giga Hub resumes acting as primary NAT router and DNS relay within 90 seconds.