Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

ClearPass and non 802 devices

This thread has been viewed 0 times
  • 1.  ClearPass and non 802 devices

    Posted Feb 24, 2020 10:30 AM

    We have a SSID for non 802 devices like gaming consoles on campus.  We use ClearPass portal for users to register these devices via MAC.  We have found that many are registering their 802 devices as well and would like to prevent any 802 device from connecting to this SSID.  Suggestion on how to accomplish this would be appreciated.



  • 2.  RE: ClearPass and non 802 devices

    EMPLOYEE
    Posted Feb 24, 2020 12:13 PM

    If you know Device Types of those non 802.1X Devices, you could use the Profiler to get rid of all the other Device Types like Smartphones, etc.

     

    Another thing could be that you place Sponsored Registration, where a Sponsor must allow registered Devices before they can gain access to the network.



  • 3.  RE: ClearPass and non 802 devices

    Posted Feb 24, 2020 01:31 PM

    Can you show me how I would do the first part?  Do not want to get someone bogged down with having to do that all day.

     

    THANKS!



  • 4.  RE: ClearPass and non 802 devices

    EMPLOYEE
    Posted Feb 25, 2020 02:08 AM
      |   view attached

    Another possibility is to create an Enforcement Profile where all disallowed Device Types get a "Deny Access Profile".

    You can set the rule the way you like with allow or disallow of Device Types.

     



  • 5.  RE: ClearPass and non 802 devices

    Posted Feb 25, 2020 10:44 AM

    Can you send me a link on how to do this - just might work.  Thank you



  • 6.  RE: ClearPass and non 802 devices

    EMPLOYEE
    Posted Feb 25, 2020 11:56 AM

    Have you seen the attachment of my Reply?

    There is a picture which shows how to configure.



  • 7.  RE: ClearPass and non 802 devices

    Posted Mar 09, 2020 10:25 AM

    When a device authenticates successfully using dot1x, you flag it by setting an attribute in the Endpoint Repository (e.g. Dot1xEnabled = True)

     

    Then in your MAC Auth service for the non-dot1x SSID, you check that this attribute does not exist.

     

    Other than that I don't see how you can do it, since your non-dot1x service is not capable of detecting dot1x devices (by definition).