thanks casinmirad  ;D

@heper:

+1 to implement a nice webgui in future release if possible and time permits this, altho working with limiters might work.

it would be nice to maybe make a link with the dhcp leases and create groups by mac-address (like a fixed ip).

+1  :D

I delete old captive poartal that have no zone and create a new zone. I select PAP.
I guess the above error is gone, but I can't see any login user in Captiveportal status at the Dashboard.
I can see login user only at Status\Captiveportal\Myzone. Thanks anyway.

By the way…

Hardware here is a Supermicro 1u with 3.0GHz P4 processor, 4gb DDR RAM, 256Gb SATA w/RAID controller and 2 x 1gig Intel Pro1000 ports onboard.

Packages I'm running include Snort (the 2.5.1 pkg) in AC-BANDED mode with all ET & Snort rules selected except policy related, darkstat, lcdproc-dev, pfBlocker & Strikeback.  The only service available on the WAN IP is IPSEC VPN for getting back into my home office while on the road (me=road warrior/engineer)...no web, ftp, etc.

I have been offloading system logs to another server, but it was up and running fine when I noticed the problem.  I did shortly thereafter change the config to stop sending syslog traffic to the other server, as I'm about to turn all of it off and add that third network interface to the pf box.  But as I said, this happened last night as well with no apparent cause.  Any ideas would be appreciated.

Thanks!
Treffin

No, it doesn't work right now.

Thanks Phil, that's sorted!

Works fine on Win7 64 bit with the new OpenVPN 2.3 alpha2 release. Using it sucessfully with local user password and certificate authentication. Finally a reliable way to use IPv6 anywhere I like ;) Many thanks to the pfSense developers for implementing this!

Thank you for commit:

https://github.com/bsdperimeter/pfsense-packages/commit/1a1124da89e8832cd4fb7ce0ba01d06d96971362

I just submitted a pull request with a new system_gateways_edit.php - it implements lots of validation of the parameters in the advanced section. Also the explanations and error messages have been made correct and standardised. Previously there were lots of weird things that could be entered. Now I believe I have checked for all the obviously wrong conditions.

I've got exactly the same random message on a fresh install. What is the date of your snapshot?

@databeestje:

not touching that with a long stick. Someone else will need to apply.

One way of doing it would be to have a widget per interface, rather than having all interfaces in one widget, then the regular dashboard code could be used that's already in place.

Yeah, snort has a bunch of different optimization settings for memory/CPU usage. I've run into this problem as well and had to change my settings. I have a business I deployed it in with 100+ users and snort on the WAN interface. After a day or two it's up to 90% usage with a good amount of swap being used. Snort does seem to be a bit of a memory hog, but I found that optimizing the firewall algorithm to aggressive and playing with how many states pfsense can have etc in the advanced settings can help as well.. I guess it depends on your environment/traffic load

I have noticed this in the 2.1 snapshots where I have to now manually enable some packages such as pfblocker. The settings are saved, but the setting that enables it is not checked after upgrades.

It probably was a caching issue, but occasionally it can be from a leftover js file post-upgrade:
http://doc.pfsense.org/index.php/Dashboard_widgets_won%27t_update_(Stuck_at_%22Updating_in_10_seconds%22)

Found problem, in General settings was local DNS server wihtch is shutdown now, i wrote ISPs servers - nothing chancged, then i updated from pfSense-Full-Update-2.1-DEVELOPMENT-i386-20120720-0129.tgz , reboot and now its working

You are on the latest version. :)

the slow nanobsd issue has been here for a while in freebsd 8.3. We don't have a fix for that issue.