Brian Candler wrote:
On Mon, Jul 24, 2006 at 01:40:13PM -0700, Julian Elischer wrote:
an ng_ip node :-)
I've considerred it.
Then all the tools like 'netstat' and 'route' need modifying to talk to a
netgraph socket, but in principle I don't see why it couldn't be done.
ISTM there are
Brett Glass wrote:
At 08:09 AM 7/24/2006, Marko Zec wrote:
Yes this should work with a virtualized stack - all the "outsied"
interfaces
in each jail / virtual stack could be simply bridged together using
netgraph
which is virtualization-agnostic, i.e. a global facility in the current
impleme
On Mon, Jul 24, 2006 at 09:17:37PM -0600, Brett Glass wrote:
> I've been noodling over this for two weeks now, and am thinking
> that the easiest thing to do might be is map every address in each
> "virtual" router to a unique address from FreeBSD's point of view
> (i.e. 192.168.0.2 on LAN 1 bec
On Tuesday 25 July 2006 05:17, Brett Glass wrote:
> At 08:09 AM 7/24/2006, Marko Zec wrote:
> >Yes this should work with a virtualized stack - all the "outsied"
> > interfaces in each jail / virtual stack could be simply bridged together
> > using netgraph which is virtualization-agnostic, i.e. a g
On Monday 24 July 2006 22:40, Julian Elischer wrote:
...
> >Also, what would really suit him is a netgraph IP interface node - i.e.
> >something which takes raw ethernet frames from the interface, performs IP
> >encapsulation/decapsulation and ARP - and an IP forwarding node with its
> > own forwar
On Mon, Jul 24, 2006 at 01:40:13PM -0700, Julian Elischer wrote:
> an ng_ip node :-)
> I've considerred it.
Then all the tools like 'netstat' and 'route' need modifying to talk to a
netgraph socket, but in principle I don't see why it couldn't be done.
ISTM there are a zillion userland-to-kernel
At 08:09 AM 7/24/2006, Marko Zec wrote:
Yes this should work with a virtualized stack - all the "outsied" interfaces
in each jail / virtual stack could be simply bridged together using netgraph
which is virtualization-agnostic, i.e. a global facility in the current
implementation of "vimage".
Brian Candler wrote:
On Mon, Jul 24, 2006 at 04:09:29PM +0200, Marko Zec wrote:
There's a project called 'vimage' which adds a separate virtual forwarding
table per jail. This might work for you, although all the natd's "outside"
interfaces would need to sit on the same interface, and I don'
On Mon, Jul 24, 2006 at 04:09:29PM +0200, Marko Zec wrote:
> > There's a project called 'vimage' which adds a separate virtual forwarding
> > table per jail. This might work for you, although all the natd's "outside"
> > interfaces would need to sit on the same interface, and I don't know if it
> >
On Monday 24 July 2006 11:09, Brian Candler wrote:
> On Fri, Jul 21, 2006 at 11:13:47AM -0600, Brett Glass wrote:
> > I have an application in which I'd like a FreeBSD router to have
> > multiple, isolated LANS attached to it, each with the same address
> > space. The FreeBSD box would take the pla
On Fri, Jul 21, 2006 at 11:13:47AM -0600, Brett Glass wrote:
> I have an application in which I'd like a FreeBSD router to have
> multiple, isolated LANS attached to it, each with the same address
> space. The FreeBSD box would take the place of multiple NAT routers.
>
> For example, I might wan
> I have an application in which I'd like a FreeBSD router to have
> multiple, isolated LANS attached to it, each with the same address
> space. The FreeBSD box would take the place of multiple NAT routers.
>
> For example, I might want to have three internal Ethernet
> interfaces on the FreeBS
Brett Glass wrote:
> I have an application in which I'd like a FreeBSD router to have
> multiple, isolated LANS attached to it, each with the same address
> space. The FreeBSD box would take the place of multiple NAT routers.
>
Normally i'd point and laugh, but your ... unusual ..., problem got m
Brett Glass wrote:
I have an application in which I'd like a FreeBSD router to have
multiple, isolated LANS attached to it, each with the same address
space. The FreeBSD box would take the place of multiple NAT routers.
For example, I might want to have three internal Ethernet interfaces
on
I have an application in which I'd like a FreeBSD router to have
multiple, isolated LANS attached to it, each with the same address
space. The FreeBSD box would take the place of multiple NAT routers.
For example, I might want to have three internal Ethernet
interfaces on the FreeBSD box. Each
15 matches
Mail list logo
