I've actually tried with the following, minimalist ruleset, and gotten
the same outcome.
Notice I included a rule of each type (nat, rdr, pass, block).
vlan31="vlan31"
vlan95="vlan95"
vlan710="vlan710"
table { 192.168.1.1 }
table const { 192.168.2.2 }
table persist { 192.168.3.3 }
set optimi
Did you ever post your ruleset and example tables ? I don't think pf
changed that much between 8.2-RELEASE to 8.3 as it stands now in the
aspects that would effect this outcome.
I am on 8.3-STABLE and the configuration of rules sounds similiar to
yours but I am not exhibiting any problems. Rule o
Sending to -pf since nobody in -stable seemed interested.
Kindly let me know if I can be of assistance to track down the issue.
For the record, a source update against RELENG_8 today (2012/04/12)
did not show any updated file regarding PF, so I guess this still is
an issue.
-- Forwarded
On Thu, 12 Apr 2012 15:01:46 +0200
Ermal Luçi wrote:
> Hello,
>
> On Thu, Apr 12, 2012 at 1:16 PM, Theodor-Iulian Ciobanu
> wrote:
> > Hello,
> >
> > I came across this same issue yesterday on a system I have just set
> > up. I'm currently using the default kernel:
> >
> > FreeBSD changeme 9.0-
Hello,
On Thu, Apr 12, 2012 at 1:16 PM, Theodor-Iulian Ciobanu
wrote:
> Hello,
>
> I came across this same issue yesterday on a system I have just set up.
> I'm currently using the default kernel:
>
> FreeBSD changeme 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30
> UTC 2012 r...@farrell
Hello,
I came across this same issue yesterday on a system I have just set up.
I'm currently using the default kernel:
FreeBSD changeme 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30
UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
amd64
with pf obviously loaded as a m
