- last edited on by
RogersTony
There have been many questions in the Rogers Community Forums lately from users who have switched to Ignite TV and now wish to enable Bridge Mode on the Ignite modem/gateway and use Ignite TV with their own routers and Wi-Fi access points. The Ignite TV service is actually pretty flexible and works great with a wide range of 3rd-party networking equipment. That said, Rogers cannot troubleshoot problems or provide any level of support for these configurations so I'm creating this thread so that we, as a community, can support each other.
I recently posted some configuration tips for setting up your own router for use with the Ignite TV service and (time permitting) will post a more comprehensive step-by-step guide. However, I still don't recommend using Ignite TV in any unsupported configuration unless you have moderately-advanced networking skills and can troubleshoot problems on your own. Also, if any technical issues should arise, you need to be able to put your Ignite TV components back into their originally-installed supportable configuration before contacting Rogers for technical support.
*** Edited Labels ***
@GarfieldTheCat The Rogers IPv6 Status thread is probably a better place to ask general IPv6-related questions.
However, the setup that you describe here is a good example of why it is NOT a good thing to cascade multiple router/firewall devices behind one another as it can cause issues that affect both IPv4 and IPv6.
In the IPv4 case, you typically have public IPv4 address (reachable from the entire Internet) on your router's WAN interface, a private address range on your internal LAN segment, the router/firewall typically performs network address translation, making it it look like connections from an internal device originate from the public IP address that is assigned to your WAN interface. It can be problematic, for some applications, when a connection traverses multiple router/firewalls. (Search the Internet for "double NAT" to see what some of these problems can be.)
With IPv6, we don't perform NAT because EVERY IPv6 device gets its own unique IPv6 address. In our case, our IPv6 router obtains an IPv6 prefix delegation from Rogers and allocates that (or a portion of it) to its internal LAN segment. One of the problems with cascading IPv6 router/firewalls is that the downstream router may only get a portion of the PD that it requests/expects and, worst case, may only be able to get an IPv6 address on its WAN interface.
All of these issues can be fixed with the proper configuration, and knowledge of what to do (and what not to do) and why... and this can also cause frustration for those with limited networking knowledge when things don't "just work".
@toolcubed wrote: I have had problems with MS Teams and Outlook on our work computers.
You are aware of the recent issues re MS365 Outlook/Teams?
@GarfieldTheCat wrote:
Currently, I have XB6 -> EdgeRouter Lite -> Devices.
Sorry... I misunderstood your post on first reading, and I was trying to explain why your configuration was not working. I also don't have firsthand experience with Ubiquiti routers, so I couldn't give you any guidance on the configuration. Please let me try again.
I still have the XB6 in "non-bridge" mode. And I setup DHCPv6-PD on EdgeRouter Lite by following instructions on another forum. Hopefully, I followed it correctly. I see EdgeRouter Lite gets an IPv6 address. But the devices that is connecting to EdgeRouter Lite, should it be getting IPv6 address now or only after the XB6 is switched to Bridge mode?
I don't know exactly how the EdgeRouter behaves but you will need to test this with the XB6 in bridge mode to see whether your router's WAN interface is getting initialized properly and to verify that the IPv6 PD is getting assigned to your internal LAN segment.
I would test as simple a configuration as possible, namely: XB6 -> EdgeRouter Lite -> Computer
and verify that the computer is getting IPv4 and IPv6 addresses assigned and that IPv6 works on the computer. Then you can expand your internal network again and add your other devices.
Also, keep in mind that your EdgeRouter Lite will now also be the device that will be securing your in-home network, so you will need to ensure that its internal firewall is enabled and that you have security policies configured and working properly for both IPv4 and IPv6.
And if one of the Devices is a wireless router. And I would need to setup the Wireless router to do DHCPv6-PD? And it should have the IPv6 address and the device that connect to this wireless router would get the IPv6 address too? I guess I would need this for the Ignite TV?
If you are using this Wi-Fi router just to provide wireless access within your home, I would actually configure it as a Wi-Fi access point. Some routers have a specific configuration option for this that disables routing and firewall functionality, DHCP, etc. and bridges the WAN and LAN segments together. Those that don't have a "bridge" or "AP mode" usually have a support page on their corporate web site that provide steps on how to do this manually. If you leave this device configured as a router and place it behind your EdgeRouter, you could still run into weird issues, and Ignite TV may not work properly either, especially if you get into a situation where IPv6 connectivity is only half-working.
Currently, I am still in non-bridge mode, and my devices, either a Windows computer or wireless router, are not getting IPv6 address from EdgeRouter Lite. I would like to make sure I have everything setup correctly before trying to turn on bridge mode. Which I currently not sure if I have the EdgeRouter setup correctly.
You are experiencing these problems because you have multiple router/firewalls cascaded, so you would be better off testing with the simple configuration that I proposed.
Thank you in advance. And sorry for all the dumb questions...
Good luck with getting this all working.
@toolcubed wrote:
Question - do the Ignite TV boxes absolutely need IPv6 or will they work fine with just IPv4?
I have never tested Ignite TV with an IPv4-only network configuration, so I can't say with 100% certainty, but I don't think that it will work fine. The only Ignite TV configuration that Rogers supports is to have the Ignite (XB6) modem in gateway mode, not bridge mode, and there is no way to disable IPv6 on the XB6 itself. Furthermore, if IPv6 connectivity "breaks" for whatever reason, I know that the Ignite set-top boxes will fall back to IPv4 but you will run into weird issues, such as channel changes taking several seconds.
@toolcubed wrote:
I've been struggling to decide whether or not to go thru with my Ignite migration, and based on a few things I've learned about the platform over the last few weeks, I'm leaning towards cancelling it and just keeping my legacy digital cable services...but I'm not 100% on that yet. However, this week I noticed something that could be a huge show-stopper for me migrating to Ignite. Up until a few days ago, I had IPv6 disabled on my Asus RT-AC68U router which I'm using with a CODA-4582 modem in bridge mode. Everything was working flawlessly until I decided to re-enable IPv6 a few days ago. Ever since then, my wife and I have had problems with MS Teams and Outlook on our work computers. With IPv6 enabled, we drop MS Teams calls every few mins, and Outlook frequently refuses to connect to our Exchange servers. As soon as I disabled IPv6 on the router today, boom! - everything worked well again. I'm not sure if it's a problem on Rogers' end or if it's my Asus router because I have not tested using the CODA-4582 exclusively (and obviously with IPv6 enabled) without my Asus router.
After enabling IPv6 on your router, did you reboot your router, then reboot your computer?
Also, when you started running into issues with IPv6 enabled, did you try testing your connectivity with any of the following sites?
... and test IPv6/IPv4-fallback with the following?
If all of the above tests okay, could your problems be due to a configuration issue on your corporate network, VPN client, etc. ... something that would cause your computer to believe that it has IPv6 connectivity to a host on your corporate network when in fact you have IPv6-related brokenness somewhere on the network path?
@Fookaroo Your computer definitely does not have IPv6 Internet connectivity. It's interesting that you do not experience any problems with Ignite TV. (The issues that I saw were the result of IPv6-brokenness, where the Ignite set-top boxes thought that they had IPv6 connectivity, then didn't handle it well when it did not work. I've never tested in an IPv4-only configuration.)
@toolcubed wrote:
1. Your existing legacy digital equipment (cable tv boxes, internet modem, home phone modem) will be useless paperweights once you’re on Ignite. If you own your cable tv boxes, you don’t need to return them and
2. might actually be able to still access any recordings you have (if any of them are PVRs) but not 100% sure about that.
1. These (if owned) may be worth something if returned to Rogers. There was a time when Rogers provided a small one-time credit. Not sure if that still holds. There are lots for sale on Kijiji or similar, so you can see what they're worth - not much.
2. Rogers will deactivate any boxes as soon as you start with IgniteTV. You would need to disconnect the RF-coax from owned PVRs before deactivation and also not let them power down. As soon as they power down, they will not reboot again at your home. Watch any recordings before you switch to Ignite.
-
141573 views
-
94 Likes
-
-
