On 2/10/07, Dan Langille <[EMAIL PROTECTED]> wrote:
Hi folks,
Yesterday I rebooted a server to load a new kernel. After the
reboot, the firewall rules were not loaded.
$ grep pf /etc/rc.conf
pf_enable="YES"
pflog_enable="YES"
pf_rules="/etc/pf.rules"
I never checked for the rules until today
Hi folks,
Yesterday I rebooted a server to load a new kernel. After the
reboot, the firewall rules were not loaded.
$ grep pf /etc/rc.conf
pf_enable="YES"
pflog_enable="YES"
pf_rules="/etc/pf.rules"
I never checked for the rules until today and found this:
[EMAIL PROTECTED]:~] $ sudo pfctl
Hello,
after 6 weeks in HEAD I have received ZERO additional feedback! Does
anyone (other than avatar) care?
On Friday 29 December 2006 15:18, Max Laier wrote:
> I just put this in HEAD, a diff to RELENG_6 is attached. Please follow
> avatar's example and test and report back!
>
> Just apply a
Volker <[EMAIL PROTECTED]> writes:
> I haven't found a way to use that mechanism to block such hosts for,
> say 120 minutes (which would be a great feature).
pfctl is in the process of growing an expire feature (in
OpenBSD-current now, in all likelihood part of the OpenBSD 4.1
release), but timed
