Log associations, reassociations and disassociations of clients
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I'd like to log or access a list of associations, reassociations and disassociations of clients.
I have 9 EAP( 3x 115, 6x225[-Outdoor] ) APs and an oc200.
My goal is to see at which point reassociations between the APs happen so I can move some APs for better coverage. (Most APs are outdoors with many objects potentially blocking some APs)
I have a bunch of VLANs incase that matters. I'd only need to monitor a single vlan but across all APs.
The omada control panel is too slow with updating the AP a client is connected to so I can't use that as a gauge.
So far I tried mirroring the switch port of the oc200 and analysing it with wireshark but noticed that the communication between the APs and the oc200 is rather... unreadable, to put it like that.
I also tried SSHing into the OC200 but I cannot connect, even though I turned SSH on. I have no idea if that would even help as I was never able to access it.
Any idea is welcome!
I think the clientStats script would fit better in this case, it's in this post.
It seems that Omada Controller even records surveys from clients which do not associate with an SSID at all.
Just change the lines:
case $# in
0) query="\$and: [ { site: 'Default' }, { duration: { \$ne: 0 } } ]" ;;
1) query="\$and: [ { site: '$1' }, { duration: { \$ne: 0 } } ]" ;;
*) echo "Usage: ${0##*/} [site]"; exit 1 ;;
esac
to:
case $# in
0) query="site: 'Default'" ;;
1) query="site: '$1'" ;;
*) echo "Usage: ${0##*/} [site]"; exit 1 ;;
esac
to see all clients requesting the SSID during a survey.
Modified script appended to this post.
