I guess it's the definition of problem. For me, my old router settings didn't have to change, and it's WAN port connects to the Ignite router on the LAN side. Anything connecting to Ignite gets a 10.x.x.x address (including TVs and the old router),...
Double NAT is used, and there isn't any issue that needs solving. A private router on the original IP subnet is a solution to the Ignite Guest mode problem (yes it's a painful problem). It's just the burden of administering the private router and r...
"Not this time around" in my reply above refers to using bridge mode on the Rogers router (in response to darthwolf). In the past it was true that bridge mode was required to use a private home router, but the Ignite router now allows this with sepa...
Not this time around. The ignite gateway was installed by Rogers, and they configured it with a separate SSID, which is required by the TV boxes. WiFi users can choose the new SSID, which is supported by extenders so has greater range, or the old S...
I'll describe how it works for me. It's close to Eddiepet's diagram option 2, but the smart home devices are fully on the legacy WiFi. The Rogers Gateway is of course at the top, and it did not need any configuration. The second router has the gue...
