Date: Mon, 10 Sep 2007 11:16:39 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-questions@freebsd.org Subject: Re: natd / ipfw services on internal interface Message-ID: <fc321o$9b9$3@sea.gmane.org> In-Reply-To: <127823.54280.qm@web34607.mail.mud.yahoo.com> References: <127823.54280.qm@web34607.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig54869093AD563005315EB0F9 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Joe wrote: > I have a question about natd/ and ipfw. I am running natd on my extern= al interface and I have some services on my internal interface.=20 >=20 > The services seem to be getting their ip addresses nat'd and some of th= em work and some of them dont. =20 >=20 > Any idea how to prevent things from going into natd? You should specify more information about your setup, but generally you=20 should be able to just insert a rule like "ipfw add xxx allow ip from=20 mynet/mask to mynet/mask", where "xxx" is the rule-number BEFORE your=20 natd redirection rule-number and mynet/mask describes your internal netwo= rk. --------------enig54869093AD563005315EB0F9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG5Qt4ldnAQVacBcgRA+LdAKDJl/ZT+tg7EZAg1ymQW0SNAAp4cQCfQtYU 9vz3Y1B7ADnNBzqKESuDREY= =I1LU -----END PGP SIGNATURE----- --------------enig54869093AD563005315EB0F9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fc321o$9b9$3>