I’m trying to configure the Aruba Mobility Controller 7010 to work with PacketFence. I want PacketFence to serve as the captive portal for people who want to access the Wi-Fi network.
I configured the VLANs and created the roles (Visitor-Registered (VLAN 600) and Visitor-Unregistered (VLAN 3)) on the controller. I added the controller as a switch in PacketFence (type Aruba Network). I set up Role by Switch Role, assigning the role Visitor-Registered after authentication. When a user connects to the Visitors SSID, they are correctly redirected to the PacketFence captive portal. I can see that they are on the correct VLAN (3), and on the controller it shows that they are in the Visitor-Unregistered role. After authentication on the portal, I can see on the controller that they receive the Visitor-Registered role, but the user cannot obtain an IP from VLAN 600, which is the VLAN for this new role. They continue to have an IP from VLAN 3, the registration VLAN. Is there any way to force the client to obtain a new DHCP address from the infrastructure after the role change on the controller? Do you have any idea what might be causing this?
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
