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
Hello everybody,
Suppose I have two addresses routed to my box over a
PPP interface. I have created on Host_2 a loopback interface
and assigned to it Inet_addr_2. Host_1 routes to Host_2
Inet_Addr_2 and everything works if something is coming
from internet to Inet_Addr_2. Host_2 has as default rou
Current FreeBSD problem reports
Critical problems
Serious problems
S Submitted Tracker Resp. Description
---
o [2006/01/30] kern/92552 net A serious bug in most network drivers fro
f [2006/02/12] kern
On Mon, Jul 24, 2006 at 12:38:56PM +0300, Nikos Vassiliadis wrote:
> Can I somehow use lo1 address
> for connections initiated from Host_2?
Options I know of:
(1) the application which originates the connection can explicitly bind
to the lo1 address (see for example telnet -s and ping -S options)
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 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
> >
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'
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".
