So, may i get your words for:
table xxx { any !x.b.c/24 }
Thanks.
On 7/30/06, Jason Dixon [EMAIL PROTECTED] wrote:
On Jul 30, 2006, at 3:50 AM, Gustavo Rios wrote:
Hey folks,
i am structuring my first firewall server. I am having hard times with
the following building a tables that holds
i am structuring my first firewall server. I am having hard
times with
the following building a tables that holds every IPv4 address but
excludes a given range.
My initial idea was:
table xxx { 0/0 !x.b.c/24 }
But it is not acceptable.
How would you handle that?
By default, any
tableaddr-list = tableaddr-list [ , ] tableaddr-spec | tableaddr-spec
you need to seperate with , to make that rule work.
just to touch base on that, the brackets signify
the comma is optional. ( not the first time i've seen a sugestion
that someone needed to add/remove a comma for
On 7/30/06, jared r r spiegel [EMAIL PROTECTED] wrote:
anywhere you can put a comma, you can also leave it out; pfctl(8)
parses the rule the same.
--
I had commas give me problems around 3.7.
But you're right, it shouldn't give problems anymore.
4 matches
Mail list logo
