I appreciate the clarification. I was able to get this working by setting up both the LAN and the DMZ controllers in the PacketFence switch configuration. It was also necessary to setup the access control lists on the LAN controller. The ACL was already configured on the DMZ controller, but I¹m not sure if it is even needed there. No harm in having it defined in both places, though.
Thanks, _______________________________________ Chris Mielke | Lead, ISS Network Systems Drake Technology Services (DTS) | Drake University T 515.271.4640 E [email protected] On 11/5/14, 12:53 PM, "Fabrice DURAND" <[email protected]> wrote: >Hello, > >with WLC Web auth you don´t need the dhcp traffic since we do a link >between the radius request and the captive portal (it´s why you have a >redirect url like http://192.168.0.1/cep1234 , 1234 is a session id that >contain information about the device). > >I remember with another client we did the same configuration and we >defined define the mac-auth configuration on the DMZ WLC (normal radius >server not freeradius) and the traffic was tunneled to the internal WLC. > >You probably have to defnie the 2 WLC in Packetfence switch configuration. > >Regards >Fabrice ------------------------------------------------------------------------------ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
