I'm surprised this doesn't already exist and I know there are options in Luci, but it doesn't seem to do exactly what I am looking for and feels to be a base item I had in other router manufacturers/UI.
2 Features are missing for me:
Live bandwidth monitoring of my connection
Indication on which device clients are speaking to (wireless).
On the first one, why not a simple graph showing upload/download speeds in the main UI with top talkers?
On the second, I'd like to know what client is associated to what radio on which device. I have a main router (flint2) and 3 marbles as APs. I'd like to know if a particular client is talking to one of the APs and which one.
I will record the first one and hand to PM team to evaluate.
The second one also will recorded, but may be hard to achieve, since which client is associated with which Marble AP or main router Flint 2 WiFi, the client list of main router Flint2 cannot be confirmed as the client list is obtained through ARP and DHCP server assigned, and it is impossible to know the special client is associated with which AP. If this feature develops to achieve, I think that needs to consider it deeply, it may belong to the Mesh function (including the wired or wireless Mesh) and has a large development workload. I think only developed the Mesh structure networking can this feature be achieved.
I appreciate you forwarding it along to the PMs and team. If i had access to Jira, I'd submit it myself.
Just thinking in terms of parity in general consumer hardware UI. Seeing #1 is a base item. Show me my upstream/WAN link speeds on a graph and maybe clients that are the 'top talkers'. Would answer the initial question you always get as the network admin for your home 'why is everything so slow' (and then try to prove it is them streaming or DNS again). I somewhat expected it to be on the main page or under 'network' as status. I am aware that values will be skewed because of hardware acceleration, but you could initially work in terms of % rather than raw numbers if you want to avoid confusion.
On #2, that is a selfish item that probably would require tagging and reporting from the individual radios up to the main. I don't know if that is a base functionality of 802.11s. I am just trying to figure out which AP/Repeater/Device is currently servicing that client. It would allow me to adjust radios to compensate. Eventually, it would be nice to force clients only to bind to a particular AP, but that probably is a huge undertaking to script and prone to support complaints. I'm trying to avoid a device such as a TV or speaker that normally doesn't travel from picking up signal several rooms away rather than the AP nearby.
To bring in specifics, this was functionality I had with Google/Nest access points. It tagged what puck it was talking to. Also, unifi/ubiquiti (yes, i know it's more prosumer), you can bind to specific AP. I was spitballing how to achieve this by setting up some ACLs on various devices to either deny or allow specific MACs.
