Date: Mon, 26 Jan 2015 22:33:11 +0100 From: Polytropon <freebsd@edvax.de> To: Maxim Filimonov <che@bein.link> Cc: freebsd-questions@freebsd.org, Luciano Mannucci <luciano@vespaperitivo.it> Subject: Re: Simple NAT Message-ID: <20150126223311.2e94d3cd.freebsd@edvax.de> In-Reply-To: <355611034.aCCaRRifNT@thinkpad> References: <3kWFlD70VnzRRrw@baobab.bilink.it> <20150126213658.48423c08.freebsd@edvax.de> <355611034.aCCaRRifNT@thinkpad>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 Jan 2015 00:16:35 +0300, Maxim Filimonov wrote: > On Monday 26 January 2015 21:36:58 Polytropon wrote: > > On Mon, 26 Jan 2015 16:45:16 +0100, Luciano Mannucci wrote: > > > I have a freebsd machine (FreeBSD troika 10.1-RELEASE FreeBSD 10.1-RELEASE > > > #0 r274401) with openvpn that works like a charm :-)... > > > I wish to nat one and only one of my openvpn clients, possibly for a > > > single destination. What's the better way to avoid disturbing the rest > > > of the operations? > > > Any clues? > > > Is IPFW my friend? > > > > Yes, that should work. In /etc/rc.conf, set > > > > natd_enable="YES" > > natd_interface="xl0" > > > > Why use natd, when ipfw can do kernel NAT? You're right, that's probably easier. Because I didn't have a configuration example at hand, I took one from an older system still relying on natd. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150126223311.2e94d3cd.freebsd>