* cmsv c...@wirelesspt.net [09.03.2013 22:37]:
The Calculations on the Time of 63.9 Sec doing 4.00GBytes does not add up to
538MBit/s
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
Behalf Of Bastian Bittorf
Sent: Sunday, 10 March 2013 5:37 PM
To: c...@wirelesspt.net; OpenWrt Development List
Hi everyone!
The hardware-ID is different for TL-WDR4300v1 devices sold in Israel.
For unknown reasons, instead of having proper settings in the WiFi EEPROM, the
importer decided to have a rootfs-mod of TP-LINKs original firmware -- still
with US regdomain in the EEPROM, but limiting the choices
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
* 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
Felix Fietkau n...@openwrt.org [2013-03-09 01:37:38]:
Please find out which exact OpenWrt revision broke it, and I will help
sort out the details.
e3d7c9b6f5e62fdbec05fd5f2e1ef59aa4a14673 is the first bad commit
commit e3d7c9b6f5e62fdbec05fd5f2e1ef59aa4a14673
Author:
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
On 2013-03-10 3:20 PM, Petr Štetiar wrote:
Felix Fietkau n...@openwrt.org [2013-03-09 01:37:38]:
Please find out which exact OpenWrt revision broke it, and I will help
sort out the details.
e3d7c9b6f5e62fdbec05fd5f2e1ef59aa4a14673 is the first bad commit
commit
* 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
* 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
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
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
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
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
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
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
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
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
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
Do not overflow the input buffer. This happens on slow hosts that take
long time to recompute the data on start.
Signed-off-by: Paul Fertser fercer...@gmail.com
---
This is really important because without this patch the weather daemon
can't start at all after having collected some statistics
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
LAN1 and LAN2 LEDs not present (it pulled to ground via resistors) on
MR3040 and MR11U devices.
But this LEDs=GPIOs we canNOT control by default.
Сonfirmed: https://forum.openwrt.org/viewtopic.php?pid=193705#p193705
This little patch enabling ability to control GPIO14 and GPIO15:
Index:
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
* 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
* 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
* 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.
Index: target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v8.c
===
--- target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v8.c
(revision
35934)
+++ target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v8.c
* 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:
Felix Fietkau n...@openwrt.org [2013-03-10 15:37:41]:
Does reverting this change make things work for you in the latest revision?
Yes, I did reverted it in AA and it works fine:
89b3ea101c0a49194d637a119bccea6ae47ae2c3 Revert AA: ar71xx: fix GPIO
function selection for AR934x
Could this be back ported to AA?
Kind Regards
Hanno Schupp
On 11/03/2013, at 8:23 AM, Dmytro dioptimi...@gmail.com wrote:
Index: target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr841n-v8.c
===
---
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
Has the source address used for NAT reflection changed with firewall3?
At r35938, I’m seeing that when I attempt to connect from a host on my LAN
to a redirected port on my main router’s WAN address, the router reflects
the request back in to my LAN using its own WAN address as the source
This patch provides the chage utility for programs that require it.
Signed-off-by: Kyle Anderson k...@xkyle.com
shadow-chage.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
This patch provides preliminary support for Puppet, a configuration
management tool, for OpenWrt.
It does depend on this ticket being resolved:
https://dev.openwrt.org/ticket/9873
It also depends on previously submitted patches, shadow-chage and facter.
This is a first pass. Next I'll work to
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:
35 matches
Mail list logo
