On Tue, Nov 07, 2006 at 11:50:16PM +0100, Markus Bergkvist wrote: > Reyk Floeter wrote: > >the trunk will use the mac address of it's primary trunkport, which is > >fxp0 in your case. as soon as you add ral0 to the trunk it will also > >use the trunk mac address (00:02:a5:b8:71:b5 from fxp0) for ethernet > >and 802.11 traffic. this should trigger a new authentication and > >association to the accesspoint using the new mac address. > I noticed that at some point too. Good to know that is the correct > behaviour. > > > > >if you use anything like mac address filters on your ap, please > >whitelist fxp0's address and try it again. > > > Nope, no address filtering on the ap.
hmmm, interesting. can you monitor the auth/assoc state on the ap? for example, if your ap is an openbsd box, you can use ifconfig -M to list the client nodes and tcpdump -y ieee802_11_radio to monitor the wireless traffic. reyk
