Date: Sun, 26 Feb 2006 09:27:17 +1100 From: Edwin Groothuis <edwin@mavetju.org> To: Brian Candler <B.Candler@pobox.com> Cc: freebsd-net@freebsd.org Subject: Re: socket / bind - specific address Message-ID: <20060225222717.GC92618@k7.mavetju> In-Reply-To: <20060225142846.GA70376@uk.tiscali.com> References: <20060225070722.GA92618@k7.mavetju> <20060225142846.GA70376@uk.tiscali.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 25, 2006 at 02:28:46PM +0000, Brian Candler wrote: > On Sat, Feb 25, 2006 at 06:07:22PM +1100, Edwin Groothuis wrote: > > The situation is as follows: > > > > We have a couple of FreeBSD routers, with RFC1918 addresses on the > > ethernets and a public address on the loopback. This works fine for > > connecting to the routers, but is problematic for locally originated > > outgoing traffic (think NTP, think syslog): it takes the IP address > > of the outgoing interface, which is the RFC1918 address. > > > > Is there a way (sysctl, kernel option) to define which IP address > > is used for locally originated outgoing traffic? > > One way is to run your daemon (ntpd, syslogd etc) within a jail, and give > the jail your public loopback as its IP address. I'm surely going to try this and see if it works. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060225222717.GC92618>