Coova DHCP and DD-Wrt Repeater Bridge configuration

[wlanmac]

Then, the issues isn't that chilli is handling DHCP wrongly. The real
issue is that your subscribers are NAT'ed (in layer 2) such that chilli
would not see the true MAC of the subscriber. This is fundamentally a
problem with chilli - even if DHCP was operating as you expected. 

I believe 'sweetspot' might be more what you are looking for. From what
I understand, it is like chilli only for layer 3. 


On Thu, 2009-03-26 at 23:18 +0100, Iacopo Spalletti wrote:
> Alle 17:23 di giovedì 26 marzo 2009, wlanmac ha scritto:
> > I haven't confirmed your statement that coova-chilli takes the ethernet
> > source over the client-mac (though probably true). But, isn't the point
> > of the bridge that the request's ethernet source is that of the
> > subscriber? If so, then what is the problem exactly?
> 
> While WDS bridge is completely transparent (i.e. ethernet frames across bridge 
> maintains original source mac-address), as far as i have read on dd-wrt docs 
> (http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge#Limitations and 
> http://www.dd-wrt.com/phpBB2/viewtopic.php?t=68) Client Bridge and Repeater 
> Bridge mode are not so transparent, so that every packet coming from the 
> Repeater/Client side has AP mac-address as source (as a result of 802.11 
> protocol specifications), and that's confusing coova which give the same IP 
> address to all  the clients associated to the repeater.
> Sniffing traffic with wireshark on the coova host shows dhcp request packet formed 
> as described earlier: i can provide it to you if you need it and i can help 
> with more tests
>