FreeRadius sounds nice  … I was thinking of ... wifi request --> software api < does email exist ?> [if email exists and email is member: grant 30day pass |if email does not exist or if email is not member: grant 2 hour pass] store email, timestamp and mac in mongodb for customized messages and more

@freebee: Have you compiled in FreeBSD 8.4 and just substitute the FreeBSD 8.3 version ?.  If i wrong, just correct me. I reverted to an older port snapshot. But you can also simply substitute the 8.3 make with the 8.4 one, grabbed from a livefs iso for example.

Being insulting doesn't help

It's tcsh in case you haven't found that by now. Steve

Running an email server (let alone full-blown groupware) on a router is not a good idea from both security and administrative perspectives.

@charliem: I'm pretty sure he was asking about a suitable, up-to-date replacement, which (paywall or otherwise) is still missing AFAIK. Indeed, or at least a place to eventually restart one.

There isn't an automatic background check for that – If there are upgrades they are only shown when the package list is viewed. However if you add the "Installed packages" widget to the dashboard it will check and blink at you when an upgrade is available when the dashboard is loaded.

gonzopancho, is there any manual/documentation on building pfSense ? I got the tools repo, but got no further :( thanks, none

Stuck beacon log spamming can be greatly reduced by setting the sysctl hw.ath.bstuck to something higher. I have it set to 8 in the System: Advanced: System Tunables: table. This is much less of a problem now that wireless have their own logs though. Steve

2.4.9_2kg v0.42 would be what you want, as it integrates my fixes. (It hasn't been thoroughly tested on the mod_security side, though… :/)

Any fix on this? I am having the exact same issue.

There is no easy way to do this currently.  One SSH key per account.

On master branch: The test was expanded by: https://github.com/pfsense/pfsense/commit/629f07c3312bd5bbf9f4e0d39809dfd3a8278006 11 Nov 2013 Then fixed up again by: https://github.com/pfsense/pfsense/commit/635c00d36d96ceee00301ae593985410061ec16e 28 Dec 2013 But then the whole piece of code was removed by: https://github.com/pfsense/pfsense/commit/83c0dc1d1ea154c0096f6a291f51944d057f5241 12 Apr 2014 and these have also been applied on 2.1 branch. So for some reason the test has been removed completely from the official code. That is why it is not there in recent releases.

Looks good now - thanks @jporter!