Bug 207305 - An issue related with pf
Summary: An issue related with pf
Status: Closed Works As Intended
Alias: None
Product: Base System
Classification: Unclassified
Component: standards (show other bugs)
Version: 10.2-RELEASE
Hardware: amd64 Any
: --- Affects Many People
Assignee: freebsd-pf (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-18 11:47 UTC by Riyaz Marecar
Modified: 2016-02-25 22:38 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Riyaz Marecar 2016-02-18 11:47:52 UTC
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
Comment 1 cmb 2016-02-20 00:07:17 UTC
This isn't a bug, that's not a valid config and it's correctly failing with a syntax error. It's (self) not self in that usage.
Comment 2 Kristof Provost freebsd_committer 2016-02-25 22:38:14 UTC
Closed as per comment #2.