Date: Thu, 01 Aug 2013 06:48:20 -0500 From: Mark Felder <feld@FreeBSD.org> To: freebsd-jail@freebsd.org Subject: Re: Starting jail breaks routing / multi-network jail Message-ID: <1375357700.9597.4374227.38E046B6@webmail.messagingengine.com> In-Reply-To: <CAHDrHStCng%2Bzg=_RThWysgRm5wD=DxxzJQz=%2BoZL8JwbX%2BXh7w@mail.gmail.com> References: <CAHDrHStCng%2Bzg=_RThWysgRm5wD=DxxzJQz=%2BoZL8JwbX%2BXh7w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 31, 2013, at 20:55, Josh Beard wrote: > > Starting a jail with a LAN and public address changes the host's routing > table and will not talk over the public network. Cycling the netif and > routing services resolves it. > I'm not aware of the routing issue you're describing. I had a need not too long ago for a 32bit system to get migrated to 64bit, but first we needed to run it in a 32bit jail while we formulated the plan. This server had several NICs on different networks which were all passed to the jail. Many were private, a couple were public. The routing itself worked fine; the problem was that raw sockets always picked the first interface of the jail. The most obvious breakage was ping. However, TCP and UDP worked fine to all networks. This was 9.0-RELEASE at the time. I do have a PR for my issue here: http://www.freebsd.org/cgi/query-pr.cgi?pr=168678 Are you sure you aren't just running into that? Although, I really doubt restarting routing would fix it, so you must be hitting another anomaly...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1375357700.9597.4374227.38E046B6>