Hmm, I had started to write a blog posting about how I ended up with a similar
situation, and using fib to solve it. Though we decided to go in a different
direction for production deployments of FreeBSD in our datacenter...of which
there aren't any yet.
I should see about finishing the postin
On 08/01/2013 20:39, Devin Teske wrote:
Maybe giving each of the jails their own networking stack would help?
Do you know about VIMAGE?
I have a boot script that makes it easy to test out this
new/experimental (yet very stable) feature:
http://druidbsd.sf.net/vimage.shtml
--
Devin
Thanks Dev
On Tue, Jan 08, 2013 at 12:39:44PM -0800, Devin Teske wrote:
> Maybe giving each of the jails their own networking stack would help?
>
> Do you know about VIMAGE?
>
> I have a boot script that makes it easy to test out this new/experimental
> (yet very stable) feature:
>
> http://druidbsd.sf.ne
Maybe giving each of the jails their own networking stack would help?
Do you know about VIMAGE?
I have a boot script that makes it easy to test out this new/experimental (yet
very stable) feature:
http://druidbsd.sf.net/vimage.shtml
--
Devin
On Jan 8, 2013, at 12:07 PM, Free BSD wrote:
> De
Dear List Members
I have a scenario where I have an unusual routing need. This is one
server with two (or more) interfaces. One of the interface is connected
to a public IP network, the other one is connected to the LAN. This box
is NOT a gateway machine, just a box serving on two sides of the
