Re: socket / bind - specific address

2006-02-25 Thread Edwin Groothuis
On Sat, Feb 25, 2006 at 02:28:46PM +, 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 wor

Re: socket / bind - specific address

2006-02-25 Thread Edwin Groothuis
On Sat, Feb 25, 2006 at 08:47:00AM -0500, Chuck Swiger wrote: > 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,

Re: socket / bind - specific address

2006-02-25 Thread Vince Hoffman
On Sat, 25 Feb 2006, 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 rout

Re: socket / bind - specific address

2006-02-25 Thread Brian Candler
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 o

Re: socket / bind - specific address

2006-02-25 Thread Chuck Swiger
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, t