[Bug 207305] An issue related with pf

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207305

            Bug ID: 207305
           Summary: An issue related with pf
           Product: Base System
           Version: 10.2-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: standards
          Assignee: freebsd-standards at FreeBSD.org
          Reporter: techriyaz at gmail.com
                CC: freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

Hi, 

It seems like a bug pf on 10.2p9 the option "self" gives the error :  "no
translation address with matching address family found."

Here is my pf configuration : 

if_ext="vlan150"
if_ext1="vlan100"
default_gw="10.0.0.1"
default_nat="8.1.12.3"
all_ifs="{" $if_ext $if_ext1 "}"
nat on $if_ext1 from self to ! $default_gw -> $default_nat
#nat on vlan100 inet from 127.0.0.1 to ! 10.0.0.1 -> $default_nat
#nat on vlan100 inet from 10.0.0.4 to ! 10.0.0.1 -> $default_nat
#nat on vlan100 inet from 10.0.1.4 to ! 10.0.0.1 -> $default_nat
#nat on vlan100 inet from 8.1.12.2 to ! 10.0.0.1 -> $default_nat
#nat on vlan100 inet from 6.19.1.8  to ! 10.0.0.1 -> $default_nat
pass in quick on $all_ifs inet keep state
pass out quick on $all_ifs inet keep state


Error if i reload it : 

pfctl -f /etc/pf.conf
No ALTQ support in kernel
ALTQ related functions disabled
/etc/pf.conf:6: no translation address with matching address family found.
pfctl: Syntax error in config file: pf rules not loaded

if i replace the line : 
nat on $if_ext1 from self to ! $default_gw -> $default_nat

per : 

#nat on vlan100 inet from 127.0.0.1 to ! 10.0.0.1 -> $default_nat
#nat on vlan100 inet from 10.0.0.4 to ! 10.0.0.1 -> $default_nat
#nat on vlan100 inet from 10.0.1.4 to ! 10.0.0.1 -> $default_nat
#nat on vlan100 inet from 8.1.12.2 to ! 10.0.0.1 -> $default_nat
#nat on vlan100 inet from 6.19.1.8  to ! 10.0.0.1 -> $default_nat

i can able to reload pf without any issue. Thanks to see. 


Regards, 
Marecar Riyaz

-- 
You are receiving this mail because:
You are on the CC list for the bug.