Hi this is a step by step on how to configure an SSID in a functional Cisco WLC (8.10) for Guest Authentication and MAC Caching using Aruba Clearpass General Steps (this guide assumes you have correctly configured the Clearpass side) Create an Authentication Server (The secret is the same as the one configured in Clearpass) Create an Accounting Server (The secret is the same as the one configured in Clearpass) Configure the WebAuth login Page (use the configured guets login page in Clearpass) Make sure the Web Auth Certificate points to the virtual IP in the WLC Create the FlexConnect Access List (or IPV4) Make sure WebAuth SecureWeb is enable Configure the SSID with the appropiate settings 1.- Create an Authentication Server 2.- Create an Accounting Server 3.- Configure the WebAuth login Page (in this example is; guest.demo-clearpass.net/cisco_login.php) Note.- In order to avoid the security warnings in the conencting devices, install the appropiate cert...
Hi, today I'm gonna show how to interact with the Aruba OS version 16.10 switches API using postman. My intention is that you know how to construct the request using headers, parameters and the body of the request. The first things to start working with the switch API are: to have administrative access to the device and to make sure of the switch version so you can look for the appropiate document. Remember, APIs can change form version to version. You can use the command: show version. In my case is 16.10 Then you can make a quick search in google like "Aruba switch 16.10 API" to get the document and find out what are the option provided in the API. In the document you will find examples using curl and that's why i'm writting this in postman, so you have options. Now, let's do 4 thing so you can use the API: Make sure the REST interface is enable or enable it Login to the device API Construct a GET request Construct a POST request Make sure the REST inter...
Hi, in this post I would tell you how to be sure which WiFi channels are supported by a wireless client so we can configure wireless solutions that will work with the endpoints in the environment. I normally approach this topic in 2 ways 1. Directly in the wireless client This one is the obvious option but, in my experience, the majority of wireless clients don't show that in any part of the configuration. Because wireless clients are very different and their configurations menus too there's no way to show a "common" path to see the supported channels(if the wireless client shows them) 2.- Use a wireless adapter in monitor mode and wireshark to see an Association Request paquet from the client. In the following images we'll see where in the association request we can see that information. The fastest way to do it is to follow these steps: Put the wireless adapatar in monitor mode in the AP channel we'are going to connect the wireless client Open wireshar...
Comments
Post a Comment