User profile assignment not working in NG (clients get default profile) [bis]

  • 1
  • Question
  • Updated 1 year ago
  • (Edited)
(Instead of hijacking topic made by Jonas Dekkers), I create my own.


Problem:
Clients receive only default profile instead of VLAN assigned by user profile 

Global Configuration :
15 sites with AP130

1 SSID with WPA Enterprise 802.1x

In one site, we have 3 VLANS:

Native vlan 172.16 
AP1 DHCP server (with NAT) :
 - mgt0.1 - vlan 2021 - IP 10.0.71.254
 - mgt0.2 - vlan 2022 - IP 10.0.72.254

AP2 DHCP relay :
- mgt0.1 - vlan 2021 - IP Primary DHCP Server 10.0.71.254
- mgt0.2 - vlan 2022 - IP Primary DHCP Server 10.0.72.254

Both AP can see the other on each VLAN (ping OK), no firewall beetween the AP

I use specific User Profile for separate Workstation OS and Mobile OS
  • vlan 2021 => workstation
  • vlan 2022 => smartphone
Here is a screenshot of the actuel configuration (I have to mask some details, sorry):

The others assignement rules (the other sites) are working. There is not "Client OS Type" configured on those).

What I am doing wrong ?

Best regards


-English is not my native language-
Photo of SLC-FR

SLC-FR

  • 4 Posts
  • 0 Reply Likes
  • confused

Posted 1 year ago

  • 1
Photo of SLC-FR

SLC-FR

  • 4 Posts
  • 0 Reply Likes
UPDATE

It's work with removing "Client OS type" from Rule Assignement
Photo of Tobias Protz

Tobias Protz

  • 61 Posts
  • 11 Reply Likes
Did you get rules working based on ClientOS at all?