hi,
On Thu, Nov 09, 2006 at 01:44:26AM +0100, Markus Bergkvist wrote:
> First, I thought it was because fxp0 and ral0 on the host was on
> different sub-nets but now they are both on 192.168.0/24 and so is trunk0.
> So i added a bridge
> # ifconfig bridge0 create
> # brconfig bridge0 add fxp0 add ral0 up
> but that didn't help either.
>
the bridge is running on you're ap, isn't it? this is correct, but you
don't need to run a bridge on your trunk'ed client.
so you're right, you have to use the same subnet for this trick. and
there is the problem: the bridge on your ap will learn you're clients
lladdr on the wired interface and if you unplug the cable it will
suddenly appear on the wireless side. the openbsd bridge
implementation is currently not optimized for fast topology changes
(i'm not sure if RSTP support would help in this case), but you can
improve it a bit by changing the cache timeout:
# brconfig bridge0 timeout 10
in this example, the you're clients lladdr will be removed from the
cache after 10 seconds and can be re-learned on another interface. you
can even decrease or increase it, depending on the number of clients
in your wireless network (it's not a very good idea to force you're ap
bridge to re-learn the entries all the time, especially in large
networks).
it actually works ;)! some people on this list may have seen my
demonstration during one of my talks using an openbsd client (ath0 +
em0 trunk) and an openbsd ap (ral0/ath0 + fxp0 bridge)... playing an
uncached humppa* stream, unplug, few seconds silence, humppa
continues...
*) if you don't have any humppa, you can get the taste by buying the
cd-set and listening to the openbsd 4.0 release song
(http://www.openbsd.org/lyrics.html#40).
reyk
