Hello Guys, I'm experiencing a lot of issues in configuring PacketFence's Captive Portal (Version 9.0.1) with Cisco's WLC (5508, software version 8.1). Basically I've tried to deploy the solution in two ways:
- The "Network Guide" one, where there is only 1 VLAN with ACLs on the WLC to permit only traffic to DHCP/DNS servers and PacketFence Portal. The issue here is the fact that the redirection does not work at all. The Radius parameter with the URL redirection is not filled with data and so the WLC doesn't redirect at all the traffic. This is an issue because I do not like the user experience, since being force to type an URL to log in and register the device is not good. - The second type of deployment I've tried to do is an interface in Registration mode, on a dedicated VLAN managed entirely by PacketFence, trying to use the VLAN change to grant internet access. In this case the Captive Portal works fine, but once I log into it is not recognized internet access and I get an error saying that internet access cannot be validated. If I try to disconnect the client and reconnect it, the VLAN is changed properly and everything works fine, but again this is not a good user experience and I cannot put in a production environment something that doesn't work properly. This would also be my preferred solution since it grants the best approach to security of course since I would be able to isolate the Registration VLAN and then with Access-List prohibit access to corporate network once the client in registered. Do you have any idea on how to solve these issues? I do think it is most likely a misconfiguration on PacketFence or maybe I'm trying to implement something that it is not supported by Cisco with its WLC?! Any help on this would be greatly appreciated, Ivan
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
