NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

cgthayer's avatar
cgthayer
Follower
Jun 12, 2021

EERO and ReadyNAS

I have two ReadyNAS (a 2TB and 4TB).  I recently moved to use an "eero pro" for mesh wifi.  Both devices are not showing up on my network although they're wired (over ethernet) to the eero.  The DHCP in the eero says one was assigned to 192.168.4.30, but when I run raidar (linux on wifi) I get "Found 0 total systems":

 

 

; ./bin/raidar-cli -v
got 3 interfaces:
IP=172.17.0.1 Mac=02:42:29:a4:4a:23 BroadAddress=172.17.255.255
IP=172.18.0.1 Mac=02:42:04:93:e2:be BroadAddress=172.18.255.255
IP=192.168.4.30 Mac=4c:34:88:54:26:b2 BroadAddress=192.168.7.255
sent primer with sid=0xffffffff cid=0x3cf64

Found 0 total systems

I was hopeful that it might be the 192.168.4.30, but that didn't work 

ping 192.168.4.30
PING 192.168.4.30 (192.168.4.30) 56(84) bytes of data.
64 bytes from 192.168.4.30: icmp_seq=1 ttl=64 time=0.052 ms
64 bytes from 192.168.4.30: icmp_seq=2 ttl=64 time=0.040 ms
64 bytes from 192.168.4.30: icmp_seq=3 ttl=64 time=0.082 ms

curl -v 192.168.4.30
*   Trying 192.168.4.30:80...
* TCP_NODELAY set
* connect to 192.168.4.30 port 80 failed: Connection refused
* Failed to connect to 192.168.4.30 port 80: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 192.168.4.30 port 80: Connection refused

 

Running "arp -a" gives me no luck.  I would need to be on the wired network for that, or eero would provide (which I can't find)

ping -b 255.255.255.255
WARNING: pinging broadcast address
PING 255.255.255.255 (255.255.255.255) 56(84) bytes of data.
64 bytes from 192.168.4.34: icmp_seq=1 ttl=64 time=22.2 ms
64 bytes from 192.168.4.34: icmp_seq=2 ttl=64 time=43.7 ms

arp -a
YR00DP168499.local (192.168.4.38) at 88:de:a9:23:aa:95 [ether] on wlp3s0
eero-18\05890\05888\058b3\0580e\05880.local (192.168.4.42) at 18:90:88:b3:0e:92 [ether] on wlp3s0
iMac-2.local (192.168.4.34) at ec:35:86:30:c1:b4 [ether] on wlp3s0
_gateway (192.168.4.1) at 74:b6:b6:8a:10:6d [ether] on wlp3s0


How can I further debug this? 

Everything has been power cycled multiple times.

Thanks for any advice.

 

2 Replies

Replies have been turned off for this discussion
  • Sandshark's avatar
    Sandshark
    Sensei - Experienced User

    I'm not familiar with RAIDar on Linux, but this doesn't seem quite right: 

    IP=192.168.4.30 Mac=4c:34:88:54:26:b2 BroadAddress=192.168.7.255

    The listed addresses are in different subnets.  Did you previously have your LAN subnet as 192.168.7.xxx, and might you have assigned the NAS a static IP in that range?

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More