Skip to main content (Press Enter).
Register | Sign in
Skip auxiliary navigation (Press Enter).
Help
Skip main navigation (Press Enter).
Toggle navigation
Products
Access Points
Switches
Product Selector
How it Works
Partners
Support
Documentation
Software
Help Center
Contact Support
Community
Discuss
Knowledge Base
Reviews
Instant On Blogs
Buy Now
Search Options
Communities
Community Home
Discussion
Topic Thread
Everything Instant On
Community Home
Discussion
1.7K
Library
10
Blogs
21
Events
0
Members
397
Back to discussions
Expand all
|
Collapse all
Why does the Aruba Instant On Portal / App randomly shows incorrect OS for Wi-Fi clients
1.
Why does the Aruba Instant On Portal / App randomly shows incorrect OS for Wi-Fi clients
0
Recommend
Employee
Krishnaprasad
Posted 12-12-2019 05:00 PM
Reply
Reply Privately
Options Dropdown
The OS information for a client is identified using the User-Agent field in HTTP traffic.
Refer to the below post for more details on the same.
https://community.arubainstanton.com/t5/Everything-Instant-On/How-does-Aruba-Instant-ON-AP-learn-the-Operating-System-of-the/m-p/1171#M396
,
Following screenshot is an example for few clients getting classified as Android devices and one Android device getting classified as Linux.
Clients Tab
Below is the random capture of a
HTTP
traffic initiated by an Android Client that is classified as a Linux Client.
The User-Agent has the OS info in the User-Agent –>
Mozilla/5.0 (Linux; Android 9; ONEPLUS A5000 Build/PKQ1.180716.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/78.0.3904.108 Mobile Safari/537.36
Though the User-Agent has the OS information as
Android
, the AP has set the OS for that client as
Linux
.
The above is because, a client device initiates multiple HTTP traffic through various applications.
The first HTTP packet, that was processed by the AP had the User-Agent value set to -
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.32 Safari/537.36
The AP hence processes the User-Agent field only on the first HTTP packet. Once the OS is classified for the client, the User-Agent field will not be processed on the following HTTP packets.
If a client entry is removed from the AP and the client connects again to the Wi-Fi, the chances for that client to send the appropriate OS information in the User-Agent Field is very high.
The AP will then re-classify the client’s OS accordingly and update the Client’s tab with the appropriate OS information for the corresponding clients.
This feature is hence completely based on the client's behavior.
#ClientsTab
#ArubaInstantOn
#OS
#User-Agent
×
New Best Answer
This thread already has a best answer. Would you like to mark this message as the new best answer?
Privacy policy
Terms of service
Legal
© Copyright 2024 Hewlett Packard Enterprise Development LP
Powered by Higher Logic