Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-10-2019 05:45 AM
Hello,
we are currently implementating the ClearPass.
A smartphone is connection to the company SSID and should be automatically move into another VLAN where only public internet available. So far so good and it is working but we don`t want to assign a VLAN on the ClearPass. We are using at each location a different VLAN for the public Internet. Therefore we would like to assing only a VLAN name on the ClearPass instead a VLAN number.
Question:
Is there the possibility to implement this in a WING environment?
We are using WING 5.9.1.5 on a VX9000. The APs are connected via a MINT L2 Link.
Regards,
Stefan
we are currently implementating the ClearPass.
A smartphone is connection to the company SSID and should be automatically move into another VLAN where only public internet available. So far so good and it is working but we don`t want to assign a VLAN on the ClearPass. We are using at each location a different VLAN for the public Internet. Therefore we would like to assing only a VLAN name on the ClearPass instead a VLAN number.
Question:
Is there the possibility to implement this in a WING environment?
We are using WING 5.9.1.5 on a VX9000. The APs are connected via a MINT L2 Link.
Regards,
Stefan
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-10-2019 06:30 PM
Stefan,
Yes, this is possible. WiNG does have a VSA for "WING-VLAN-NAME" that can be used to specify a string name value in a RADIUS Access-Accept response.
Along with setting that side up, you would also need to create the string name Alias within each RF Domain (each RF Domain representing a different Location for you) and the different VLAN that should be used for that RF Domain (The VLAN Alias in each RF Domain would then have a name-to-VLAN mapping that you specify)
***The Attribute Name shown below in green is incorrect in the graphic. It should read "WING-VLAN-Name"
Yes, this is possible. WiNG does have a VSA for "WING-VLAN-NAME" that can be used to specify a string name value in a RADIUS Access-Accept response.
Along with setting that side up, you would also need to create the string name Alias within each RF Domain (each RF Domain representing a different Location for you) and the different VLAN that should be used for that RF Domain (The VLAN Alias in each RF Domain would then have a name-to-VLAN mapping that you specify)
***The Attribute Name shown below in green is incorrect in the graphic. It should read "WING-VLAN-Name"
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-11-2019 09:41 AM
Hello Chris,
wohoo... That`s it. It works 
Thanks for your support.
Regards,
Stefan
wohoo... That`s it. It works 
Thanks for your support.
Regards,
Stefan
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-10-2019 06:30 PM
Stefan,
Yes, this is possible. WiNG does have a VSA for "WING-VLAN-NAME" that can be used to specify a string name value in a RADIUS Access-Accept response.
Along with setting that side up, you would also need to create the string name Alias within each RF Domain (each RF Domain representing a different Location for you) and the different VLAN that should be used for that RF Domain (The VLAN Alias in each RF Domain would then have a name-to-VLAN mapping that you specify)
***The Attribute Name shown below in green is incorrect in the graphic. It should read "WING-VLAN-Name"
Yes, this is possible. WiNG does have a VSA for "WING-VLAN-NAME" that can be used to specify a string name value in a RADIUS Access-Accept response.
Along with setting that side up, you would also need to create the string name Alias within each RF Domain (each RF Domain representing a different Location for you) and the different VLAN that should be used for that RF Domain (The VLAN Alias in each RF Domain would then have a name-to-VLAN mapping that you specify)
***The Attribute Name shown below in green is incorrect in the graphic. It should read "WING-VLAN-Name"
