The ipfw firewall rules, put in place when the captive portal is activated, start with some rules letting through DHCP traffic. It's part of the default rule set.
When a device is hooked up, can you see DHCP traffic (DHCPDISCOVER) in the pfSense DHCP logs ?
If not, NIC is bad, cable is bad, or some switch device between user and pfSense.
Btw : you should keep LAN for admin purposes, and use a second interface - OPT1 - for the portal.
If remote admining is needed, use OpenVPN
@wakasavan said in DHCP Stop Working when captive Portal is enabled:
As long as captive portal enabled no Internet at all.
That's what a portal should be doing.
@wakasavan said in DHCP Stop Working when captive Portal is enabled:
I repair the the firewall but there is no issue there
What do you man ? You repaired something that wasn't broken ?
@wakasavan said in DHCP Stop Working when captive Portal is enabled:
Firewall can be accessed via WAN link but from local interfaced it is not working.
If a portal is activated on that LAN, then,except for obtaining an IP, nothing should work.
Exception : DNS requests ! Check that. But ok, if the device can't get an IP, all will be down.
@wakasavan said in DHCP Stop Working when captive Portal is enabled:
There was a power outage for a long time
The power of pfSense was shut down using the way it should ? Do you use a UPS ?
The file system is clean ? ( see very recent Netgate video on Youtube).