Captive Portal with no authentication works on clients but not on server
-
I have activated CP with no authentication in pfsense and the client PCs are getting the CP page successfully.
The problem is that the Domain Controller itself does not get the CP page, it gets a Timeout browser error page.
Obviously the clients and the server are on the same network and use the same DNS server, which in the DC is itself.
The server does not have the windows firewall active and does not have any antivirus.
The server's NIC has static IP as this is the PDC.DHCP runs in the pfsense, and I have a Host override and Domain override in DNS Resolver to point to the DC and Domain so pfsense can ping the DC and the internal clients by name.
-
Are you sure putting your DC behind a captive portal is the best idea you can come up with? Seems like a recipe for disaster to me.
If I HAD NO OTHER CHOICE I would probably just add the DC IP address as a pass through.
-
The server does not have the windows firewall active and does not have any antivirus.
If it were my business, I'd be far more worried about this than whether my DC could access a CP page!
-
The server does not have the windows firewall active and does not have any antivirus.
If it were my business, I'd be far more worried about this than whether my DC could access a CP page!
This a test system running on VMs and is behind the pfsense firewall which is actually not directly connected to the Internet.
-
Are you sure putting your DC behind a captive portal is the best idea you can come up with? Seems like a recipe for disaster to me.
If I HAD NO OTHER CHOICE I would probably just add the DC IP address as a pass through.
The DC IP is already a pass through. The DC is also the DNS and the clients need clear pass to the DNS for CP to work.
The situation is that I am planning to use CP for squid authentication. The DC will also be filtered by the squid and will like the users to authenticate even on the DC.
If CP does not work on the DC, then they will not be able to authenticate to squid, then wont have access to the Internet.
Currently users authenticate to squid by freeradius. My goal is to authenticate squid -> CP -> freeradius on all machines including the DC.
-
so you have pc on lets call it 192.168.0.0/24 so say pc is 192.168.0.100 and DC is 192.168.0.101 and lets call your pfsense box 192.168.0.1
Your saying pc can get to CP when what happens when they try and go to www.pfsense.org ? And when DC tries to do the same thing in his browser he gets timeout?
Is the proxy set to use a proxy? Your saying pc uses DC for its dns 192.168.0.101 and DC points to itself for dns 192.168.0.101 or loopback?
Here is the thing pfsense doesn't give 2 shits if its a client os or a server os.. It can not even tell.. So if your saying all your other devices work then you need to look to the DC on why its not working.. Wrong gateway? DNS not working? Using a proxy? etc. etc..
-
This a test system. At this moment the browsers do not have the proxy configure and there is a Firewall block to the HTTP/HTTPS ports from the network so they will not reach Internet. Only pfsense is allowed to pass to those ports.
But yes, the PC does get the CP while the DC does not. The DC points to itself as DNS to the net IP not the loopback.
The gateway is set to the pfsense IP on the DC and the PC. The DC is static IP and the PC is DHCP set. They all ping successfully to each other.
From the DC I connect to the pfsense WebConfigurator. The WebConfigurator runs on HTTP.I know it is weird that CP does not work on the DC but that is why I am looking for help.
-
So the PCs point to pfsense for dns while the DC does not..
Point the DC to pfsense for dns.. Then what happens
-
Thr PCs gateway is pfsense. DNS for the PCs and DC is the same DC. DC has the DNS role for the Domain. The DHCP role is hold by the pfsense but sets the DNS to be the DC.
-
Why not just do DHCP on the DC? Why do people insist on drinking only half the glass of microsoft koolaid?
DHCP/DNS on pfSense has nothing to do with captive portal.
-
In my case the DHCP in pfsense provide more functionality. In the near feature a wireless router will connect to the network and DHCP relay will be used.
Besides every one keeps telling me that for CP to work the DHCP has to be handled by pfsense. You are the first that tells me otherwise.
-
Not true at all.
For CP to work you have to adjust your DHCP pool size and lease times to accomodate your captive portal timeouts. You cannot use a DHCP server that does not allow you to do this.
This is the first time I have ever heard anyone say that pfSense DHCP server is more capable than that in Windows Server.
I am still unclear as to exactly what the problem is that you are having.
-
The dhcp server in windows server, especially 2012 or above is more than capable and provides all the features if not more than the dnsmasq dhcp server being used on pfsense. And it also is integrated right into DNS for AD that always it to register clients that do not register in dns themselves, etc.
If you are running a MS AD shop there is ZERO point to running dhcp/dns on pfsense. Those functions are there to provide those services on a network that does not have dns/dhcp services already. If you are running a MS house with servers then you have no use for the dhcp/dns that pfsense can provide.. Unless your running like really really old windows..
I would be very interested in what feature of dhcp in pfsense your using that is not support or functions better than the MS dhcp..
-
The discussion of were the DHCP role should be is nice, but changing the place where it runs does not change that the CP is not being called on my DC.
If the DHCP place does not have to be in the pfsense for the CP to work then why changing the DHCP to the DC will make the CP to be called in the DC?
Since this is a test system. I will make the change to see how it works.
-
OK. I made the DHCP to be in the DC. CP is working on the clients but it is not working on the DC.
So the DHCP to be in pfsense is not a requirement for CP. This should be made clear on the WIKI pages.
Any way my problem is still active.
-
By the way this is important for controlling bandwidth in the DC with freeradius2 / CP combination when Authentication is enabled.
-
I realize that the CP can not be active for the DC/DNS. The DNS needs continues and full access to the internet to be able to resolve the addresses.
If CP were active the DNS will fail and therefore every machine pointing to that DNS will fail.
So not working CP in this DC/DNS is probably an intentional design in pfsense.
I guess that if I want to control some bandwidth in this server I will have to add its MAC address in the CP and some how hardwired the MAC to freeradius. That is for another thread.
