From owner-freebsd-current@FreeBSD.ORG Thu Oct 21 16:38:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 778C916A4CE for ; Thu, 21 Oct 2004 16:38:40 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB5CB43D1F for ; Thu, 21 Oct 2004 16:38:39 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CKfxW-0000WO-00; Thu, 21 Oct 2004 18:38:38 +0200 Received: from [217.227.156.227] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CKfxV-00032t-00; Thu, 21 Oct 2004 18:38:38 +0200 From: Max Laier To: freebsd-current@freebsd.org, rionda@gufi.org Date: Thu, 21 Oct 2004 18:38:12 +0200 User-Agent: KMail/1.7 References: <1098364825.16153.30.camel@kaiser.sig11.org> In-Reply-To: <1098364825.16153.30.camel@kaiser.sig11.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart15046940.ooo17Qs351"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410211838.20297.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 Subject: Re: Is PF nat broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 16:38:40 -0000 --nextPart15046940.ooo17Qs351 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 =3D "tun0" > wifi_if =3D "rl0" > eth_if =3D "fxp1" > > wifi_net =3D "192.168.1.0/27" > eth_net =3D "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=3D"YES" > ppp_enable=3D"YES" > ppp_mode=3D"ddial" > ppp_nat=3D"NO" > ppp_profile=3D"eth" > pf_enable=3D"YES" > pf_rules=3D"/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= =20 mentioning of the actual problem. To answer your question generally: No, PF nat is not borken. Not build into= =20 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 pfc= tl=20 =2Dvsr considers helpful). You might also want to join freebsd-pf@ instead = of=20 freebsd-current@ to further discuss this. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart15046940.ooo17Qs351 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBd+X8XyyEoT62BG0RAtFOAJ0ZDkdU/AUxrZj4Udb76xeYyC9eoACeJ7bD LdWTdvhern7B94Z8BexFUUs= =Gx5r -----END PGP SIGNATURE----- --nextPart15046940.ooo17Qs351--