the.it.dude I tested around some things more. What I found in the pftop log was that for nearly every click on a link in the WebGui, the LightHTTP Server starts a new session. That OK because the sessions have a small expiration time of 60 – to 90 seconds. But after some time there will be a session with an expiration time of over 85000 seconds and after this the WebGui is not reachable anymore. Also after some time there will be a process called keglim and this has also the long running session time. Googling this process leads you to a thread in a FreeBSD forum. http://forums.freebsd.org/archive/index.php/t-11880.html It seems to be really a driver problem in FreeBSD with the Broadcom Network Cards. I changed the interface to one of the Intel NIC´s and do not have any problems at all with the WebGui for days. So at this time it works for me in this way not to use the Broadcom NIC´s an just use 8 of the network cards in the servers. In case of Endian and ZeroShell I agree with your opinion. These distributions are not really an alternative to pfSense at this time. Olaf.

Thank you for the answer! I guess that adding a user @/var/run/htpasswd will work, but with no privilege option. :-) Best Regards!

Just installed v1.2.3 from scratch and ran through my entire config without any issues…  Definitely doesn't like something about 2.0.

the issue is in confusion. i use m0n0wall for this, as the admin of the hotspot get lost in full GUI. i understand the the main issue is security, and to take care of critical configuration. i hope this find the light, and best congratulations for RC1 2.0 is real OS allow you to use almost every thing FreeBSD. regards Mohammed

The link to my interface is at this post…http://forum.pfsense.org/index.php/topic,35384.msg183476.html#msg183476

If you mean the firewall rule list, that's all in /usr/local/www/firewall_rules.php, the icons are printed around line 492. As to what specific code you need to change to make them behave the way you want, that isn't quite so easy to answer. I'm not sure if there are line breaks, or if the table cell needs widened, or what. Could be any one of half a dozen or more things.

You could activate the SNMP service and have cacti poll the data, but otherwise there isn't a way to push them as-is. You could have some kind of automated process that connected every so often and dumped the data, and then restore it into an rrd file on the cacti server, but that isn't ideal either.

Running a web server on a firewall is not a value-add, its a massive security hole.  What you propose is the definition of a "very bad idea"

Edit /etc/inc/auth.inc and change this line:         header("WWW-Authenticate: Basic realm=\".\""); Though of course that won't survive a firmware update. On 2.0 the auth system is completely different so this isn't relevant there.

Probably not, since even the 80 column view spills over the page I doubt it would be added as a standard option. You could always edit the source of that page and add -w 120 to the command it runs…

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.