Why the headless Raspberry Pi 5 isn't showing up on the LAN while the Xfinity gateway is set to bridge mode.
Why the headless Raspberry Pi 5 isn't showing up on the LAN while the Xfinity gateway is set to bridge mode.
I possess an ASUS RT-AX55 router and a Xfinity Gateway (Cox Technicolor CGM4331) operating in Bridge Mode.
NETGEAR 8-Port Gigabit Ethernet Plus Switch (GS308E)
LAN - [switch] - [router] - [Xfinity Gateway (bridge mode)]
Nine devices connected via Ethernet, except when WiFi is active:
1 Smart Security Hub (WiFi, visible)
2 active laptops (visible)
1 tablet (WiFi)
3 streaming devices: Onn (WiFi, visible), Xumo (visible), Roku (not visible)
1 printer (WiFi, not visible)
2 Raspberry Pi Zero 2 w (visible)
All these units can reach the internet through bridge mode enabled or disabled.
Printing is possible from any of them.
SSH access is available to the Pi zeros.
Remote control can be sent from either laptop to the other.
The Pi 5 appears only when the gateway isn’t in bridge mode.
The information regarding the Pi 5's connections and network setup isn't specified. The term "not visible" refers to unclear details about where the device is linked, whether it relies only on wired or wireless signals from the Asus router or switch. It also asks about using a Cox-owned modem with Xfinity and whether the Pi 5 receives an IP address within the same subnet as other devices.
What IP addresses and subnet masks are you employing?
Please add a line diagram or network representation to your update.
Images and screenshots can be shared using imgur (www.imgur.com > green icon "New post").
Additional details are required.
The PI 5 is linked through the switch. Not visible indicates the device isn’t listed on the Asus device directory, yet it’s active on the network and working properly. Four devices connect wirelessly, while five use the switch. The Xfinity Android app confirms "Your TECHNICOLOR CGM4331COM is online." A link to the support page is provided: https://www.cox.com/residential/support/...m4331.html. I’m unsure of the PI’s assigned address since it doesn’t appear in the Asus list. It seems headless, with the default dynamic IP, and it boots correctly; no error codes are shown on the LEDs.
Cox just happens to use Technicolor and provides a support page for it for their customers. It is a brand used by most cable ISPs. Cox doesn't produce them.
Who cares whether the Asus shows it in the device list if it's working perfectly fine? And if it's on the network and functioning, then I'd assume you're able to remotely access it, so you must know what IP it has. If you can't get into it, how do you know it's working or has booted normally?
The connected devices/network map list in an Asus router isn't 100% accurate; it's a proprietary feature and nobody outside Asus knows what criteria it's using to "find" them, and it's known to have devices randomly missing from it. Sometimes refreshing repeatedly will change the list, sometimes a reboot of the router does the job. Sometimes they'll just appear on their own briefly then go away. There's no way to know why it works when bridge mode is off but not when it's on. (What subnet do you have the router set to for the LAN side, and what IP does it get on the WAN when bridge mode is off?)
The DHCP client list will show what IPs have been assigned to what devices. You can also just try ping scanning the entire subnet range with Advanced IP Scanner, if in fact you don't know the IP, as long as the Pi5 is configured to respond to ping. (It will also test some common ports so it might be identified even if it doesn't respond to ping. Advanced Port Scanner can go further.)