1 ACCEPTED SOLUTION
Accepted Solutions
@LordDrakkon No, not really. Comcast designed their set-top boxes to work hand-in-hand with the gateway as an integrated turnkey solution. They do not (officially) support their set-top boxes connecting to 3rd-party network gear.
@timpayne This is going to be a constant problem for you unless you configure Ignite Gateway with the same Wi-Fi network name and passphrase that you use in your external network gear, even if you are running it in Bridge Mode.
Here is what is going on: If the Ignite set-top box loses Wi-Fi connectivity (e.g. when you upgrade firmware in your Wi-Fi router and reboot it) it will contact a service on the Ignite Gateway (via a hidden Wi-Fi network), authenticate with Rogers' back-end systems to determine/confirm the account that it belongs to, and will then obtain the Wi-Fi credentials that were configured in your Ignite Gateway. Comcast designed it this way to make it easy to install new set-top boxes -- you just power them on and they automagically connect -- and to allow the set-top boxes to seamlessly reconnect to the network if you should change your Wi-Fi password.
If you put your Ignite Gateway into Bridge Mode, its internal services are still running and the set-top box can (and will) still contact the "Lost and Found" service on the Gateway to figure out which Wi-Fi service it should connect to. If you have a different Wi-Fi name and passphrase in your network gear (and the credentials configured in the Ignite Gateway are not active on any nearby Wi-Fi network), the set-top box will drop off of Wi-Fi and will not re-connect.
If you simply configure your Wi-Fi gear with the same Wi-Fi credentials that are configured in your Ignite Gateway, the set-top box will remain connected to your Wi-Fi AP. Also, if you should ever need tech support and need to revert back to a Rogers-supported configuration, all that you need to do is disable Bridge Mode on the Ignite Gateway and power-off your Wi-Fi router.
@LordDrakkon No, not really. Comcast designed their set-top boxes to work hand-in-hand with the gateway as an integrated turnkey solution. They do not (officially) support their set-top boxes connecting to 3rd-party network gear.
@timpayne This is going to be a constant problem for you unless you configure Ignite Gateway with the same Wi-Fi network name and passphrase that you use in your external network gear, even if you are running it in Bridge Mode.
Here is what is going on: If the Ignite set-top box loses Wi-Fi connectivity (e.g. when you upgrade firmware in your Wi-Fi router and reboot it) it will contact a service on the Ignite Gateway (via a hidden Wi-Fi network), authenticate with Rogers' back-end systems to determine/confirm the account that it belongs to, and will then obtain the Wi-Fi credentials that were configured in your Ignite Gateway. Comcast designed it this way to make it easy to install new set-top boxes -- you just power them on and they automagically connect -- and to allow the set-top boxes to seamlessly reconnect to the network if you should change your Wi-Fi password.
If you put your Ignite Gateway into Bridge Mode, its internal services are still running and the set-top box can (and will) still contact the "Lost and Found" service on the Gateway to figure out which Wi-Fi service it should connect to. If you have a different Wi-Fi name and passphrase in your network gear (and the credentials configured in the Ignite Gateway are not active on any nearby Wi-Fi network), the set-top box will drop off of Wi-Fi and will not re-connect.
If you simply configure your Wi-Fi gear with the same Wi-Fi credentials that are configured in your Ignite Gateway, the set-top box will remain connected to your Wi-Fi AP. Also, if you should ever need tech support and need to revert back to a Rogers-supported configuration, all that you need to do is disable Bridge Mode on the Ignite Gateway and power-off your Wi-Fi router.
@Insainspeed wrote:
Sorry to bring an old topic back to life, but even today I'm experiencing this issue. I have XB7 in bridge mode connect to a TP-Link omada router, switch and access points. I constantly get random drops causing my two STBs to stop working and give a XRE-03090 error. Sometimes it sits there for 2-5 mins and comes back online or otherwise I need to issue a reconnect through the omada interface. Also, the ssid on the Rogers gateway is duplicated to my WLAN setup on the omada side. Really scratching my head. Any further suggestions?
XRE-03090 comes up when there is a network connectivity problem and the set-top box cannot communicate with back-end systems. It could be due to an upstream issue on Rogers' side (e.g. Rogers loses track of your IPv6 PD and cannot route traffic to you) or it could be a problem with your gear that is breaking your set-top boxes' network connectivity.
Also, the ssid on the Rogers gateway is duplicated to my WLAN setup on the omada side. Really scratching my head. Any further suggestions?
That tip is for maintaining Wi-Fi stability, to prevent your set-top boxes from dropping off of Wi-Fi. When a set-top box is unable to reconnect to Wi-Fi, you would see an RDK-03087 error message.
-
2035 views
-
4 Likes
-
-
