- Community Home
- Internet
- Re: Giga Hub 2.0: PPPoE passthrough/2nd PPPoE sess...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2026 11:57 PM - edited 01-07-2026 12:20 AM
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
- Labels:
-
Giga Hub 2.0
-
PPPoE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2026 10:31 AM - edited 08-26-2026 10:32 AM
ScratchMang, I would love your guidance as I’ve been struggling to figure this out, I have the UCG Fiber that I’m hoping is more than capable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2026 10:34 AM
PM Sent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2026 10:38 AM
Very well said @ScratchMang this is exactly the answer Bell please listen to this as this is exactly what we need!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2026 11:03 AM - edited 08-26-2026 11:05 AM
What we need is someone we can speak with, even if only through these forums, who can engage with us at the appropriate technical level.
I apologize in advance if that sounds blunt, but I have worked in IT since before DHCP and PPPoE were adopted for general use. I am not looking for basic troubleshooting, nor do I expect front-line support to configure my equipment. (They couldn't anyway)
What we (The Power User Community) need is access to someone who understands Bell’s network implementation well enough to discuss DHCP behaviour, off-subnet gateways, routing and Advanced DMZ without immediately falling back on “third-party equipment is unsupported” or “this is what most customers want.” Thus far, those are essentially the only responses we have received from the call centres and Community All-Stars. That is not intended to be demeaning; it is simply the reality of the support currently available.
Bell choosing not to support our hardware is fair enough, I do not expect Bell to support or configure my equipment. However, accurately documenting Bell’s side of the connection should not be too much to ask.
Having someone available on these forums with the technical knowledge and authority to discuss configurations beyond “that isn’t supported” would likely resolve many issues and substantially reduce the time and frustration experienced by customers who venture beyond Bell’s approved support model.
Perhaps an area on the forums for "Power Users" with the caveat that any and all information contained within is NOT Supported / Endorsed / Recommended by Bell and users are playing with fire when seeking advice in this area 😛
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2026 11:03 AM
Hi ScratchMang, I’ve been using the unifi platform for several years. I’d be interested in your solution.
Thank you for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2026 05:06 PM
Because you haven't shared the steps here? Your comment saying your solution was on reddit seems to no longer be here but I have a copy in my email.
It can be found here:
"For those having issues with the aDMZ on their GigaHub 2.0
One solution, that has proven to work, is to configure 192.168.2.1 as onlink, meaning the router treats it as directly reachable through the WAN interface despite the subnet mismatch. OPNsense and pfSense call this Far Gateway and can easily be configured in the GUI. UniFi gateways, however, do not expose an onlink or Far Gateway option.
The reported UniFi workaround is to create two static routes:
Bell ADMZ Route 1
Destination Network: 0.0.0.0/1
Type: Interface
Interface: WAN
Distance: 1
Bell ADMZ Route 2
Destination Network: 128.0.0.0/1
Type: Interface
Interface: WAN
Distance: 1
Leave the UniFi WAN connection configured for DHCP.
Together, these routes cover the entire IPv4 address space and force traffic directly through the WAN interface, bypassing UniFi’s inability to use Bell’s off-subnet 192.168.2.1 gateway normally.
Also ensure that your internal network is not using 192.168.2.0/24, as that would conflict with Bell’s gateway network.
I cannot guarantee this will resolve every UniFi configuration, as behaviour may vary between models and firmware versions. My own setup has been extensively tested and is stable using OPNsense, which properly supports onlink through its Far Gateway option. The two-route configuration should accomplish the same objective."
Works great on my Express 7. Thank you for figuring this out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2026 05:12 PM
Anyone wanting the info feel free to PM Me I'll happily share my findings and help where I can. But yeah, this forum is not the place discuss Bell GigaHub issues,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2026 09:40 AM
So,
In the space of a couple of weeks, the community has managed to find and implement working solutions for the GigaHub 2.0 that work with pfSense, OPNsense, and Ubiquiti routers.
So, to the “All Stars” who repeatedly insisted that this simply could not be done, it would appear that you were mistaken.
What is considerably more disappointing, however, is the way the discussion itself was handled by the moderators. Rather than moderating the people who were actually creating the hostility and disruption, moderators repeatedly removed or censored posts from those trying to challenge the accepted narrative and work toward a solution.
At times it genuinely felt less like a technical forum and more like being told that questioning the established position was itself the problem. I knew there was a workable answer, others knew there was a workable answer, and yet resistance, dismissal, and censorship seemed to appear at nearly every turn.
Obviously, not everyone who arrives with a new idea is Galileo. But you also cannot treat everyone who challenges the accepted wisdom as though they are some kind of heretic simply because their idea contradicts what the established voices have already decided must be true. Sometimes the person questioning the consensus is wrong. Sometimes they are the person who discovers that the consensus was wrong.
That is precisely why ideas should be tested rather than silenced.
Even after 30 years of working in IT, I still learn new things almost every day. Why, then, would anyone else in this field assume they have nothing left to learn?
Admitting that you do not know everything can be a humbling thing to do, particularly when you have years of experience behind you. But the sooner you accept that there will always be something you do not know, the sooner you become open to learning far more than you ever thought possible. Experience should make us more willing to investigate new ideas, not more certain that anything outside our existing knowledge must be impossible.
That is a deeply unhealthy way to run a technical community.
Progress depends on people being willing to question assumptions, test alternatives, and occasionally prove the prevailing wisdom wrong. A forum should encourage that process, not suppress it simply because it challenges what influential members or moderators believe to be true.
“Progress is rarely made by silencing dissent. It is made by allowing ideas to be tested, challenged, and proven.”
Perhaps next time, instead of discouraging people from searching for a solution, or censoring them when they refuse to accept “it can’t be done”, the better approach would be to help them find out whether it actually can.
And, frankly, I fully expect that once the moderators see this post, it too will be removed or censored like so many of the others, because criticism of the forum’s established hierarchy does not appear to be particularly welcome here.
If that happens, it will rather neatly prove the point.
And that, in itself, is a shame.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2026 10:08 AM - edited 08-30-2026 10:09 AM
Very well said.. Let hope this forum stay open to ideas and thoughts. As another person with over 30 years experience in IT and even before I was even paid to do IT.. this type of behavior pushes the real experts away that understand and want to help Bell with these solutions. If this is not the correct place let us know so our experience and wisdom can be put to use if we want to help solve a problem.
I have an ENTIRE blog devoted to helping others when others said things could not be done or let's not talk about this or that. I was also sick of being told it can't be done by the echo chamber of support. We put a lot of time and effort into our support that is taken for granted or ignored while the next users modem just hums along because of the hard work of a few.
Open communication is the ONLY way to do this!
Let's hope this forum keep open to new ideas and thoughts that might differ!
- « Previous
- Next »
New to our forum? These guides will help you find your way around quickly.
- Welcome to the Community!
- Log in/Register
- Community guidelines
- Community help
- Meet the Moderators
- Bell Community All-Stars
- How to send a private message
- Existing customers, login to MyBell to see exclusive offers
- What's on Crave
- What's on Free Preview
- Mobility phone & device catalog
- Latest in the Community

