Hi,
After 6 months of long woking hours I'd phased out wrt using as os for my wp54 for wireless cpe. It failed miserably in every rook and corner reason not known but unforunately my hardwork gone wasted. Here is my experience.
After installing kamikaze on 7.09 it behaved strangely and the behaviour was same mac address on all the ap u flash with wrt. The mac address is  00:41:44:4D:51:20 whereas wrt provided by compex version 7.07 didn't had anyproblem with it. No one came for support even compex couldn't help it.
This took some weeks to know.
After changing the version or recompiling the grep changed its behaviour. Earlier it was discounting the hash bang line and with the change of version it started counting the hash bang.
I searched all the net but no documents found over the difference between bash and ash.
After all these hardwork I found no station bridging is supported by madwifi drivers as soon as u bridge the eth and ath the result is no pings but link is there. Not all ap support address 4 we tested on few and all failed.
In the forum someone told me to link with ath0 as ap and ath1 as wds. I tried with mikrotik it connected but the second part of the connection .. asking for wds now this vap of wds is running with a different mac address and its different from ap vap which result in deauth by mikrotik. I tried everything but mac address goes the same.
this is just the tip of iceberg. I'd already requested by arpnat patch in ebtables. I think everyone needs it.
regards
norms

seems that you forget to set madwifi parameter wds to 1. Do it like this:

iwpriv ath0 wds 1

This should be done both on AP and STA.

Edgars
openrb.com

(Last edited by edgars on 11 Aug 2008, 20:26)

this is only compatible with wrt based radios like wrt ubnt wili or maybe oswave. I tried everyting. There  must be some reason why there is arpnat patch developed. Just to do client bridging. Its been used by willibox, ubnt, dd.
thnx for ur response
regards
norms

(Last edited by normunds on 11 Aug 2008, 21:52)

i think this arpnat youre talking about is for ap+sta on broadcom, not wds. i tol you wds works for me between openwrt and mikrotik. set mikrotik as ap-bridge and enable wds dynamic and set bridge1. on openwrt you need two interfaces, ap and wds, wds has bssid of mikrotik, both have wds=1. works.

ya u r rt its for sta mode. I tried ur way i:e ath0 as ap and ath1 as wds but it all failed as ath0 and ath1 had different mac address so when ap connected to mtik. Mtik asks for wds and that wds is having different mac address than ath1 so it gives deauth.
regards
norms