Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-11 Thread Bastian Bittorf
* Daniel Dickinson dan...@powercloudsystems.com [11.03.2013 09:27]: you posted some screenshots of the original tplink-firmware for Israel: they made nearly everything wrong for the user. I'm afraid you've confused me with someone else. I posted no such thing. Also I looked at the forum

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-11 Thread Daniel Golle
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

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-11 Thread Bastian Bittorf
* Daniel Golle daniel.go...@gmail.com [11.03.2013 13:23]: 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

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-11 Thread Daniel Golle
On 03/11/2013 02:28 PM, Bastian Bittorf wrote: * Daniel Golle daniel.go...@gmail.com [11.03.2013 13:23]: 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

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-11 Thread Bastian Bittorf
* Daniel Golle daniel.go...@gmail.com [11.03.2013 14:14]: This won't work during firstboot, because /etc/config/wireless will be created by 'wifi detect' only after tplink_board_detect already run. but if wifi-detect runs, the wifi is off anyway so the setting is not needed: only during first

[OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Daniel Golle
Sorry, the previous mail contained the wrong patch (that's the problem with attachments -- you don't see their content while composing the mail...) From 062e4686778df46a94729195cc07ff4bfdc57fa2 Mon Sep 17 00:00:00 2001 From: Daniel Golle dgo...@allnet.de Date: Fri, 8 Mar 2013 03:42:56 +0200

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Bastian Bittorf
* Daniel Golle daniel.go...@gmail.com [10.03.2013 15:17]: ;; + 430080*) + iw reg set IL + model=TP-Link TL-WDR4300 (IL) + ;; dont do 'iw reg' magic here, the user should decide that in the common way (uci...) bye, bastian

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Daniel Golle
On 03/10/2013 04:18 PM, Bastian Bittorf wrote: * Daniel Golle daniel.go...@gmail.com [10.03.2013 15:17]: ;; +430080*) +iw reg set IL +model=TP-Link TL-WDR4300 (IL) +;; dont do 'iw reg' magic here, the user should decide that in the

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Bastian Bittorf
* Daniel Golle daniel.go...@gmail.com [10.03.2013 16:24]: However, the law over here says that it should not be up to the user to decide that. i understand your thoughts, but linux/openwrt is not responsible for fight with the law. otherwise we must e.g. built it without SSL for several

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Bastian Bittorf
* Daniel Golle daniel.go...@gmail.com [10.03.2013 16:24]: The idea of doing iw reg set IL when the board is detected was to simulate that behaviour and achieve the same result as if it was done properly in the EEPROM (i.e. the user can then only further limit herself) it will be resetted

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Daniel Golle
On 03/10/2013 05:37 PM, Bastian Bittorf wrote: * Daniel Golle daniel.go...@gmail.com [10.03.2013 16:24]: However, the law over here says that it should not be up to the user to decide that. i understand your thoughts, but linux/openwrt is not responsible for fight with the law. otherwise

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Daniel Golle
On 03/10/2013 05:42 PM, Bastian Bittorf wrote: * Daniel Golle daniel.go...@gmail.com [10.03.2013 16:24]: The idea of doing iw reg set IL when the board is detected was to simulate that behaviour and achieve the same result as if it was done properly in the EEPROM (i.e. the user can then

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Matthias Schiffer
On 03/10/2013 05:05 PM, Daniel Golle wrote: On 03/10/2013 05:37 PM, Bastian Bittorf wrote: * Daniel Golle daniel.go...@gmail.com [10.03.2013 16:24]: However, the law over here says that it should not be up to the user to decide that. i understand your thoughts, but linux/openwrt is not

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Daniel Golle
On 03/10/2013 06:56 PM, Matthias Schiffer wrote: On 03/10/2013 05:05 PM, Daniel Golle wrote: Simply speaking: If I buy a TP-LINK router in germany and flash it with OpenWrt, it will come with ETSI 0x68 regdomain (or similar) set in the art partition, which is marked read-only. OpenWrt

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Matthias Schiffer
On 03/10/2013 06:11 PM, Daniel Golle wrote: On 03/10/2013 06:56 PM, Matthias Schiffer wrote: By the way, this is not entirely correct... a lot of the TP-Link routers I've bought in Germany have the regdomain set to US in the art partitition (the stock firmware gives me a list with many

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Daniel Golle
On 03/10/2013 07:19 PM, Matthias Schiffer wrote: On 03/10/2013 06:11 PM, Daniel Golle wrote: On 03/10/2013 06:56 PM, Matthias Schiffer wrote: By the way, this is not entirely correct... a lot of the TP-Link routers I've bought in Germany have the regdomain set to US in the art partitition

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Stefan Lippers-Hollmann
Hi On Sunday 10 March 2013, Daniel Golle wrote: On 03/10/2013 05:37 PM, Bastian Bittorf wrote: * Daniel Golle daniel.go...@gmail.com [10.03.2013 16:24]: […] I'm not going to comment upon what's the correct approach in this case and certainly agree that the local regulatory requirements should

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-10 Thread Daniel Golle
On 03/10/2013 07:52 PM, Bastian Bittorf wrote: * Daniel Golle daniel.go...@gmail.com [10.03.2013 18:00]: The default settings of the binaries on downloads.openwrt.org do *not* allow me to do that. And that's what I'm talking about. thats not true. OpenWrt defaults to regdomain US

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Daniel Golle
Hi Stefan, thank you for that delighting summary of the situation! On 03/10/2013 08:04 PM, Stefan Lippers-Hollmann wrote: I'm not going to comment upon what's the correct approach in this case and certainly agree that the local regulatory requirements should be enforced by default. Simply

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-10 Thread Daniel Dickinson
On Sun, 10 Mar 2013 20:03:29 +0200 Daniel Golle daniel.go...@gmail.com wrote: On 03/10/2013 07:52 PM, Bastian Bittorf wrote: * Daniel Golle daniel.go...@gmail.com [10.03.2013 18:00]: The default settings of the binaries on downloads.openwrt.org do *not* allow me to do that. And that's what

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-10 Thread Daniel Dickinson
Also, of note is that there are efforts underway to change the way regulatory compliance is met, so that the law is satisfied (and e.g atheros' need to comply) while addressing international concerns, however these efforts will take time and you will need to be patient. I'd recommend if you want

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-10 Thread Bastian Bittorf
* Daniel Golle daniel.go...@gmail.com [10.03.2013 18:00]: maybe you can set it via uci (without commiting it), so it survives any wifi action _and_ can be overidden... technically that's not that easy, because tplink_board_detect is called before wifi detect during firstboot. Therefore

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL)

2013-03-10 Thread Bastian Bittorf
* Daniel Golle daniel.go...@gmail.com [10.03.2013 19:57]: So by default, this just *prevents* you from using channels you are legally allowed to use in your country. Using the binary from downloads.openwrt.org won't give you access to bands which are restricted by law, right? Not that this is

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-10 Thread Bastian Bittorf
* Daniel Golle daniel.go...@gmail.com [10.03.2013 19:57]: On 03/10/2013 07:52 PM, Bastian Bittorf wrote: thats not true. OpenWrt defaults to regdomain US (hardcoded in the builts, because the regdomain is choosen during compiletime). so NACK. no such a thing as a hardcoded country code.

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-10 Thread Bastian Bittorf
* Daniel Dickinson dan...@cshore.neomailbox.net [10.03.2013 19:57]: Actually, the default in the code is to use the EEPROM values if present, but if the EEPROM doesn't set a country code or to be clear: during compile-time, a description is loaded which values are allowed for each country:

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-10 Thread Daniel Golle
On 03/10/2013 09:28 PM, Bastian Bittorf wrote: you posted some screenshots of the original tplink-firmware for Israel: they made nearly everything wrong for the user. I don't think it's all wrong for the user. It's definitely not the right way to do it [tm], but it serves the purpose (getting

Re: [OpenWrt-Devel] [PATCH/RFC v2] add hardware id for TL-WDR4300v1 (IL) / regdomain issue

2013-03-10 Thread Daniel Dickinson
On Sun, 10 Mar 2013 20:28:13 +0100 Bastian Bittorf bitt...@bluebottle.com wrote: * Daniel Dickinson dan...@cshore.neomailbox.net [10.03.2013 19:57]: Actually, the default in the code is to use the EEPROM values if present, but if the EEPROM doesn't set a country code or to be clear: