dns eror when i enable captive portal on pfsense (last stable realse)
-
hi
i have configured pfsense completely
but when i activate captive portal on interface "switch" which is my local network
it won't redirect to captive portal page .
I got error which is DNS
i am running pdc-srv 2019 , my dhcp is runnig on my pdc-srv
in scope option i have defined dns servers : Like
192.168.14.10 which is my pdc-srv address
8.8.8.8 which is google
192.168.100.10 which is pfsense
and in dns server setting part on pfsense i have defined only 192.168.200.1 which is my routeri have 10 vlans which has diffrent range of ip address
like vlan 14 : 192.168.14.0/24
.
.
.
vlan 90 : 192.168.90.0/24
i create A record in dns on pdc "192.168.100.10 which is my pfsense lan ip address"
on the wan side i have router and i have configured dynamic dns like my ISP dns and google dns
clients in order to obtain ip address from dhcp i have configured " ip helper-add 192.168.14.10" in my switch core which is 3750x-12ss
and of course i have default route in my switch that routes all packets to 192.168.100.10(pfsense)
i have configured dhcp relay on pfsense , i thought it was the problem , sadly it wasn't
any ideas ??? tnx
:-( -
@hamedlynx said in dns eror when i enable captive portal on pfsense (last stable realse):
any ideas ??? tnx
Noop.
To many 'things'Make about : make a LAN 192.168.1.1/24 as a LAN.
Another LAN called ... OPT1 ;) using 192.168.2.1/24
On OPT1, put a firewall pass all rule.
Add a DHCP server on OPT2 with a pool.No DHCP relay, no 'router', no VLANs, nothing.
When that works, add 'one' thing, and test severally.
It works ? Add something else. And test.Something breaks ? you know what is was.
-
@gertjan
hi there thanks for response
well this is my topology
at moment everything is fine and working
all clients at all vlans has the internet acc
but omm again captive portal wont respond
even though it redirects to captive portal page but it doesn't show anything at all
i disbled dhcp realy
put dns server setting on google dns and my isp dns
but not working :-( -
https://docs.netgate.com/pfsense/en/latest/troubleshooting/captiveportal.html
When you're wired up with the portal, over wire or Wifi, DNS should work.
The only DNS that gets passed, is not 8.8.8.8 - as everything is blocked.
The DNS that works is : the portal interface, port 53. So the connected user should use that one, and not some 8.8.8.8.Then a http:// (not https://...) request should be possible .... etc.