Current FreeBSD problem reports
Critical problems
Serious problems
S Submitted Tracker Resp. Description
---
o [2005/06/15] kern/82271 pf [pf] cbq scheduler cause bad latency
f [2005/07/31] kern/8437
/etc/rc.d/pf will happily let you load a rules file into pf, but
unfortunately won't let you load table data if it doesn't fit on a single
line or if you want to store table data in other files for any reason.
pfctl only allows one -f option, so creative use of pf_flags won't help,
so I added
On Mon, May 29, 2006 at 03:37:58PM -0500, PauAmma wrote:
> /etc/rc.d/pf will happily let you load a rules file into pf, but
> unfortunately won't let you load table data if it doesn't fit on a single
> line or if you want to store table data in other files for any reason.
>
> pfctl only allows o
On Monday 29 May 2006 22:37, PauAmma wrote:
> /etc/rc.d/pf will happily let you load a rules file into pf, but
> unfortunately won't let you load table data if it doesn't fit on a single
> line or if you want to store table data in other files for any reason.
From pf.conf(5):
table persist file
On Mon, 29 May 2006, Gergely CZUCZY wrote:
what's the problem with a ruleset like
table persist file "/etc/pf-abuse_ssh"
table persist file "/etc/goodguys"
Er, nothing wrong with it, only with me for failing to spot it despite
repeated readings of pf.conf(5) and eventually deciding to reinv
On Mon, 29 May 2006, Max Laier wrote:
From pf.conf(5):
table persist file "/etc/spammers" file "/etc/openrelays"
Too easy?
Too obvious in the doc for me to spot, I guess. :-( *pries foot from
mouth, wipes egg off face*
___
freebsd-pf@freebsd.or
Peter
Thanks very much for the link..
Here my new file pf.conf
==
ext_if="xl0"# replace with actual external interface name i.e., dc0
internal_net="168.96.200.0/24"
table { 168.96.200.9, 168.96.200.8, 168.96.200.54, 168.96.200.196 }
table {
Peter
Thanks very much for the link..
Here my new file pf.conf
==
ext_if="xl0"# replace with actual external interface name i.e., dc0
internal_net="168.96.200.0/24"
table { 168.96.200.9, 168.96.200.8, 168.96.200.54, 168.96.200.196 }
table {
