Direct Transition from Modem to Ethernet Switch
Direct Transition from Modem to Ethernet Switch
I've noticed some unusual network behavior with your friend. It seems they're connecting straight from the fiber optic box to a Google Wi-Fi router and then into an Ethernet switch. Based on what you described, it looks like they're using a modem-router combo setup. I'm curious if this is the standard configuration they should follow. Also, wondering if the Google Wi-Fi router might have restrictions or settings that need adjusting. If this box is indeed a modem-router combo, would it make more sense to route directly to a switch rather than going through the router? Any suggestions would be appreciated. Thanks for your help!
The FO modem should include a basic network bridge or router built-in. Its issues align with a layered NAT configuration. The Google Home router must be set up as an access point, not as a router or NAT provider. --OR-- Set the FO modem as a straightforward network bridge. --OR-- Position the Google Home router in a DMZ.
It seems setting up the Google Wi-Fi router as an access point removes its mesh functionality, which explains why they acquired it originally. You’ll likely need to ensure all other devices in the network operate in bridge mode or disable their NAT settings. The additional switches you purchased may help replace outdated hardware, but confirming whether the router itself can be configured on your end is important. I’m not sure if you need to contact support directly—check the documentation for the box or see if XMission can assist. Let me know if this makes sense.
I attempted to connect a computer straight into the FO box without success. Trying via the switch from the box also didn’t work. The best option was using the Google Wi-Fi router to reach the FO box, then connecting to a computer. This indicated my setup likely involves routing through multiple devices rather than direct connections. It seems the FO box probably assigns IP addresses to each router in my network, which is why I couldn't get a direct link. Plugging just one device directly might not work unless it’s part of a properly configured setup. After troubleshooting, I ran a tracert through a friend’s router and noticed only one private IP address—this could mean the NAT isn’t cascading as expected.
It’s probable the FO box acts as a "router" with a restricted DHCP range. I’d think the scope limit relates to service level. From the SS, there are two routers—number 1 and number 2. The FO box has an IP inside the ISP’s subnet assigned to it, indicated by the lo0 prefix. This suggests it’s routing traffic but probably only handling the essential forwarding to/from the ISP. So it likely serves as a bridge.
Access the customer area of the box to review its setup. This provides sufficient details to confirm whether NAT is active and to turn it off if needed. Random ping spikes might also stem from ISP-related issues, such as poor connection quality or damaged cables like a bent FO cable.