Please note: I have posted a update on the HH3000 configuration here.
I switched to Bell Fibe services (Internet and TV) after many years with Rogers. In my experience, the Rogers Ignite service worked well but the TV service with the NextBox 3.0 was just awful. The many problems with this service are well documented and I won’t get into it here. Being a techie at heart, I wanted to enjoy newer home entertainment technology and Bell seems to be the current leader here in Ontario, Canada. There is a rumor that Rogers will be launching IPTV sometime in 2018 but I wanted the new tech now. First off, no more physical cable running throughout my house. The Bell television receivers are all wifi capable (ethernet is also available) which means that I can conveniently move my receivers and televisions around the house without any hassle. Depending on your perspective, the only downside to the Bell service is that the Home Hub 3000 is required to manage delivery of all services: Television, Internet and Phone.
I have fiber to my house to the HH3000 (FTTH). I measured a sustained 286Mbps download speeds and low ping times with a laptop connected directed to the HH3000. Sweet. Do I really need that speed? Probably not. Netflix only requires 5Mbps per HD stream. My home network setup is centered around Ubiquiti EdgeRouter X for routing and security and Ubiquiti UniFi AP for wifi services. With my previous setup, the Rogers router was placed into bridge mode (wifi disabled) and my own router handling wifi duties. I had similar plans for the Bell router.
The new Home Hub 3000 from Bell does not have a bridge mode. Although I found many posts online that suggests that the HH3000 supports pppoe passthrough, I was unable to get it working with my Bell B1 username and password. A ppp session is being established but then it disconnects with the following error: LCP: timeout sending Config-Requests.
The HH3000 does not support a bridge mode. You have to enable the Advanced DMZ by navigating to the advanced configuration menu. According to the Bell service manual provided to their installation technicians, the Advanced DMZ feature available on Bell Aliant Actiontec routers provides an alternative to RFC 1483 Bridge Mode deployment. This feature delivers the functionality which is usually sought after in a Bridge Mode configuration while maintaining compatibility with service offerings and support capabilities. Enabling Advanced DMZ on the HH3000 allows my router to obtain the HH3000’s WAN IP address and receive every packet received on the router’s WAN interface (just like being in bridge mode). Packets to and from my router in the Advanced DMZ won’t need to be modified as they traverse the firewall since they were constructed using the WAN IP address to begin with. This configuration is the preferred method since it allows Bell to maintain management of the HH3000 to reset, push updates, etc. The HH3000 sits outside of my LAN and has no visibility into my home network.
I have had this new setup for a few weeks now and it seems to be solid:
- Disabled wifi on the HH3000 since my home wifi is managed by the Ubiquiti EdgeRouter X.
- Enabled firewall on the HH3000. Never hurts to have multiple layers of security.
The Bell Fibe TV service makes use of a separate network on the HH3000 and is not affected by disabling the main wifi service. I have had this new setup for a few weeks now and it seems to be solid.
The Advanced DMZ function of the Home Hub 3000 no longer works for me. A WAN IP address is assigned but nothing is being forwarded by the HH3000. I also tried pppoe and was able to authenticate and get a WAN IP assigned. However, just like the Advanced DMZ, nothing is being forwarded. The HH3000 only works with the Advanced DMZ disabled. There are references to this issue on other forums such as http://www.digitalhome.ca/forum/192-bell-aliant-home-phone-internet-iptv/281945-home-hub-3000-advanced-dmz-not-working.html. I am setup with a “double NAT” situation but I do not run any services that are adversely affected.