Captive portal with cisco WLC
I'm setting up a captive portal for an open SSID on serveral Cisco controllers. I'm currently using v1.2.3 and am wondering if I have the interfaces set up properly. The goal is to have one interface set up for management from my internal network and possibly 1 or 2 WLANS use the captive portal for Radius authentication when visiting a web site. The WLAN currently has a separate DNS and DHCP servers and I'd prefer not to use PfSense for those functions. My current interface setup is as follows:
WAN (internal network)
LAN (WLAN Sits in Cisco Firewall context)
I've previously set up v2RC3 and had no issues but I only used the WAN interface but seem to be having more issues with 1.2.3. I have no interest in using the firewall functions of PfSense at this point. Whats the best way to set this up?
I've had good results with captive portal from 2.0 RC3 snapshot builds.
I've not used captive portal from 1.2.3.
Are you reluctant to use 2.0 because its still release candidate status?
Yes but I'm not opposed using v2RC3 if it's stable and works well. Will I need to set my wireless controllers default gateway to the pfsense LAN IP address?
Will I need to set my wireless controllers default gateway to the pfsense LAN IP address?
I'm not familiar with those wireless controllers but I would guess:
No if the wireless controller gets its "WAN" IP address from pfSense by DHCP.
Yes if you have configured a static IP address on the wireless controller's "WAN" interface.
One problem with using snapshot builds is that there might be a temporary bug introduced as part of a fix for a different. I've had good results with the official RC3 built Tue Jun 21 17:40:54 EDT 2011 and with the snapshot build in file pfSense-Full-Update-2.0-RC3-i386-20110719-2331.tgz