Giga Hub 2.0: PPPoE passthrough/2nd PPPoE session capped (average 330 Mbps) on 3 Gbps plan

[Velaris]

Hello,

I'm on a 3 Gbps plan and I'm seeing a repeatable/hard throughput cap only when using PPPoE on a downstream device (PPPoE passthrough / second session).

My setup:

- Bell Giga Hub 2.0
- Downstream router: UniFi Cloud Gateway Fiber (UCG-Fiber) connected to the Giga Hub 10G port

What works:

- If the UCG-Fiber WAN is set to DHCP (e.g. behind the Giga Hub 2.0/double NAT), I can reach full speed (~3 Gbps).
- If my PC is behind the Giga Hub 2.0 on DHCP, my PC (1GbE NIC) reaches the expected ~1 Gbps.

The problem (reproducible):

When I establish a PPPoE session from a device behind the Giga Hub, throughput is capped around ~300–330 Mbps.

Repro 1: PPPoE from UCG-Fiber

- UCG-Fiber WAN set to PPPoE using my b1 credentials
- Result: ~300–330 Mbps (repeatable), despite 3 Gbps plan

Repro 2: PPPoE from a Windows PC (bypassing UCG-Fiber)

- PC connected by Ethernet to the Giga Hub 2.0
- PC NIC: 1GbE, cable: Cat6A
- Created a Windows "Broadband (PPPoE)" connection using the same b1 credentials
- Result: same cap at ~300–330 Mbps (repeatable)

Because the same cap occurs even when PPPoE is established directly from a PC (*no* UniFi router involved), it points to the Giga Hub 2.0 PPPoE passthrough / secondary PPPoE session path rather than my router.

Can you confirm:

- Is this a known issue on the Giga Hub 2.0 (firmware-related)?
- Is there a firmware update or hardware replacement option to resolve PPPoE passthrough speed caps?

Thanks

[ScratchMang]

The truth may be uncomfortable, but my experience with Bell over the past several days has been an exercise in frustration.

I have dealt with technicians who did not understand basic networking concepts such as DHCP, along with representatives who were dismissive, arrogant, and condescending. There appears to be little accountability for either the quality of the support provided or the way customers are treated.

Bell’s decisions often seem to lack any reasonable technical or customer-service justification and instead appear designed primarily to protect revenue at the customer’s expense.

In my experience, Bell behaves like a monopoly that provides the minimum acceptable level of service while relying on poorly trained support staff and restrictive contracts to retain customers. Once my contract ends, I will be taking my business elsewhere, and I will strongly recommend that others do the same.

I have worked in IT for many years, and I intend to make people aware of how Bell operates.

I am particularly concerned about the level of access Bell maintains to customer equipment and home networks, the lack of clear disclosure, and whether customers have provided meaningful, informed consent. Hiding broad permissions inside an excessively long service agreement does not automatically make those practices reasonable, transparent, or acceptable.

[ScratchMang]

Do you have 3Gig speed or 1Gig?

[Maddjik]

3 Gbps

[ScratchMang]

Can anyone confirm if PPPoE Passthru or Bridge mode work on a GigaHub 1.0? As of Aug 2026 that is?

[Maddjik]

This is my setup and it works just fine. OPNsense firewall using PPPoE creds.

[ScratchMang]

OK, 

I'm running Opnsense on a Protectli so I'm going to see if I can get them to send me a v1.0 Anyone want to take bets on if they will?

[Vanadiel]

The forum Community Guidelines are accessible from the top side section on the right of the forum under "getting started".

Here's a direct link. 

[Vanadiel]

You might want to check for firmware version 3.11.6.3. That is new firmware being rolled out that according to user feedback resolved their PPPOE connectivity issues.

[ScratchMang]

Mine still reports as 3.11.6.2

Any sure fire method of forcing a firmware update?

[dg6464]

No, only having a Level 2 Advanced Tech Support person manually add you to the early rollout group, or push it to your modem likely at this point unless your modem happens to be in the first rollout group lot of 3.11.6.3.

I called Bell last night and am waiting on a Level 2 Tech to call me back as "none were available at this time" (fair, it was between 10-11pm).

This has been the timing on my modem of previous firmware updates, which are NOT OFTEN, so I am hoping Bell rolls this out quicker than most previous updates in the past (happening ~1 time per year, around November-December), except this last 3.11.6.2 in May (based on Gigahub 1.0 Logs):

• May 20, 2026 04:25:13 → Bell ACS/TR-069 pushed firmware 3.11.6.2.
• 2025-11-04 04:24:44–04:25:17 firmware update
• 2024-12-13 02:43:39 firmware update
• 2023-12-07 02:50:55–02:51:25 firmware update

Here's hoping Level 2 calls me back today, as Level 1 just doesn't know much about the networking world and is trained not to go off script for that reason. I was told "your modem is running the latest 3.11.6.2 firmware and is in a working state, there is no 3.11.6.3 firmware version that I can see available".

