So I figured it out.  On the NAT rule I had to enable NAT reflection (the default setting is off).

Easy fix…

1)  Get access to the webGUI (after removing conflicting computer)
2)  Go back to the mac address box in the webGUI and blank it out.
3)  Click Save at bottom of page
4)  I had to reboot and the original mac address came back.

JH

/usr/local/www/themes/<theme name="">/</theme>

The suggested fix has been tested by me and applied in the latest 2.0 code.

awesome, thanks!

Thank you for your work !!!

Yes, this is very easy to do with pfSense.  You will want a firewall rule on the WAN interface which allows access to the port you're running your webGUI from the source IP in question.  Then you'll want to create a firewall rule on the LAN side (above the default allow rule) which blocks access to that same port from any source IP.

BUMP?

I'm having the same issue.

Did you manage to fix it?

For me, deactivating traffic shaper did the job. But this is not a solution :-(

Still searching for help.

then i suggest you do one of two things:

1. contact the person who was managing it before you
2. run nmap from a local machine using the command: nmap -p- -A 192.168.10.254
this may take some time, it will scan all tcp ports and try to connect to them to see what is running, look for a port that responds with:
"PortNumber/tcp open  ssl/http lighttpd"

Sorted it. The modem was giving pfsense the IP for the ISP gateway, which is not the same as the next hop gateway.

Normal operation has been restored :)

Thanks again for your help.

Hello,

You were wright now it works fine.
Sorry for my noob question and thanks a lot !

If you break its connection over the network to the ldap server, it should fall back to local database auth.

If that doesn't work, you could use viconfig at the console to edit out the LDAP auth selection from the raw config.

Hi,

any new information ? Is this a "problem" of how the "User Manager" is handling otional packages or is it a problem of me/my usage ?

Thx.

Are you using the embedded/nanobsd install? Try adding the "packet capture fix" package, since there was a bug that shipped with 1.2.3.