Rogers Ignite doesn't show devices connected to LAN Ethernet port

[lovetheinternet]

I see all the WiFi devices, but it doesn't show any of the devices connected directly to the modem/router.

Is there any way to fix this?

*** Edited Labels ***

[RogersTony]

Hello, @lovetheinternet 

Thank you for posting your concern to the community.

Can you confirm if you are connecting directly to the Rogers Gateway modem or are you connecting to a router or a switch via Ethernet?

RogersTony

[-G- · Accepted solution]

@lovetheinternet  Do any of those devices obtain IP addresses through DHCP or do they have static IP addresses?  Devices with static IP addresses often do not show up in the device list; it's a quirk of the Ignite gateway's device management.  If the device is in the device list, the Ignite WiFi Hub app will list its Connection Type as "Ethernet", regardless of whether is connected directly, through a switch, or through an external Wi-Fi Access Point.

[lovetheinternet]

Fussed with it for a few hours and still couldn't get it working. For now I'm just going to connect through WiFi and be done with it.  When I have more time, I'll try to debug it further.  It was DHCP and not static IP, and was directly connected to the gateway lan port, not through a switch.  Thanks for everyone's responses.

[-G-]

@lovetheinternet  You can also view connected devices by logging into your Ignite Gateway with a web browser.  "Gateway > At a Glance" will show a partial list of connected devices and you can click the "View Connected Devices" button (or go to "Connected Devices > Devices") to show all connected devices and how they connect.

[Mdminto]

I don’t understand how this is a solution. All of my devices show connect as dhcp on the gateway but only one device consistently does not show up in the ignite app. I need it to show up so I can manage it as it’s a kids device.

[RogersCorey]

When all but one device works, typically that indicates a problem with that specific device.

What kind of device is it that won't show up @Mdminto?

Regards,

RogersCorey

[Mdminto]

It is a desktop computer and it was showing up previously - sporadically - but it did show up. It hasn’t showed up in about a couple months. We’ve rebooted the computer and the modem and it appears on the gateway network and it’s connected to the network.

[RogersCorey]

Could you please be more specific about the make/model and OS that this desktop computer is currently running? Thank you!

Regards,

RogersCorey

[-G-]

---

@Mdminto wrote:
It is a desktop computer and it was showing up previously - sporadically - but it did show up. It hasn’t showed up in about a couple months. We’ve rebooted the computer and the modem and it appears on the gateway network and it’s connected to the network.

---

There is some brokenness with the Ignite Gateways' device management.  It works fairly reliably if you have an IPv4-only device.  If it's a dual-stack machine and starts off by making network connections over IPv6, this can cause the device to not show as active in the device list.  (Device management can also be thrown off if the machine connects with a randomized MAC address.)

Machines can also disappear from the device list when they have a reserved IPv4 address in DHCP.  For whatever reason, the Gateway can spontaneously decide to give it a different IP address, and when this happens, the device will not appear in the device list, because it will only show as connected when it can obtain its reserved IP address.

You can also run into weird problems if you leave Wi-Fi enabled on the Ignite Gateway and have an Ethernet-connected Wi-Fi access point.  In that situation, a device could be Wi-Fi connected, have the Wi-Fi MAC address appear as being connected over Ethernet if it connects to the external Wi-Fi AP, or appear as being connected over Ethernet with yet a different MAC address if physically connected with an Ethernet cable.  If you add randomized MAC addresses into this mix, it can mess the Ignite Gateway up even more.

These bugs have been around for years.  It breaks port forwarding, device management and parental controls.

[Mdminto]

Thanks for the great explanation. Although it doesn’t sound like you've provided a solution. I need this to function properly for parental controls. That is the main purpose I use the ignite app for and you’ve basically told me it’s broken and glitchy and has been for years.

[-G-]

---

@Mdminto wrote:
Thanks for the great explanation. Although it doesn’t sound like you've provided a solution. I need this to function properly for parental controls. That is the main purpose I use the ignite app for and you’ve basically told me it’s broken and glitchy and has been for years.

---

The problem is also that Rogers is at the mercy of Comcast to deliver a functional implementation.

If you check the Xfinity support forums, you'll see Comcast's own customers complaining about the very same issues that Rogers' customers do.  Comcast is well aware that their equipment is bug ridden.  Some bugs simply are not a high priority for them to fix.