Re: Is PF nat broken?

On Thursday 21 October 2004 15:20, Matteo Riondato wrote:
> I switched from PPP -nat + IPFW to PF for nat and packet filtering.
> It seems to me that nat does not work with pf:
> This are my rules in /etc/pf.conf :
>
> ext_if = "tun0"
> wifi_if = "rl0"
> eth_if = "fxp1"
>
> wifi_net = "192.168.1.0/27"
> eth_net = "192.168.0.0/29"
>
> [snip]
>
> nat on $ext_if from $wifi_net to any -> ($ext_if)
> nat on $ext_if from $eth_net to any -> ($ext_if)
>
> [snip filtering rules]
>
> In rc.conf I have
> gateway_enable="YES"
> ppp_enable="YES"
> ppp_mode="ddial"
> ppp_nat="NO"
> ppp_profile="eth"
> pf_enable="YES"
> pf_rules="/etc/pf.conf"
> [snip]
>
> Please note that I'm using pf.ko, not in-kernel support.
> There isn't a "nat enable yes" line in /etc/ppp/ppp.conf
> Any help will be appreciated.

Well, could you try to tell us what exactly the problem is? I don't see any 
mentioning of the actual problem.

To answer your question generally: No, PF nat is not borken. Not build into 
the kernel nor as a module. I am sure as I have it running.

Please follow up with more details about your setup (tcpdump, pflog and pfctl 
-vsr considers helpful). You might also want to join freebsd-pf_at_ instead of 
freebsd-current_at_ to further discuss this.

-- 
/"\  Best regards,                      | mlaier_at_freebsd.org
\ /  Max Laier                          | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | mlaier_at_EFnet
/ \  ASCII Ribbon Campaign              | Against HTML Mail and News