You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It is difficult to identify WiFi clients only by their MAC addresses, especially when there are many of them.
Describe the solution you'd like
If the hostname associated to a MAC address is know to an AP (e.g. because it runs a DHCP server or has its /etc/ethers regularly populated by a DHCP server), the AP should send this information to the OpenWisp server, which should display it as an additional field in the corresponding WiFi session.
The text was updated successfully, but these errors were encountered:
In the wifi session, there is already a DEVICE column. However, the reason devices are displayed as MAC addresses instead of hostnames is that, in the Device section, the hostname is set to the MAC address. This results in the MAC address being shown instead of hostname.
In the below image it is shown the device name is set to Test-Device1
The fact that all of the wifi sessions are shown below has same Device name is because it is been populated by a manual api which uses the Test-Device1's pk and key in the params
This is what I interpreted, please correct me if I'm wrong.
@dee077 In the DEVICE column I see the hostnames of the OpenWisp APs, but this feature request is obviously about the hostnames of the wifi clients connected to them (identified by the MAC ADDRESS column).
Is your feature request related to a problem? Please describe.
It is difficult to identify WiFi clients only by their MAC addresses, especially when there are many of them.
Describe the solution you'd like
If the hostname associated to a MAC address is know to an AP (e.g. because it runs a DHCP server or has its
/etc/ethers
regularly populated by a DHCP server), the AP should send this information to the OpenWisp server, which should display it as an additional field in the corresponding WiFi session.The text was updated successfully, but these errors were encountered: