× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973

Re: sickbeard, readynas remote/leafnet, wombles


sickbeard, readynas remote/leafnet, wombles

forever I have had errors from sickbeard regarding wombles index.

after some investigation, I discovered that nzb.isasecret.com I can ping from my pc, but the readynas's can not.

Z:\d>ping nzb.isasecret.com

Pinging nzb.isasecret.com [] with 32 bytes of data:
Reply from bytes=32 time=472ms TTL=113
Reply from bytes=32 time=202ms TTL=113
Reply from bytes=32 time=192ms TTL=113
Reply from bytes=32 time=249ms TTL=113

Ping statistics for
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 192ms, Maximum = 472ms, Average = 278ms


sauron:~# ping nzb.isasecret.com
PING nzb.isasecret.com ( 56(84) bytes of data.
From 5.168.x.x icmp_seq=2 Destination Host Unreachable

looking at the nas routing table, leafnet is sending all 5.x.x.x traffic to the leafnet adapter.

sauron:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface * U 0 0 0 eth0 * U 0 0 0 LeafNets
default DD-WRT UG 0 0 0 eth0

since wombles is apparently hosted on a 5.x.x.x network, but not a leafnet network, it is failing because it is trying to route out the leaf adapter instead of the default route.

I would prefer to keep remote installed/enabled, but it obviously has the wrong subnet mask in the routing table.

looking up the 5.168 network shows

inetnum: -
netname: TIM-NET
descr: TIM
descr: Telecom Italia Mobile
descr: Service Provider
country: IT

not sure why it doesn't belong to leafnet or netgear, but which calculates out to be a network

so I fixed it with the below;

route del -net netmask
ip route add dev LeafNets
Message 1 of 7

Re: sickbeard, readynas remote/leafnet, wombles

When Leaf first began operations, 5.x.x.x was reserved for "experimental use" by IANA so it was safe to use for the VPN address scheme.

When IPv4 addresses started becoming scarce, it was re-allocated, so it could be (and now is) used for internet addressing. Netgear needs to switch the leaf adapter to use a private address space. But they never have, even though the 5.x.x.x addresses were reallocated a few years ago.
Message 2 of 7

Re: sickbeard, readynas remote/leafnet, wombles

I had wondered about that, makes sense. They definitely need to switch to a private network then, 5.x public ips are inaccessible from the nas unless you manually make the routing changes.

A /15 may not even be most correct subnet for leaf too.
Message 3 of 7

Re: sickbeard, readynas remote/leafnet, wombles

I just ran into this myself. I was having this really strange networking issue last night where I could no longer access one of my (recently moved) remote servers from any of my ReadyNAS devices [destination network unreachable], however, all of my other devices could access it perfectly fine. After a couple hours of troubleshooting [disabling bonding, jumbo frames, rebooting, etc] I noticed that the ReadyNAS Remote service (specifically the LeafNetworks adpater) has a network ID & subnet mask of 5.169.x.y/ that was sending traffic destined for my server through the Leaf adapter instead of the server (5.79.x.y)

I have disabled ReadyNAS remote as a temporary workaround, but it would be wise for Netgear to address the issue.
Message 4 of 7

Re: sickbeard, readynas remote/leafnet, wombles

Wow, here we are in 2015 and this still is not fixed.

Thanks for the well documented solution/hack/workaround.
Message 5 of 7
NETGEAR Employee Retired

Re: sickbeard, readynas remote/leafnet, wombles

If it was a simple fix we would have fixed this ages go.
Message 6 of 7

Re: sickbeard, readynas remote/leafnet, wombles

IP6 and done.

Message 7 of 7
Top Contributors
Discussion stats
  • 6 replies
  • 0 kudos
  • 5 in conversation