Using PPPoE and DMZ / Advanced DMZ for 'Bridge Mode' use of 3rd Party router on the HH4000 & Giga Hub

navderek
Contributor II

It would be great if Bell could confirm if they are going to update the FW on the HH4000 to enable a true bridge mode setup...also to stop the Wifi from automatically re-enabling itself anytime the HH4000 reboots itself. These are two MAJOR issues right now with the HH4000 and posted about on many forums (not just here).

It would be great if someone from Bell could chime in and let the community know if it is actually going to address these issues or not? If not, please explain why and please do not point to advanced DMZ as a solution because that doesn't actually work very well and severely impacts the performance on the Google Mesh (or any other pre-existing mesh setup). This is also discussed on many forums both on this one and externally by your customers.

We do realize the HH4000 is relatively new so there can be some improvements. We, as a community, just want to know if Bell plans to make those improvements or not.

Thanks,

-Derek

 

-------------------------------------------------------------------------------------------------------------------------------------------------------

AI Summary: 

When attempting to use a third-party router, customers frequently encounter networking challenges due to the absence of a true 'bridge mode'. This limitation has led to a variety of solutions involving PPPoE and the Advanced DMZ feature to avoid issues like double NAT; where two devices on the network are performing Network Address Translation (NAT). Double NAT can lead to problems with online gaming, port forwarding, and other applications that require a direct connection to the internet.

Some complications you may experience:

  • Wi-Fi auto re-enabling: Even when disabled, the Bell Home Hub's Wi-Fi can turn back on after a reboot.
  • Advanced DMZ limitations: Advanced DMZ can be unreliable, especially with third party mesh systems. PPPoE is preferred by users in this scenario.
  • IP lease and connectivity drops: Devices lose connection when the public IP changes, requiring manual reconfiguration.
  • Performance degradation: Speeds, especially download speeds can drop over time. A reboot or modem reset will be needed to restore.
  • No static IPs: IP changes cause disruptions. Using DDNS can be considered.

In response, Bell Community users have detailed two primary methods to approximate a bridge mode: PPPoE passthrough and the use of the Advanced DMZ feature.

User-Shared Solutions:

PPPoE Passthrough: Often described as more stable and straightforward; it involves configuring the third-party router to establish the PPPoE connection directly with Bell. This effectively bypasses the Bell Home Hub 4000, Giga Hub and Giga Hub 2.0's routing functions, providing the third-party router with its own public IP address. To do this, users typically need to obtain their "b1" username and password from Bell. While stable, a significant drawback of this method is a potential reduction in internet speeds, particularly on plans faster than 500 Mbps, as many consumer routers struggle with the overhead of PPPoE.

Advanced DMZ: This method involves placing the third-party router in the modem's "Advanced Demilitarized Zone." This exposes the third-party router directly to the internet, which can result in higher performance. However, this solution is often reported to be less stable. For instance, rebooting your router might necessitate a subsequent reboot of your Giga Hub/Giga Hub 2.0 to restore the internet connection. Some have also reported experiencing lag spikes with this configuration. When using Advanced DMZ, it is advised to leave the login information on the third-party router blank, as entering PPPoE credentials can cause the connection to fail.

Configuration Tips from the Bell Community:

  • When setting up either method, it's recommended to disable the Wi-Fi on the Bell Giga Hub/Giga Hub 2.0 to prevent interference.
  • For PPPoE passthrough, connecting the WAN port of the third-party router to any LAN port on the Bell hub and configuring the router with your b1 credentials is the general procedure.
  • For Advanced DMZ, users need to enable the feature in the Giga Hub/Giga Hub 2.0's settings and assign their third-party router to it. It's also highly recommended to not plug other devices directly into the Bell hub for security reasons when using Advanced DMZ.

Ultimately, the choice between PPPoE passthrough and Advanced DMZ depends on the user's priorities. If stability and ease of setup are paramount, PPPoE passthrough is often the recommended choice. For those who prioritize performance and are willing to troubleshoot potential instabilities, Advanced DMZ may be the preferred option.

 

 

11 208 142K
208 REPLIES 208

Vanadiel
Community All-Star
Community All-Star

Are you using PPPOE on the UDM? 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

I am not. Im using DHCPv4

On the Gigahub check go to My Devices>Ethernet>Expand Advanced and make sure you didn't set a static LAN IP for the UDMP. Leave it as dynamic and then re-do the ADMZ settings and reconnect the UDMP to the HH.  Once the ADMZ is working the public IP should show in the UDMP and the HH ethernet should show as a 169.1.1.1 address but back to static.

Everything I read says that if I put my router in the Advanced DMZ it should be in front of the Modem's firewall.

This doesn't seem to be the case because I keep having to forward ports to my router. 

What's going on here or am I misunderstanding what Advanced DMZ does?

For instance, I run a few apps at my house and contact them via DNS.  I had to forward port 443 on the Bell Modem software to my router IP. This seems counterintuitive if the Advanced DMZ puts my router in front of the firewall.

Also, I tried to setup pppoe but I couldn't figure out my password. The tech left and gave me the modem access password, which I changed.  Was this supposed to be by pppoe password? Which password would it be, the original one or what I changed it too?  Neither worked.

Did you ever get an external IP?

Does this actually work to get an external address on the HH 4000? Everything I have read is that it doesn't actually work like they say it does. I have not been able to anyway...

Yes I did.

I had to set the ADMZ on the GigaHub and restart my UDMP 1-2 times before it would pick up the public IP.

Bell really needs to give us a true bridge mode feature.

Thank you for being the only helpful person on here or reddit ❤️👍

Vanadiel
Community All-Star
Community All-Star

ADMZ in my opinion is not reliable. I would much rather use double NAT than PPPOE ADMZ.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

From my understanding @mkennedy isn't using PPPOE, just ADMZ.

Yea, its a little finicky, will agree and there is some bumps in terms of latency.

But I didnt really want to put in the effort to deal with port forwarding on a double nat configuration. haha

It's the port forwarding that I'm worried about. Every day I encounter something that isn't working and I have to go forward some ports (Sonos for instance). I wanted a bridge-mode alternative, not a part-time job.

There is some information in here that explains the difference. I didnt fully read the article. Im by no means a network guy. Just a hobbyist.

https://itnerd.blog/2023/01/08/questions-and-answers-about-using-advanced-dmz-vs-pppoe-passthrough-u...

Why are you port forwarding for Sonos? I have two Arcs and Era 100's and I dont do any port forwarding for them.

Vanadiel
Community All-Star
Community All-Star

ok, I understand. Just hoping you have the correct ports opened up and the remainder closed. That's one downfall of using the public IP for your own router: you have to make sure it's secure enough to have a public IP.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.