openwrt-mt6000-4.8.2-op24-0903-1756864663.
A NAS was given an IPv4 address but the Clients display shows an IPv6 address. An NSLOOKUP of the host name returns the IPv4 address. An NSLOOKUP of the displayed IPv6 address returns an Unknown Domain error.
Another possible bug (and perhaps a dumb user error): Two other NAS devices were given IPv6 addresses. These do not appear in the Clients list. Also, I want them to have IPv4 (or both IPv4 and IPv6) addresses. I can see no way to control this.
Click on the name the device it’s a link to a a more detailed client view.
OF-Pub-NAS1
Also is DHCP enabled on the NAS, It looks like Odhcp6 might be working since you got a local ipv6
Some time overnight these two devices were given IPv4 addresses. I’ve now set a static lease for these addresses so hopefully they will stay as IPv4.
The incorrect information on the Clients display has not resolved.
This is weird. The detailed display shows two IPv6 addresses but no IPv4 address. The device is reachable via the (unshown) IPv4 address. The device is also reachable (at least PINGable) by the non-Link Local I{v6 address. (I don’t know what to call that address.) The device in not reachable by the display Link Local address. NSLOOKUP issued on Windows does not know either of the IPv6 addresses but does know the (unshown) IPv4 address. I suspect this will clear up if I reboot the router, but that would end any diagnostic work.
When I make changes to the network settings I usually reboot or at the very least /etc/init.d/system reload. the router
Most changes also require you to reset the connected devices on your network to propagate the changes
I had to reboot twice to solve a different problem. This display error survived the two reboots. It probably has something to do with the NAS and doesn’t seem to effect anything other than the display, but it is odd (and persistent).
did you try rebooting the NAS, That would have been my first thing to do.
Thanks for the idea but it didn’t work. Same problem in the Clients display.
Hi
It appears there was an error while retrieving the client address.
Could you please share your device with us via GoodCloud for remote inspection, following the tutorial below?
Technical Support via GoodCloud - GL.iNet Router Docs 4
Please send us the MAC address and web password via private message so we can access it.
There will be a delay in doing this. I had to switch back to my ASUS router because of problems getting CNAME processing to work.
I’ve swapped the routers again so I’m now using the MT6000 again, but it’s after midnight here and I’m going to bed. I probably won’t get to the GoodCloud thing until at least mid morning.
BTW, I rebooted the MT6000 and briefly the Clients display showed IPv4 address for a while but it then went back to the IPv6 addr.
Thank you for the update. Please feel free to share your device via GoodCloud whenever you are ready.
I’m having problems with GoodCloud setup. I need a GLiNet account (which is apparently separate from this forum account). The sign up process does not like something about my email address. It also wants a verification code that (I guess) gets sent to my email.
I’ll try another email address, but I doubt that will help.
The GoodCloud instructions also instructions I don’t know how to follow:
Before sharing your device with GL.iNet technical support, please ensure your router has an additional Internet connection for stability. Set up an Ethernet or Repeater connection as a failover backup and ensure it works properly.
I have only one internet connection and the router uses it. I can go back to my ASUS router and put the GL router down-stream from it (with all of my LAN devices except my PC still attached to the GL router) but that doesn’t give the GL router any fallback internet connection. It just gives me internet connection if you reboot the router.
Om Mondays I run backups to/from devices on my LAN. It will be hours before I can reconfigure my network if that’s really needed.
OKay. It really didn’t like my email address. I’m set with GoodCloud (I think).
Thank you for sharing the device, but we couldn't find it in the list.
Could you please check again or re-share the device?
As I had said in an earlier reply, I didn’t know what to set as Recipient. Thank you for showing me. Is there anything else I need to do?
Update:
This issue is caused by certain devices sending high-frequency IPv4 ACD, resulting in abnormal client list displays (toggling between IPv4 and IPv6 addresses).
We have submitted this to the R&D department and a fix is planned.
