Client status in firmware 376.45 - 376.48_3

[FireWire76]

Hi.

I have a problem with clients connecting to my router(RT-N66U).

Here is how my client status window looks like.

I tried refreshing, rebooting etc, so it's not old information that is displayed.
And the problem exist in all firmwares mentioned in the thread title.

Firstly the wired clients count is always wrong.

All devices are listed in my lan settings and I have set IP for each device. There seems to be something broken about this. Firstly about the 2 devices that gets the same IP, although they are listed in lan settings with different IP:s assigned to their mac-addresses.
The other problem here, is that I got a smart phone that I assigned an IP-address, but the router keeps letting the phone have a completely different IP...

Any help to narrow down the problem would be appreciated. Is it something wrong with firmware or is it something I have done wrong, that's the question.

 

[RussellInCincinnati]

The first thing to try is to view your router status screens with different browsers, on different computers. And see if any of the clients show up in any way that is different. If you see the exact same client icons on every different browser and every different computer, then you at least know that the display oddness is a result of something within the router.

It would also be interesting to know, concerning that unsettling problem of the device coming up with different IP addresses, whether or not the device really has different IP addresses (as verified by looking at the device itself), or is it merely a router display problem. Finally am interested in what exact steps you took in what exact router screens to assign the device an IP.

 

[FireWire76]

The first thing to try is to view your router status screens with different browsers, on different computers. And see if any of the clients show up in any way that is different. If you see the exact same client icons on every different browser and every different computer, then you at least know that the display oddness is a result of something within the router.

It would also be interesting to know, concerning that unsettling problem of the device coming up with different IP addresses, whether or not the device really has different IP addresses (as verified by looking at the device itself), or is it merely a router display problem. Finally am interested in what exact steps you took in what exact router screens to assign the device an IP.

Part 1 of your question, I have tried with both Firefox, Chrome and IE on 2 different computers. The same result presented in all conditions.
The count on wired is always wrong. If I add wired(x) and wireless(x) it sums up to 14 devices, but I only have 11. Which is presented under the online tab.

Part 2, the device don't come up with different IP-addresses. It's to different devices(Synology NAS devices) DISKSTATION-L and DISKSTATION-W. The L-unit is connected with cable and the W-unit is connected thru wifi. And they both receives the same IP-address!!!
Both diskstations have DHCP-enabled and no manual IP or dns-settings.

About assigning the IP-number to mac-addresses, I did this under "LAN" and the tab "DHCP Server".
I'll post an image below on how the assignment looks like.

 

[RMerlin]

Wireless clients show up as wired when they are offline. This is currently a known limitation of Asus's Networkmap.

Make sure you do upgrade your firmware. Newer versions will do a client list refresh every time you access it, to get rid of such stale entries.

 

[rototiller]

Try giving your Diskstations a static IP address each. I have a Diskstation myself and I assigned it a static IP address and it works.

 

[john9527]

Two things....

- Can you post the output of the System Log/DHCP Leases page?

- Can you try renaming them to L-DISKSTATION and W-DISKSTATION and see if that changes things?

Edit: I now remembered where I had seen this before. This can happen if two clients are broadcasting the same system name in the DHCP requests (like when a PC has both Ethernet and wireless active at the same time). Please check your two NAS units and make sure they have different names set directly on the NAS.

 

[FireWire76]

Two things....

- Can you post the output of the System Log/DHCP Leases page?

- Can you try renaming them to L-DISKSTATION and W-DISKSTATION and see if that changes things?

Edit: I now remembered where I had seen this before. This can happen if two clients are broadcasting the same system name in the DHCP requests (like when a PC has both Ethernet and wireless active at the same time). Please check your two NAS units and make sure they have different names set directly on the NAS.

That was the issue, they were both named "DISKSTATION" in their settings.
Big thanks for all help with this. =)

 

[FireWire76]

Wireless clients show up as wired when they are offline. This is currently a known limitation of Asus's Networkmap.

Make sure you do upgrade your firmware. Newer versions will do a client list refresh every time you access it, to get rid of such stale entries.

@Merlin, newer firmware doesn't help against stale entries. As stated in the title I tried all versions from the one I currently went back to, to the newest. No change at all. Yes, the refresh keeps happening, but the stale entries are still shown under wired.

 

[RMerlin]

@Merlin, newer firmware doesn't help against stale entries. As stated in the title I tried all versions from the one I currently went back to, to the newest. No change at all. Yes, the refresh keeps happening, but the stale entries are still shown under wired.

I assume that your signature isn't up-to-date then? It shows 376.45, which probably was before the forced refresh.

I don't see how you can have a stale entry if the device isn't connected over wifi at that time. So far my wifi devices are always properly recognized as such here.

 

[FireWire76]

I assume that your signature isn't up-to-date then? It shows 376.45, which probably was before the forced refresh.

I don't see how you can have a stale entry if the device isn't connected over wifi at that time. So far my wifi devices are always properly recognized as such here.

My sig is up to date, because I went back. Because the 48_1 and 48_3 didn't solve the problem, so I went back to see if the version I was upgrading from was any different. (And I also thought there was an issue with those firmwares, because the web page never finished loading when I used them.)
For some reason it seems that when I fixed the Diskstation-problem, then there are no stale devices. When the Diskstation-problem existed, other offline devices was visible in the device list. So I guess the router didn't like that 2 devices had the same host name and that it affected other functions too?
Anyway the problem went away when the fix was applied and I have no longer stale devices in .45-firmware.