Security

Reply
Highlighted
MVP

Re: Handling BlackBerry Devices - Identification

Just in case you were talking about the BlackBerry here is the info.

'MAC Vendor' missing.

 

Model: BlackBerry Q10

Model Number: SQN100-3

Software Release: 10.1.0.4181

 

BlackBerry_Q10_MAC_Vendor.png

 

---------------------------------------------------------------------------------------

@tarnold

 

Hey just wanted to make sure which device you were talking about.

Were you talking about the BlackBerry Q10 missing the Vendor MAC?

 

Or were you talking about @cappalli and the BlackBerry devices that were getting misfinger printed as Android devices?

 

Thank you,

 

Cheers

Highlighted
MVP

Re: Handling BlackBerry Devices - Identification

I have a BlackBerry Z10 device that was been finger printed correctly.

Then just today the Endpoint profile was updated and now the finger print appears to be wrong.

 

It is showing the Z10 as an Android device. I checked the last time the "Endpoint Profile Fingerprints" db was updated and it hasn't been updated in almost a month so it is a little strange that is suddenly changed.

 

It could be that the Z10 itself was updated recently so now maybe the finger printing is off?

I have IFMAP enabled on the Aruba Controller.

 

Any thoughts?

 

Endpoints_0006.png

Highlighted

Re: Handling BlackBerry Devices - Identification

What is the controller profiling it as?

Thank You,
Troy

--Give Kudos: found something helpful, important, or cool? Click Kudos Star in a post.

--Problem Solved? Click "Accepted Solution" in a post.
Highlighted
MVP

Re: Handling BlackBerry Devices - Identification

That is a good question.

I will have to figure out how to check that and I will get back to you!

 

--------------------------------------

 

I should be able to see how the controller profiles it using the following command? Is that right?

#show log network all | include DISCOVER

If this is the case then I will need to get my hands on the phone as the logs don't go far enough back.

 

I will probably have to have the client reconnect to our Guest SSID temporarily to see what the controller is doing.

Highlighted
MVP

Re: Handling BlackBerry Devices - Identification

Hey,

 

On the 'show user-table' the device is profiled as 'Type - Android'

 

Here is the DHCP Discover string

DISCOVER 40:6f:2a:6a:e5:34 Transaction ID:0xd8af2a78 Options 0c:4d61726342427a3130 37:011c02030f060c 3c:426c61636b4265727279204f532031302e322e302e31373931

 And here are the device details.

 

Device Manuf: BlackBerry

Device Model: BlackBerry Z10

Model Number: STL100-3

OS: 10.2.0.424

 

I confirmed with the user that they recently updated the BlackBerry OS.

 

Hopefully this helps!

 

Cheers

Highlighted
Moderator

Re: Handling BlackBerry Devices - Identification

My Z10 is always profiled as Android because of the Android VM that runs in
the background to support both QNX and Android apps.


If this response is more than 1 year old, it may no longer be accurate. Please consult official Aruba documentation, TAC or your Aruba SE.

| Aruba Alumni | @timcappalli | timcappalli.me |

Highlighted
MVP

Re: Handling BlackBerry Devices - Identification

I remember you mentioning this cappalli

 

I wasn't sure if this had been resolved yet or not. Or if it is even resolvable based on your comments about the Android VM.

 

This Z10 in question at one point was being profiled correctly. It was only this most recent update that changed that.

Any chance you might know which OS your Z10's are running?

Highlighted
Moderator

Re: Handling BlackBerry Devices - Identification

Last time I did some testing, I was using 10.2.0.1767.

 

I think BB10 is the only platform that can run another OS on top of the core so I think the way it gets profiled is a new situation. Technically, it's being profiled correctly based on the information the device presents. It seems that either ClearPass or the controllers need to look at another piece of information that is unique to BB10. What that is, I do not know. I know this isn't entirely helpful, but just some observations.

 

 



If this response is more than 1 year old, it may no longer be accurate. Please consult official Aruba documentation, TAC or your Aruba SE.

| Aruba Alumni | @timcappalli | timcappalli.me |

Highlighted
MVP

Re: Handling BlackBerry Devices - Identification

No it is absolutely helpful!

 

It at least gives me an idea of what is happening and the cause.

Strange that I am only seeing it now.

 

I wonder if the CPPM could parse the DHCP Finger printing information differently as the DHCP Option60 indicates it is 'BlackBerry OS..'.

I am not sure of the reliability of this information though.

I am not all that familar with the innerworkings of the finger printing so I shouldn't comment further!

 

As a temp solution I included in my Role Mapping 'if MAC Vendor = Research In Motion' do 'blah'

 

I guess it could be a little bit before there is a solid solution to more accurately finger print the Z10's

It is pretty unique in the mobile world as you described.

 

Thanks for the info though cappalli it is much appreciated!

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: