Connecting Bell fibre directly to UDM SE with SFP+ and PPPoE

[DMot]

Has anyone connected directly to their router with an SFP and PPPoE or another method?  I'm looking for the right 10Gig SFP, but I'm not sure what one to get

I have a Ubiquitiy UDM SE gateway/router.  Currently I have a 10 Gig SFP+ to RG45 with a patch between it and the HH4K's 10G RJ45 port.  I'd like to eliminate the HH4K and go direct if possible.

thanks.

[Artikl]

Hey Vanadiel , can you please tell me wich sfp module did you use to RB5009 and how you setup them ?

[Vanadiel]

I have a home hub 3000, which comes with a removable GPON module supplied by Bell.

I removed it from the HH and plugged it directly into the SFP+ port of an RB5009. I then configured the RB5009 properly and use my B1 username and password to establish a PPPOE connection.

My HH is sitting on the shelve, as I took it completely out of the equipment loop.

I have also previously done the same thing with a UDM Pro SE, but like I said the SFP+ ports on the UDM cannot sync at 2.5 which is required for the 1.5/1 Bell profile. I think the 3/3 plan syncs at 5/5, but I could be wrong.

[B1Toroon61]

Currently have a standalone Huawei ONT with external UPS on the 1Gbps plan. I am looking to upgrade to the 3Gbps plan but was advised by Bell that this would involve a mandatory upgrade to the Gigahub.

I know Bell does have standalone XGS-PON Nokia ONTs that are installed for third party wholesale customers but Bell support is refusing to process the order with both a Nokia ONT and Gigahub (or older modem).

Is there any other channel where I can process this order so that it is fulfilled with the Nokia ONT? The end goal is to be able to fully bypass the Gigahub and connect directly to a third party router that is currently connected to the Huawei ONT. 

[dks]

Thank you for your question. The most direct answer to your question is yes, you will have to upgrade to the Giga Hub if you upgrade to the 3 Gb profile.

As you have discovered, Bell will not process an order for the Giga Hub and a separate ONT. You were on GPON with your 1 Gb profile and will be moved to XGS-PON when you move to the 3 Gb profile. The ONT is included in the Giga Hub and your separate ONT will be disabled or removed when you upgrade your profile. 

If there is an up side, the Giga Hub has a passthrough on all ports (not a true bridge mode) so by plugging a router into the 10 Gb port on the Giga Hub and moving your credentials to the router, the Giga Hub passes that traffic through. There are no issues for most consumer level internet services. Just make sure your router and computer can handle higher speeds. A 10GB network card and router will take advantage of your 3 Gb profile and be relatively future proof. 

[unlearned4231]

I'm currently using Bells 3 Gb Fibe service with a Gigahub. There are quite a few HH3000s for sale close to me, but based on the last few messages I'm not sure if I could actually just buy a used one for the GPON and get 3 Gb directly. It seems like maybe I'd be limited to 1 Gb? Is that the case?

[Vanadiel]

Different type of GPON. It will not work for a 3/3 connection. That and each equipment has a unique identifier, and if it's not registered with Bell it will not connect to their network no matter what you try.

[dks]

The simplest answer is no. Two different technologies. In addition, Bell owns the modems. Someone will get a bill and it shouldn’t be you. Stay away from Bell modems sold in the marketplace. They won’t work for you snd you will be out what you paid the vendor for it. 

[unlearned4231]

Thanks for the quick respones @Vanadiel @dks ! 

[LikesToys]

Much of the information on this forum does not really reflect the current hardware/ Firmware that Bell provides in April of 2025.  For example the current hardware Bell supplies in Ontario is the 04/2025 is the Giga Hub (GH) firmware 2.13.

PPPoE is not supported.  After a lot of wasted time and research I produced a guide to setting up an external switch (in my case a Ubiquity UniFi switch) connected to a Bell Giga Hub with an external Public IP address and DMZ/ADMZ. This eliminates the double NAT issue.  

Although this guide it is customized for Ubiquity to address some compatibility problems between it and the GH the concepts should apply to many home switches attached to a GH.

Please feel free to reach out if you have any difficulties or see some problems with the guide.

[LikesToys · Accepted solution]

Article without screens: 

April 2025 - Version 1

For those dealing with the Bell Giga Hub in 2025 - be aware that Bell only supports DMZ in Ontario.   PPPoE has been removed from the firmware.  There are many out of date discussions regarding double NAT, PPPoE and DMZ.  This paper discusses the remaining options as of April 2025.

Depending on your needs, the best option (easy and faster speeds) may be to configure the UDM and attach the GH to the 10Gps port and live with double NAT.  This may produced the best speed.  If you can’t live with double NAT then read on.

You should be aware that if you turn on DMZ with the GH 2.13 firmware, Ubiqiti Gateways don’t provide Internet access without a Routing settings adjustment (described below).   

My Current Hardware

Bell Giga Hub - Firmware 2.13 - 3Gbps, Public IP Address (not a paid static address)

UDM-SE - Network 9.0.114 - Zone Firewall Polices

Note: as various IP addresses will change as you make settings changes you should be able to reach your equipment via the following IP addresses during and after implementation:

• Bell GH: 192.168.x.1 where x is the first available VLAN ID not in use on the UDM.  In my case VLAN 2 was not being used so my GH was 192.168.2.1
• UDM-SW: 192.168.1.1 

