There won't be any difference in the chipsets between the XB6 and XB7. As far as I'm aware, there hasn't been any new chipsets designed by Broadcom or Maxlinear, who bought out Intel's Home Connected Division. Broadcom is possibly designing and fabricating the next DOCSIS 4.0 chipset, Maxlinear, who knows, given the recent take-over.
As has been pointed out, the XB6 has 8 antenna for 5 Ghz purposes versus the 4 antenna on the XB7. For that reason, I'd expect the XB6 to provide better wifi performance.
Now, if your interest is in the 2.5 Gb/s port, then the XB7 is definitely the preferred modem. With that, you'd have to have a 2.5 Gb/s port on a pc, switch or router in order to take advantage of the modem's 2.5 Gb/s port. I've seen a post where a speedtest, modem to pc via the 2.5 Gb/s port topped out at 1.2 Gb/s. The best that you're going to see on a gigabit port is about 940 Mb/s.
- last edited on by
RogersCorey
Hi.
This morning around 3:30am my XB7 rebooted on its own.
When I called Rogers Tech Support, they confirm there was a firmware upgrade causing the modem to reboot.
1. Can some confirm the below is the latest firmware?
2. I noticed there the following thread ... is there a similar one for the XB7, and if not, may we start one?
I figure the XB7 will have its own unique list of features and issues that merit discussion.
XB6 Modem Settings/Requests/Firmware Discussion
@SpeedyC wrote:
Say we can't log into 10.0.0.1 nor the app ... how can we factory reset the XB7?
Press and hold (and keep holding) the WPS button until the XB7 resets.
One more thing: if you are trying to break your link with the Ignite WiFi Hub back-end, apparently you need to perform the initial setup, using a web browser, IMMEDIATELY after the gateway comes back online... and you need to very quick and get this done before the back-end restores the previous configuration.
Without the cable connection, the modem most likely won't boot. At boot-up, the modem downloads a config file that it needs to operate. Without that file, the modem shouldn't boot.
Maybe the solution is to run a factory reset and the instant that you see the set up page, disconnect the cable and see if the set up will run to completion. Then reconnect the cable.
@ColdGranite wrote:
Is it okay to take the XB7 (or XB6) off the cable, reset it and configure it while off cable, then reconnect the cable? Will that break the link with the wifi hub?
This is certainly worth a try.
@Datalink wrote:
Without the cable connection, the modem most likely won't boot. At boot-up, the modem downloads a config file that it needs to operate. Without that file, the modem shouldn't boot.
Not necessarily. Keep in mind that the XB6 and XB7 gateways are not like other cable modems in that they can also use an Ethernet port for their WAN connection. You would use this in FTTH configurations to connect the Ignite gateway to an external ONT.
If you are going to try this, make sure that you connect your computer to Ethernet Port 1. The last/highest port is used for the EthernetWAN connection so it would be best to have nothing connected to it.
Maybe the solution is to run a factory config and the instant that you see the set up page, disconnect the cable and see if the set up will run to completion. Then reconnect the cable.
This might also work as well.
Regardless of what initially allows you to regain local access to your Wi-Fi settings, what remains to be seen is whether the Ignite WiFi Hub will try to reassert itself all over again, even if you do not use the WiFi Hub mobile or web app.
@ddd12345 wrote:
However, it seems after after I have bridged, I can't get to the XB7 login page via 10.0.0.1 for some reason. So I factory reset the XBR, at this point was able to login to 10.0.0.1. Started from scratch, disabled wifi on the gateway and then enabled bridged mode. After XBR reboots, again same thing.
Everything works fine, but can't get to 10.0.0.1. Not so sure I should be complaining as everything works, but should always be good to understand why.
Do you have your Linksys Velop configured to use 10.0.0.x on its internal network? If so, that's why.
@ddd12345 wrote:
Thanks, but not sure I understand. Can you help/explain how I go about checking this.
Thanks
With the default settings, Linksys equipment uses the 192.168.1.xxx IP address range on its Local Network. With that configuration, you should still be able connect to 10.0.0.1 and connect successfully the Ignite gateway. However, if you reconfigured the Velop to use 10.0.0.xxx locally, then connections to 10.0.0.1 will never make it beyond your local network and will never get routed to the Ignite gateway.
-
88964 views
-
36 Likes
-
-
