Exchange information across distinct network segments.
Exchange information across distinct network segments.
I just swapped my Apple Airport Extreme for a Wavelink Quantum DAX/WL-WN538A8 AC3200 router. It features three Gigabit LAN ports and one WAN port linked to my old router at 192.168.0.1 with DHCP. The Wavlink unit (192.168.10.1) has a Windows 10 PC and two printers on the LAN, getting IPs through DHCP. Both LAN and WAN ports need separate IP ranges—this wasn’t a problem before. Issue: I can ping from 192.168.10.x to 192.168.0.x but not vice versa. What should I do?
A more effective approach would be to disable DHCP on your second router and connect via LAN instead of WAN to the first router. This ensures the first router manages all DHCP requests and maintains a consistent network range.
The traffic direction depends on the router handling the connection. It directs data between networks, but when you're connected to a device like 192.168.10.5, it doesn't recognize it as part of its own network. It forwards the request to the default gateway (192.168.10.1). If the other router is involved, it can route the message correctly because it has the appropriate address range. On the other hand, if you're on 192.168.0.5 and ping 192.168.10.5, the same issue arises—it sends the request to its default gateway (192.168.0.1), which isn't part of the 192.168.10.x network and can't deliver it. The simpler fix is to disable DHCP on the second router so it acts as a static access point instead of relying on NAT. Alternatively, you could manually add a custom route to forward traffic for the 192.168.10.x subnet to the other router's IP within its network.
You'd need two DHCP servers, and it can be frustrating on a simple network.