NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Ping from WLAN to LAN or vice versa not working (RAX54)
I am using a RAX54v2 NightHawk and I have several devices connected to either a WLAN (wifi) or LAN (wired). It looks like traffic from WLAN is not routed to LAN or vice versa even though the devices are in the same subnet (192.168.1.0/24). (How) can I allow pings and other traffic to cross the LAN/WLAN boundary?
Note: I would like to preserve the protection offered by the NAT, i.e., I don't want to bridge LAN/WLAN traffic to the WAN port unless there's a safe way to do it.
Thanks.
Thank you for the replies, CrimpOn and FURRYe38.
I think I figured it out based on your answers. The devices I tested with are: a Windows laptop (wired), a Raspberry Pi, another similar Linux board running Debian, and an HP printer (wired). Both Linux devices are headless. I have several other devices connected via wifi and wired, to the same router. The Linux devices were connecting to the guest wifi, which I had set as non-routable to other networks. My Wifi networks are named something like 'Yogurt', 'More Yogurt' and 'Yogurt Guest'. The tool I was using to check the SSID of the network these devices were connecting to happened to be buggy and reported that I was connected to 'Yogurt' when I was connected to 'Yogurt Guest'.
I don't see a protection engine feature. I was referring to the 'VLAN/Bridge settings' page - my apologies, I should have been clearer. I am curious to know if there is a way I can access and edit the underlying NAT rules of the router, if needed - a command-line interface similar to iptables would be great.
Thanks again!
4 Replies
The primary network of Netgear routers (wired devices plus the primary WiFi network) is one IP subnet. ICMP (ping) and every other protocol should work between any devices on the primary network as long as the devices support the application.
ping is a bit tricky because:
- Some devices simply do not support it. The Amazon Echo Dot, for example, does not respond to ICMP.
- The firewall on some devices, such as Windows PCs, must be told to allow ICMP.
On many Netgear routers, devices on a Guest WiFi network cannot interact with devices on the primary network.
Please give examples of specific devices that are not working.
What devices do you have connected to the router on WiFi and Ethernet?
Pinging between devices on the WLAN and LAN should return success.
How are you pinging devices?
Do you see protection engine feature on the routers web page?
I am using a RAX54v2 NightHawk and I have several devices connected to either a WLAN (wifi) or LAN (wired). It looks like traffic from WLAN is not routed to LAN or vice versa even though the devices are in the same subnet (192.168.1.0/24). (How) can I allow pings and other traffic to cross the LAN/WLAN boundary?
Thank you for the replies, CrimpOn and FURRYe38.
I think I figured it out based on your answers. The devices I tested with are: a Windows laptop (wired), a Raspberry Pi, another similar Linux board running Debian, and an HP printer (wired). Both Linux devices are headless. I have several other devices connected via wifi and wired, to the same router. The Linux devices were connecting to the guest wifi, which I had set as non-routable to other networks. My Wifi networks are named something like 'Yogurt', 'More Yogurt' and 'Yogurt Guest'. The tool I was using to check the SSID of the network these devices were connecting to happened to be buggy and reported that I was connected to 'Yogurt' when I was connected to 'Yogurt Guest'.
I don't see a protection engine feature. I was referring to the 'VLAN/Bridge settings' page - my apologies, I should have been clearer. I am curious to know if there is a way I can access and edit the underlying NAT rules of the router, if needed - a command-line interface similar to iptables would be great.
Thanks again!
Glad you figured it out. ya, You won't be able to ping from LAN/WLAN to Guest network as that is isolated from those networks.
And there is no command line interface anymore on NG routers. Telnet was removed years ago.
Please mark your thread as solved so others will know. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/24231/How-do-I-back-up-the-router-configuration-settings-on-my-Nighthawk-routerEnjoy. 📡
