Hi Bastian, On 03/11/2013 10:58 AM, Bastian Bittorf wrote: > sorry, for mixing things up. i understud Daniel Golle, that they > cannot use all allowed 5 GHz channels - they dont want to break the law. I didn't say that. Mentioning it again: There is no problem with the original firmware in that regard. It allows using exactly what is legal in Israel. It might be a conservative interpretation, but well, that's not a bad thing, it will keep users out of trouble and make it less likely that they accidentally interfere. My concern is, if we add the hardware id and generate images which can be loaded through the webui of these devices, we should make sure that radio regulation law is enforced *just as in* the original firmware. In a way, the real mistake the designers of the original firmware made was to make such a big fuzz about it and write there in big letters "you are limited because your government does not allow you to do X". Because this will just make everybody think that they are missing out on something, so they will believe that circumventing the regulatory enforcement will give them something / be advantageous (it is not!). Daniel Dickinson's analogy comparing this to traffic rules is nice. You don't want to drive around according to UK traffic rules (on the left side) in France (where everybody is driving on the right). It doesn't seem like an advantageous idea to me, at least (no matter how much of a freedom-loving individualist I might be).
> Lets sum things up: > most dev's dont want to support breaking the law, so better > keep the limits lower (maybe even lower than allowed). Ack. > so, thanks for discussing this and share your options, now > back to work 8-) : what is the best way to enforce ISRAEL in this > specific router? Great, after all, we are back to the practical level :) As an outcome of this discussion, I realized that what I believed to be a specific local problem (ie. no country code or 'US' default in the EEPROM) is a reality, probably in most places and for most manufacturers. For now, I guess the work-around I suggested does the trick (anyone got a better *practical* idea) -- it detects the hwid of the board and (ab)uses it as a regulatory hint. That's not very elegant, but until there is a better solution, this is better than not having it (assuming that people will manage to flash OpenWrt anyway -- it's not that difficult of a hack to do so) _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
