Captiv portal and vouchers integration with ssid on wlc 9800
-
@Gertjan Captiv Portal is working now. Problem was with WAN interface and DNS forwarder.
Best regards,
Jozy -
@Gertjan @johnpoz Hi guys, here I am again.
So, if you know or had the similar situation.As I mentioned above Captive Portal is working fine, but only working when Im connected to the same network not when enable wifi adapter.
When I try to reach CP while trying to connect to wifi it isnt reachable.
I have Cisco WLC configured and redirections to http://10.223.103.230:8002/index.php?zone=CaptivPortal& which is Captiv Portal it isnt working.
Whan I try to paste http://10.223.103.230:8002/index.php?zone=CaptivPortal&?switch_url=https://192.0.2.1/login.html&redirect=<website-name> while using the same network (10.223.103.58) it is working fine.
I have to monition that 10.223.103.x is wifi subnet.Problem starts when I try to reach Captiv portal while trying to enable wifi adapter and test SSID on both cell phone or PC not working, it doesnt redirects me to nowhere, I just get ip adress over DHCP which is configure on win server and other setup but CP not opening.
Do you know what could be the problem?
Best regards,
Jozy -
@Jozy said in Captiv portal and vouchers integration with ssid on wlc 9800:
I have Cisco WLC configured and redirections to http://10.223.103.230:8002/index.php?zone
You shouldn't be doing anything with captive portal on your wlc if you want pfsense to handle it - if your wifi devices are on a different network then on that network in pfsense setup the captive portal.
-
@johnpoz How should I reach Captiv portal over wifi if I dont put on SSID on WLC redirects me to http://10.223.103.230:8002/index.php?zone=CaptivPortal& ?
-
@Jozy your wifi should just connect your wifi to a wired network on pfsense. No captive portal in your wlc - just setup a ssid, and have your clients connect..
Their dhcp should come from pfsense. On whatever network this is - setup pfsense captive portal on that network.
-
@johnpoz I have wlc where all access points are added and managed by wlc.
So, what would be right setup? Since it is virtual macine where L3 interface would be, on my network l3 router?
For example if I have range 10.223.103.0 for dhcp, lan adress on pfsense it 10.223.103.10
Anyway I have to configure l3 and vlan on trunk and wlc to have access to that dhcp, once I try establish connection over ssid, right?
In that case i should configure Lan ip address as my dhcp relay, right?Jozy
-
@Jozy that is fine you use wlc to control you wifi, why not just use the captive portal features in wlc? But if you want to leverage captive portal in pfsense then the clients need to be on the same L2 network as a pfsense interface.. How they get dhcp be it from your wlc or pfsense doesn't really matter.. But they need to be on the pfsense network.
-
@johnpoz we want to use pfsense captiv portal due to vouchers which can be generated on pfsense.
Currently they are on the same L2 network, only difference is that dhcp is on win server and clients get ip add from that range but wlc redirection to pfsense captiv portal not working
-
@Jozy said in Captiv portal and vouchers integration with ssid on wlc 9800:
dd from that range but wlc redirection to pfsense captiv portal not working
What part are you not understanding??? If the clients are on a pfsense network, and they have to point to pfsense as their gateway. Your captive portal would be setup on pfsense on this network the clients are on.. There would be no redirection or setup of any captive portal anything in your wlc.
-
@johnpoz im not talking on setup any captiv portal on wlc but wlc is controller for all access points, so wlc is place where ssid is cofigured and there is policy you configure your clients to use pfsense captiv portal.
So, I dont understand if I need to have L3 configured on router, there are some details missing but dont know what? :)
What is right conf step by step? -
@Jozy who cares what setups up the wifi, doesn't matter if its a wlc that manages multiple AP, or stand alone AP or some wifi router being used as an AP.
When it comes down to it the AP is a bridge from your wifi to your wired network..
You have a network 192.168.100.0./24 -- your wifi clients are on this 192.168.100.0 network.. When they try and go to the internet via pfsense as say 192.168.100.1 pfsense captive portal says hey need to auth.
That is all there is too it.. The whatever that gets your wifi client on this network is not part of this process..
Yes you need to have an L3 on pfsense - how else would it route traffic for your wifi clients?? That are on this network..
If you want devices to use pfsense as the captive portal - they should use pfsense as their gateway, and dns most likely too. if pfsense is not the gateway off this whatever network it has zero to do with controlling any thing else on the network.. It can only control who can talk to it to go to some other network.. So yes it needs an L3, and these clients need to be on this same L2/L3 network if you expect to use pfsense as a captive portal.
