If you are asking about the "kernel: MACSEC: macsec is not enabled" notifications, the following comment from RMerlin in another discussion last year may be relevant.anything i can do about these messages
That`s not an error, that`s a notification. MACSEC is a business security feature that your home router does not support, the kernel is simply mentioning it as it reports a port connection.
That device's Ethernet port is constantly flapping, you need to figure out why. Most common cause is an out-of-spec cable that's unable to sustain a reliable 2.5 Gbps link. There are also some very buggy Intel 2.5 Gbps NICs that are notoriously bad.anything i can do about these messages
412958f30f Bumped revision to beta 3
c5cd10f0d4 pdated documentation
f73df7ee59 webui: allow querying WhatismyIP.com for addresses on the Connections page; tweaked layout
7c3c9693e5 lighttpd: allow the use of custom config files
b66327a786 lighttpd: rc: fix UAMSRV using an AiCloud configuration (fix from Asus)
5ad0ee00a6 build: fix 4dfc1e2f6d
4dfc1e2f6d build: generalize code that copies router-sysdep.
e6a7f15c14 build: copy RTL8372 driver to hnd_extra
abe6d62223 HND5.04be: move rtl8372 driver to router-sysdep
577dcd9134 rc: skip periodic FW checks if disabled
c55f1886ad libovpn: fix invalid firewall rules for OVPN server bypassing LAN firewalling
Regarding the client count: I am unable to reproduce the issue here. Since very few users are affected, it might require a very specific scenario. Since the networkmap code is closed source, and the issue is only visual, it will remain as it is for the final release, with the expectation that Asus will probably eventually reproduce it on their end, and fix it in a future GPL release.
I also run a few docker images as well as LXC containers on a Proxmox server, so that's not it.Guess its like having something (my server) on the network running docker with containers or other devices connecting from the same server but with their own ips and mac's. Beta 2 was stable for me. On beta 3 now. Thanks.
I also run a few docker images as well as LXC containers on a Proxmox server, so that's not it.
In the past, networkmap mapped clients by pinging the subnet, forcing the ARP cache to get filled up with replies, and then it gathered those MAC addresses to build a client list. That might have changed in the years since I last had access to that source code. You could perhaps check the content of the router's arp cache to see if anything odd is visible there.
I like the clickable public IPs. Not as in love with the left-justified fields and the hyperlink underline makes things slightly harder (for me) to read. The centered headings feel odd when the rest is left-justified. Not deal-breakers, but initial reaction to change.f73df7ee59 webui: allow querying WhatismyIP.com for addresses on the Connections page; tweaked layout
Dirty upgrade to Beta 3 from Beta 2. The connections update is a nice addition though most of my devices always seem to be connecting Amazon Data Centers so not always sure what a device is connected to.As there were some driver changes to fix the RT-BE92U issues, I decided to have another short beta round.
July 31st: Beta 3 is now available. Changes since beta 2:
Code:412958f30f Bumped revision to beta 3 c5cd10f0d4 pdated documentation f73df7ee59 webui: allow querying WhatismyIP.com for addresses on the Connections page; tweaked layout 7c3c9693e5 lighttpd: allow the use of custom config files b66327a786 lighttpd: rc: fix UAMSRV using an AiCloud configuration (fix from Asus) 5ad0ee00a6 build: fix 4dfc1e2f6d 4dfc1e2f6d build: generalize code that copies router-sysdep. e6a7f15c14 build: copy RTL8372 driver to hnd_extra abe6d62223 HND5.04be: move rtl8372 driver to router-sysdep 577dcd9134 rc: skip periodic FW checks if disabled
The Wifi 6 also has this additionnal change (which was missing):
Code:c55f1886ad libovpn: fix invalid firewall rules for OVPN server bypassing LAN firewalling
This build includes a "one more thing" feature, knocking down another long-standing entry from my ToDo list. You can now click on an IP address on the new Connections page to get more information about that IP through the WhatismyIPaddress.com website. That website will give you info such as this:
View attachment 67034
Links will only be clickable if the IP is a public one. If you use IPv6, then your LAN devices with an IPv6 will also be clickable, since client IPv6 are public. This is working as intended.
Regarding the client count: I am unable to reproduce the issue here. Since very few users are affected, it might require a very specific scenario. Since the networkmap code is closed source, and the issue is only visual, it will remain as it is for the final release, with the expectation that Asus will probably eventually reproduce it on their end, and fix it in a future GPL release.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!