I ran a "Reset Bell Settings" from the modem to no avail.

I ran a "Factory Reset" from the GUI to no avail (it set the modem admin password to something other than what I had set and something other than the modem Serial# on the back).

I ran a "Factory Reset" by holding the button on the side of the Gigahub 1.0 for longer than the period that the screen says it's going to reset... (I held it until the screen turned off and it fully rebooted). Then the admin password was set back to the Serial# of the modem... however the issue still persisted and no 3.11.6.3 firmware was pushed, so my modem clearly isn't in the queue for rollout.

However, the Factory Resets fixed some issues of other services not showing as available on the modem (I don't use Phone or TV anyway, but they showed as working after resetting). Also... the "Speedtest" function both on the modem main panel and in the Bell Gigahub GUI was also not functioning previously... but now is working properly.

So I am hoping the Factory Reset will allow for more stable usege of Advanced DMZ than I have experience in the past (used to be "Flaky").

Will report of any major issues as I've now swapped OPNsense from PPPoE passthrough (being limited to 300-450Mbps) to Advanced DMZ (seeing full speeds).

I also verified the Double-NAT scenario (essentially just getting DHCP from the Bell modem on your Router/Firewalls WAN) provides full speeds. 

Both Double-NAT and Advanced DMZ are the same configuration on your Router/Firewall (WAN DHCP), but Advanced DMZ shares the Public IP that the modem gets directly with the Router/Firewall's WAN DHCP. You just need to get it configured properly and probably benefit from a Factory Reset beforehand to clear any other long-term modem quirks after years of firmware updates importing and re-importing older config files.

On Advanced DMZ; experiences differ based on your chosen Router/Firewall platform... because many implement DHCP leasing, Spanning Tree (STP/RSTP), Flow Control, other discovery protocols (LLDP, etc) very differently and will interact with the Advanced DMZ function in their own way (poor, mediocre or fine).

Two things I noticed after Factory Reset as well... the GUI speed was much better, as well as IPv6 showing as a toggle on the Gighub "Advanced tools and settings" under "Networking". I'm not sure if it was there before or functioning; I have not verified if it's actually being used in practice on the WAN, or just offering IPv6 leases internally to clients.

[ScratchMang]

Hmmm...

Advanced DMZ Is working you say? I'm using OPNsense 26.7.1_1-amd64 was there anything special you needed to do for the WAN Adaptor?

[dg6464]

It is worth noting... that I got here after days of troubleshooting OPNsense (using multiple hardware platforms, different 10G NIC's, tunable settings, etc), Ubiquiti/UniFi etc just to find out it was a Bell issue.

I didn't consider the Bell modem being an issue as it's been rock solid the whole time I have had the service for 3+ years.

That started with HH3000 on GPON; both with the modem using PPPoE Passthrough, as well as bypassing it using the removable Nokia SFP in my Ubiquiti 10G switch. Both rock solid.

As well as after being migrated to the Gigahub 1.0 as part of being upgraded to the 3Gbps Symmetrical service with XGS-PON (no bypass available until more recently, but no real requirement for it because PPPoE passthrough has been rock solid up until this point).

I'll be using Advanced DMZ until I get the 3.11.6.3 firmware pushed... and will report back here and other forums describing this issue as I perform testing afterwards.

Happy to anwser any questions I can or help Bell with testing new firmware revisions.

[ScratchMang]

Please let me know how Advanced DMZ works for you with Opnsense. 

From all the research I've done the Advanced DMZ has issues with dropping connections and being quite unreliable, I would be very interested in hearing about your experiences with it.

Of course, had bell not intentionally removed Bridge mode non of this would have been an issue.... 😛

[dg6464]

Will do, it's been fine all night. I had to manually enter the physical WAN interface MAC from my OPNsense Intel X520-DA2 NIC into the Bell modem's Advanced DMZ spot... as it didn't report the proper interface MAC.

Also, I am connecting the GigaHub 1.0 10Gbps Ethernet port into my Ubiquiti Switch on a dedicated WAN VLAN, as well as the OPNsense WAN port connection to the Ubiquiti switch on the WAN VLAN with that port profile.

That WAN VLAN is tied to a Port-Profile which is set to Port Mode "Infrastructure" and has everything disabled on it for:

Precision Time Protocol (PTP)

Storm Control

Egress Rate Limit

Flow Control

STP

Non-STP Loop Protection

Energy Efficient Ethernet (EEE)

LLDP-MED

Happy to answer any configuration questions, etc... but seems ok so far.

You experience may vary if connecting directly from OPNsense NIC into the Gigahub 10G ethernet port, as I've always used a switch in between for both WAN and LAN.

I'll report back if I see any instability or drops though.

[ScratchMang]

.,

You have a Gigahub 1.0, you lucky devil, I've got the much less capable and far worse  Gigahub 2.0.... Which may be the reason your having a lot more success then I am. Bell has really gone out of their way to try and prevent anyone from running anything other than their 'Approved' system and hardware.