Captive Portal with no authentication works on clients but not on server
-
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.
