Jan Johansson skrev:
kami petersen <[EMAIL PROTECTED]> wrote:
well, it should work. however, you should set an address on either of
the interfaces that constitutes the bridge, not the bridge itself.
but you don't say exactly where you are unsuccessful...
It works, I just thought there might be a cleaner solution.
For example both ral0 and fxp1 needs an IP address or dhcpd just
refuses to work on the interface.
on the router: assign 192.168.13.1 to fxp1 and none to ral0, put both
fxp1 and ral0 in the bridge, putting both ral0 and fxp1 in
dhcpd.interfaces. a similar solution is working here.
this is the basically the same as having only one interface with the
above ip on it, that is wired to a switch with an antenna and two
ethernet jacks.
also, failover trunk ought to work,
A failover trunk will work for one laptop. But if a friend and I
are sharing the wireless the friend will be cut off when the
wired interfaces goes active.
but i wouldn't know how a bridge pair directly hooked up
against let's say a round robin trunk would behave.
Don't understand this.
i'm talking about trunking on the clients. if using failover mode, only
one interface is used at a time, but in round robin mode all interfaces
are used 'simultaneously', with chances of confusing the bridge at the
router by creating a loop in the network topology. if this is the case
have a look at the spanning tree options of brconfig(8). however, i
haven't been there, so this is just where i'd start.
plus, i can't see the point of a trunk on the router.
/k
