Administrative page won't show up - ReadyNAS 314

---

Dyllo wrote:

 

The data reaches a switch (ThoughPoE), and they both have an access point there;  IP 192.168.1.72 and 192.168.1.73.
The entire data then goes to another switch (ThoughPoE); IP 192.168.1.70 ; with an access point IP 192.168.1.71

I understand that the hydrophones transmit their data to base stations (.31 and .41) but I am a confused by what you mean when you talk about the "access points" above. In normal network-talk, and "access point" would mean a WiFi access point.  But I don't think that's what you are talking about.

---

Dyllo wrote:

 

 For our internet connection we use a RadioLab router.

The RadioLAB looks like a NAT router, meaning that it has an external IP address (for the WAN port) and an internal IP address (used to reach the router over wifi or ethernet).

Is one of the LAN ports of the router connected to one of your switches?  If so, you can configure your network so any of the devices can access the internet.

Either way, if you have devices that have WiFi on while accessing the local devices, we should follow up on the router configuration.

Do you know what LAN address your router is using?  WiFi is off in your screen shots, so I can't tell.

---

Dyllo wrote:

 

-> The IP address of the RN 314 is now (after being upgraded): 169.254.71.1 

 

---

This really should also be assigned a 192.168.1.x address.

Here's an explanation: The subnet mask (255.255.255.0) is used by all your devices to determine whether the device they are trying to reach is local (on the same subnet) or remote (not on the subnet).  A better name for "remote" is "off-net".

The IP addresses and masks are all 4 bytes - 255 therefore is all ones.

So when the PC tries to reach 169.254.71.1,

it "ands" that value with the subnet mask -> resulting in 169.254.71.0.

It then similarly "ands" its own address with the subnet mask -> resulting in 192.168.1.0

If then compares the two results.  If they match, the destination is on the subnet, so the PC then finds the ethernet MAC address for the NAS using a protocol called ARP.  IT then constructs packets with the destination MAC ethernet address and the destination IP address. Your switches then know how to route the data to the NAS (layer-1 switches just use MAC addresses and totally ignore the IP addresses).

In your case they don't match, so the NAS is off-net.  In an IP network, all off-net traffic is sent to the gateway - and you don't have a gateway configured.  You are a bit lucky that you can reach the NAS at all this way.

Figuring out exactly what happens when WiFi is on requires a bit more information (asked for above).  But I suspect the PC is trying to directing the NAS data to the WiFi link, which is then unable to deliver it to the NAS.