NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Wired devices not routing: Orbi RBR50, RBS50
Hello,
My Orbi mesh system suddenly stopped routing wired devices. I had an RBR50 with two satellites (RBS50 and RBS20) previously working well. Suddenly my wired devices stopped routing.
Cur...
I solved it. I am embarressed to say, I had a killswitch process running in the background. I had to go in through the CLI and kill the process then I got right through.
Thanks for all of the help.
Is the desktop computer the only device which does not have internet access?
Could you open a command window and report the information about the desktop DHCP assignment?
i.e. run ipconfig /all
for the Ethernet adapter, report:
IP Address
Subnet Mask
Gateway IP
DNS IP
Hello,
Yes it's a desktop running Ubuntu 22.04.3 LTS
Ifconfig =
inet 192.168.3.4
netmask 255.255.255.0
broadcast 192.168.3.255
default route = 192.168.3.1
gateway = 192.168.3.1
arp -a
I can ping the
RBR50 3.1
RBS50 3.3
But I *cannot* ping 3.2 which is the laptop connected to the wifi router that I am typing on now.
From the laptop I *can* ping
The router, satellite, and the desktop that won't route out.
No changes to desktop except I did turn the firewall off for trouble shooting. Normal rule set to deny incoming and allow outgoing.
Thanks for the information. What sort of computer is the laptop?
(Windows, for example, does not respond to ICMP (ping) until told to do so. Here's one article - of many.)
https://www.en-zdv.uni-mainz.de/allowing-icmp-ping-in-the-windows-firewall/
Have you tried to ping something outside the local network, such as Google DNS (8.8.8.8)?
First, thank you for the assistance.
Laptop is Windows with McAffee Ultimate running.
Firewall is Windows Defender. I enabled ICMP Echo requests:
But still no luck.
From the wired connection, I cannot ping any outside address, the external wan interface on the RBR50, or any internet FQDN or IP such as 8.8.8.8.
Router settings are:
Connected devices:
Thanks again for the assist.
I solved it. I am embarressed to say, I had a killswitch process running in the background. I had to go in through the CLI and kill the process then I got right through.
Thanks for all of the help.