Problems: Bell’s Implementation of the Giga Hub (GH) does not support Bridge Mode (corporate greed - surely not) nor do they support PPPoE therefore in order to avoid double NAT the only choice I am aware of is DMZ.  Some services that I wish to use such as Wiregard VPN or Roon ARC do not work due to lack of Public IP address and double NAT so that left me with only DMZ.

Solution: Use DMZ in conjunction with Advanced DMZ (ADMZ).  ADMZ causes the GH to send the current public IP address to the UDM for it to use as the WAN IP.  The GH does this by using the MAC address of the UDM’s WAN port so this will have to be established first.  A Routing change is also required on the UDM.

Step 1 - Connections:  Using DMZ and ADMZ, the GH passes the public IP address using the MAC address of the UDM-SE WAN Port.  If this is not a new install, simply pluggin the GH into the UDM, the UDM will likely show this connection as WAN2 and insist when you pull out your old ISP wire you just failed over from WAN1 (your old modem).  You may need to turn off WAN1 and redefine the GH port as WAN1 to get rid of this failover message.  Fixing the port speeds and definitions before proceeding is important as the WAN1 MAC address will be used in subsequent steps.

In my case, I move from Cogeco 1Gbps using UDM ethernet port 9 to a Bell 3Gbps using UDM SPF+ port 10. I also need to adjust the speeds of the ports and set up Port 10 as the primary WAN port.  Temporarily turning off port 9 allowed me to make the settings changes on the UDM Ports screen assigning WAN to port 10 (Blue Cat6E) and WAN2 to port 9.    

I assigned WAN2 port 9 to be used as a poor mans WAN failover using an iPhone.  I will make a separate posting regarding using a iPhone with power from a UPS for the entire house WAN backup.

Note: I am sticking to Ubiquiti SPF+ equipment as cheaper alternatives stated they worked with Ubiquiti but did not for me.

Step 2 - Routing: As mentioned UNIFI does not work with ADMZ turned on until a minor Routing change is made.  I don’t think it matters what you do first but basically the UDM and the GH need to both be changed and during the process UNFI will not provide internet access.  I would use the local IP addresses I noted at the beginning of this article.

Add the following Static Routes to the UDM which assigns traffic back the the WAN port: 

Step 3: Determine WAN MAC address:

On the UDM: Select UniFi Devices (on the far left) > select the UDM > Overview (blue icon below) and scroll down to WAN1 and take note of the IP and MAC address.  Note this WAN1 MAC address must be to configure the GH, not the UDM’s MAC address.  Scroll down! 

Step 4: On the GH - (192.168.x.1)  Select Advanced > turn on DMZ.

Scroll though the list of MAC addresses or manually add the MAC address - it should populate in the Active Device.

Turn on Advanced DMZ - take note of your Public IP Address.   If all goes well it will populate into the UDM.

Save the settings. 

Step5: Restart the UDM. 

Step6: Testing

Settings>Internet.  When the UDM reboots the IP address of the WAN should be your public address and you should have browser internet access. 

 i

[dks]

Thank you for your comprehensive explanation. Bell has never offered a static IP on their consumer internet. Some third party providers may, but Bell reserves static IP services for business internet.

To the best of my knowledge, Bell has never offered a true bridge mode in their modems, for technical reasons. Users with a separate ONT were able to bypass the hub, but when the Giga Hub was introduced, the ONT was incorporated into the hub and the separate ONT was dispensed with. The Giga Hub has a PPPoE pass through, which some users have had success with. I suspect that some equipment works better than others. 

Finally, Bell does not support user provided equipment connected to the Hub. That is why this user to user forum is helpful. Thanks again for your post.. 

[LikesToys]

I am confused when you mention PPPoE as my GH does not include that as an offering.  Is it other variants of the Bell hubs that include PPPoe or am I missing something?  Same goes for Bridge mode - can I simply request they turn it on even though I am a Consumer customer ?

I also notice that there are youtube videos that state pushing the OK and Reset button sets a GH into Bridge Mode - but every time I try that the GH resets to factory settings.  All makes me feel frustrated.

[dks]

Thank for your questions. If you are in Bell Aliant territory, you use DHCP and not PPPoE. The alleged “bridge mode” trick is exactly that. There is a bootleg Python script out there that apparently works, but results again are varied, at least from what I have seen. Bell will not “turn on” bridge mode for non-business customers making that request. And not everything you see on YouTube is always accurate. 

[Vanadiel]

If you use Bell Aliant as internet provider you will be using a home hub and DHCP.

If you use Bell as an internet provider you will be using a home hub and PPPOE.

Establishing PPPOE connections using third party equipment is not officially supported by Bell, so your mileage may vary on it working or not.

My understanding is they reserved third party PPPOE connectivity for business accounts, as the average home user will be using the connection as it is provided by the home hub rather than adding third party equipment into the equation.

[Dan184]

Thanks BellPatrica, I followed your instructions and was able to do everything listed, and it does work except I cannot reach my router from a public IP, and my WAN1 shows the Bell modem's private LAN IP (in my case, 192.168.2.10), not my public IP. I am able to get on the internet but it appears I am still double-NAT'd. 

But at the end of your Step 1 section you mention "Add the following Static Routes to the UDM which assigns traffic back the the WAN port: " but nothing is listed; it just goes to step 2. Are there some static routes I am suppose to add, on the modem or UDM Pro? 

Thanks in advance!