On Thu, Apr 17, 2003 at 12:42:13PM +0200, Stefan Sonnenberg-Carstens wrote:
> And if you assign that IP to rtk1 you should be able to ping 192.168.0.3 ...
> Routing could help, but, the kernel must be able to determine the right
> interface to get to a special computer.
> A bridge normally is passive in the meaning of only repeating ethernet
> frames from on interface to the other.
> I think there is no easy solution to this point as what you like to do is
> not intended to be done by a bridge (
> which should normally be unvisible)
> .
> Sorry, can't help you.
> 
> ----- Original Message -----
> From: "Juha K Kallio" <bunnyh@psychedelic.baana.suomi.net>
> To: <netbsd-users@netbsd.org>
> Sent: Thursday, April 17, 2003 12:35 PM
> Subject: Re: IP on bridge interface?
> 
> 
> > On Thu, Apr 17, 2003 at 11:43:56AM +0200, Stefan Sonnenberg-Carstens
> wrote:
> > > You can assign a IP adress to one of the interfaces which are part of
> your
> > > bridge.
> > >
> > > ----- Original Message -----
> > > From: "Juha K Kallio" <bunnyh@psychedelic.baana.suomi.net>
> > > To: <netbsd-users@netbsd.org>
> > > Sent: Thursday, April 17, 2003 9:38 AM
> > > Subject: IP on bridge interface?
> > >
> > >
> > > > Why I cannot assign an IP-address for a bridge interface in NetBSD? I
> am
> > > trying to network three machines by installing two
> > > > NICs in one, and making it a bridge. This was possible with linux, but
> > > NetBSD doesn't seem to allow assigning an IP-address
> > > > for the bridge. Is there any other way to do this? Assigning an IP to
> one
> > > of the NICs obviously doesn't work, and I want to
> > > > have all the machines on the same network.
> > > >
> > > >
> > >
> > >
> >
> > I have tried that. bridge0 consists of rtk0 and rtk1. If I assign
> 192.168.0.1 to rtk0, I can only ping 192.168.0.2, which
> > is connected to rtk0. 192.168.0.3(rtk1) just timeouts. Do I have to set up
> some special routes?
> >
> >
> 
> 

I don't think it breaks the idea of bridge if it has an IP address. It still is passive, and forwards the frames to the 
destination ethernet address, which in this case would be one of the bridge's two NICs, or any other computer in the 
network. The interface bridge0 would have two ethernet addresses assigned. I am no expert in coding, but I don't see why 
the bridge driver doesn't include support this, like the linux version.