snmp shouldn't hurt too much, especially if you're just grabbing a few stats off the box.

Freeradius appears not to be a working option. @jimp: I don't think anyone got around to finishing FreeRADIUS up to work on ALIX. It needs a fair amount of disk space in /var/ (a ram disk) to write its database and I think as it is it would be lost at reboot even if it did work. So it looks like freeradius is not a option. - Does anyone have any ideas for a simple solution to provide just a handfull of users a data quota ?  If not pfsene, a similar type app/distro.  Or even a comercial box.

@jimp: Did you read the message under the setting? The setting is gone because it is no longer needed; The directions you are following are outdated. Filtering happens on all bridge interfaces automatically now, so essentially the setting is checked all the time. The message was left there to avoid questions like this, it's fairly self-explanatory… Thanks!

1.2.3 is the current version of pfSense.  This is very likely a bug which was fixed.

Yes of course it has. It is "always on". Because if you shutdown correctly it will not power on again if power fails and then comes back… bec the electricity is not fully away cause of the UPS. greetz

Well, don't know much about the product/installation, just trying to make our FW admin "see the light" after having his mighty ASA cluster going havoc many times… Thanks a lot!

Looks like that error just means that packets were received out of order. Could be from a lossy WAN connection or some other kind of problem with the connection between where the client are server reside. The interrupted system call could be an issue with the router at the client site, but it's hard to say. Google shows lots of hits on that exact error that may be enlightening.

Incase someone asks why am I doing this and not <something else="">, it is because I am trying something and I finished it, only this last step remains, sending Access-Accept packet.</something>

Great program!  ;D Fascinating results. Takes a while though. Googles DNS no where near the quickest for me, however it's not surprising they seemed quicker to me as my ISPs DNS servers are returning hundreds of errors!  ::) Steve

OOh thanks I miss that point, it's very closed but I cannot see. Thank alot I will try. @SeventhSon: Couldn't you use Reauthentication every minute? Then you don't have to send anything, pfSense will check if the user still has access, otherwise disconnect the user.

Hmm, well it is hooked up to a UPS. I'll try it without the UPS. EDIT: same thing either way : /

Source can be found under the Development heading of the home page and more pointers can be found in the development sub-forum. Obviously you can make changes, you just need to ensure you comply with the licenses that come with it.

you can always install NRPE, then create your local check inside of the pfsense box, and get the data from Nagios using NRPE

This is a post I wrote on my blog. This is one working solution. http://blog.magiksys.net/node/1 Regards. Alain

If I recall correctly, ntpdate is supposed to run during startup to sync the clock with the specified reference clock. Then ntpd runs to nudge the local clock from time to time to keep it in step with the reference clock. ntpdate won't act if ntpd is running. See the FreeBSD man pages at http://www.freebsd.org/cgi/man.cgifor more information on ntpdate and ntpd. From what you have said it seems likely the hardware clock is way out of spec. I have a recollection a PC clock shouldn't drift by more than about a second a day. The software may not be able to cope with a clock so far wrong. Depending on the CPU and chipset, it is sometimes possible for FreeBSD to choose an alternate clock source which might be more accurate than whatever is being used now.

yea I now suspect that the CF was exactly the failure had issues writing the beta5 to it chucked it and got a new one.. this thread can be killed :)

@wallabybob: @BlueToast: I found a problem with this. The dnsomatic API documentation at http://www.dnsomatic.com/wiki/api says in the section Update Parameters "To update all services registered with DNS-O-Matic to the new IP address, hostname may be omitted or set to all.dnsomatic.com (useful if required by client)." Ok, yes, this worked. Thanks!