Date: Thu, 21 Nov 2002 21:16:17 -0600 From: Rich Neswold <rneswold@earthlink.net> To: Matthew Emmerton <matt@gsicomp.on.ca> Cc: stable@FreeBSD.ORG Subject: Re: ppp works, but natd not working Message-ID: <20021122031617.GA94687@harpo.neswold.local> In-Reply-To: <00c801c291b5$747862f0$1200a8c0@gsicomp.on.ca> References: <200211210454.gAL4sFIV063929@arch20m.dellroad.org> <01cb01c2911b$83e59180$3164a8c0@number6.loop.bpa.nu> <00c801c291b5$747862f0$1200a8c0@gsicomp.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Wasn't it 21-Nov-2002, at 06:26PM, when Matthew Emmerton said: > Since ppp has built in NAT support (enabled with the -nat flag), is there > any special reason you using natd? This is a very good question. If you're using ppp, you really should use the built-in NAT support. If you're only using ipfw to restrict incoming ppp traffic, I'd also recommend using the filtering provided by ppp. The IP filtering and NAT support in ppp work great. --=20 Rich Neswold =20 efax: 1.240.536.7092 web: home.earthlink.net/~rneswold icq: 174908475 --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE93aGAZmE+i9FKxdwRAhspAKDySO7kxLBbTLdgLkXjnwT3S2FYfQCfWfsw IAQlnlk1vYnz+oOJ/2umwMU= =WUx2 -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021122031617.GA94687>