[OpenWrt-Devel] I'd like to donate a Linksys WRT1900AC v1
Dear OpenWrt developers, I have a Linksys WRT1900AC v1 that is running OpenWrt 15.05, but every once in a while it randomly stops routing Internet traffic. This did not happen with the stock firmware, and unfortunately, I have not had the time to try to debug the problem. Are there any OpenWrt developers interested in working on this device? I would be happy to send any of you a WRT1900AC v1 if you will try it out and see if you can find and resolve the reliability problems. I will be checking the git commit logs to make sure that this device goes to an established OpenWrt developer and not just some random person on the mailing list who wants free hardware. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] I'd like to donate an Apple Airport Express A1264
Hello, I was recently given an Apple Airport Express A1264, still in the original box, and I would be happy to mail it to any OpenWrt developer who's interested in tinkering with it. Any takers? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate an Apple Airport Express A1264
2016-01-09 11:09 GMT-07:00 Boken Lin : > Hi Alex, I'm interested. Is it still available? Yes, it's still available. Send me a private email with your mailing address and I will ship it off. Thanks for helping with OpenWrt! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Firewall settings must be manually changed for 6to4
Hello, I recently set up an OpenWrt 18.06.1 router at a place where the ISP does not provide native IPv6, but does provide their own 6to4 tunnelling server. I installed 6to4 and ip-full on the router and configured WAN6, but was puzzled as to why IPv6 wasn't working until I discovered that the default firewall settings block forwarded traffic. Changing "Forward" from "reject" to "accept" under "General Settings" resolved the problem. Would you please consider automatically enabling forwarded traffic when 6to4 is installed, or at least update the wiki [1] to include this crucial piece of information? -Alex [1] https://openwrt.org/docs/guide-user/network/ipv6/barrier.breaker.ipv6.6to4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Firewall settings must be manually changed for 6to4
On Sun, Dec 30, 2018 at 4:40 AM Jo-Philipp Wich wrote: > > Hi, > > > I recently set up an OpenWrt 18.06.1 router at a place where the ISP > > does not provide native IPv6, but does provide their own 6to4 > > tunnelling server. I installed 6to4 and ip-full on the router and > > configured WAN6, but was puzzled as to why IPv6 wasn't working until I > > discovered that the default firewall settings block forwarded traffic. > > Changing "Forward" from "reject" to "accept" under "General Settings" > > resolved the problem. > > This is a huge security issue, you should not do that, ever. > You likely need both an ingress rule allowing protocol 41 traffic and > join the wan6 interface to the existing wan zone. I didn't see an option in LuCI to allow protocol 41 traffic. How do I set that up? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [luci] Improve spelling and grammar
Signed-off-by: Alex Henrie
---
applications/luci-ahcp/luasrc/model/cbi/ahcp.lua | 2 +-
.../luci-firewall/luasrc/model/cbi/firewall/zone-details.lua | 2 +-
.../luci-meshwizard/luasrc/model/cbi/freifunk/meshwizard.lua | 2 +-
applications/luci-watchcat/luasrc/model/cbi/watchcat/watchcat.lua | 8
applications/luci-wol/luasrc/model/cbi/wol.lua| 2 +-
applications/luci-wshaper/luasrc/model/cbi/wshaper.lua| 2 +-
modules/admin-full/luasrc/controller/admin/system.lua | 2 +-
modules/admin-full/luasrc/model/cbi/admin_network/dhcp.lua| 2 +-
modules/admin-full/luasrc/model/cbi/admin_network/ifaces.lua | 2 +-
modules/admin-full/luasrc/model/cbi/admin_network/wifi.lua| 2 +-
modules/admin-full/luasrc/model/cbi/admin_network/wifi_add.lua| 2 +-
modules/admin-full/luasrc/model/cbi/admin_system/system.lua | 2 +-
modules/admin-full/luasrc/view/admin_network/wifi_overview.htm| 2 +-
modules/admin-full/luasrc/view/admin_system/flashops.htm | 2 +-
modules/admin-full/luasrc/view/admin_system/upgrade.htm | 2 +-
modules/admin-mini/luasrc/view/mini/upgrade.htm | 4 ++--
modules/failsafe/luasrc/controller/failsafe/failsafe.lua | 2 +-
modules/failsafe/luasrc/view/failsafe/flashops.htm| 2 +-
modules/failsafe/luasrc/view/failsafe/upgrade.htm | 2 +-
19 files changed, 23 insertions(+), 23 deletions(-)
diff --git a/applications/luci-ahcp/luasrc/model/cbi/ahcp.lua
b/applications/luci-ahcp/luasrc/model/cbi/ahcp.lua
index 18764a1..a48f8b4 100644
--- a/applications/luci-ahcp/luasrc/model/cbi/ahcp.lua
+++ b/applications/luci-ahcp/luasrc/model/cbi/ahcp.lua
@@ -14,7 +14,7 @@ $Id: init.lua 5764 2010-03-08 19:05:34Z jow $
m = Map("ahcpd", translate("AHCP Server"), translate("AHCP is an
autoconfiguration protocol " ..
"for IPv6 and dual-stack IPv6/IPv4 networks designed to be used in
place of router " ..
- "discovery and DHCP on networks where it is difficult or impossible to
configure a " ..
+ "discovery or DHCP on networks where it is difficult or impossible to
configure a " ..
"server within every link-layer broadcast domain, for example mobile
ad-hoc networks."))
diff --git
a/applications/luci-firewall/luasrc/model/cbi/firewall/zone-details.lua
b/applications/luci-firewall/luasrc/model/cbi/firewall/zone-details.lua
index a3b1a6e..e5bcb34 100644
--- a/applications/luci-firewall/luasrc/model/cbi/firewall/zone-details.lua
+++ b/applications/luci-firewall/luasrc/model/cbi/firewall/zone-details.lua
@@ -50,7 +50,7 @@ s = m:section(NamedSection, zone.sid, "zone",
forward option describes the policy for forwarded
traffic \
between different networks within the zone. \
Covered networks specifies which available networks
are \
- member of this zone.", zone:name()))
+ members of this zone.", zone:name()))
s.anonymous = true
s.addremove = false
diff --git
a/applications/luci-meshwizard/luasrc/model/cbi/freifunk/meshwizard.lua
b/applications/luci-meshwizard/luasrc/model/cbi/freifunk/meshwizard.lua
index 8cb0822..68f7a5a 100644
--- a/applications/luci-meshwizard/luasrc/model/cbi/freifunk/meshwizard.lua
+++ b/applications/luci-meshwizard/luasrc/model/cbi/freifunk/meshwizard.lua
@@ -22,7 +22,7 @@ n.anonymous = true
function cbi_configure(device)
local configure = n:taboption(device, Flag, device .. "_config",
translate("Configure this interface"),
- translate("Note: this will setup this interface for mesh
operation, i.e. add to zone 'freifunk' and enable olsr."))
+ translate("Note: this will set up this interface for mesh
operation, i.e. add it to zone 'freifunk' and enable olsr."))
end
function cbi_ip4addr(device)
diff --git a/applications/luci-watchcat/luasrc/model/cbi/watchcat/watchcat.lua
b/applications/luci-watchcat/luasrc/model/cbi/watchcat/watchcat.lua
index 9f47bca..bcaf438 100644
--- a/applications/luci-watchcat/luasrc/model/cbi/watchcat/watchcat.lua
+++ b/applications/luci-watchcat/luasrc/model/cbi/watchcat/watchcat.lua
@@ -14,8 +14,8 @@ $Id$
m = Map("system",
translate("Watchcat"),
- translate("Watchcat allows to configure a periodic reboot and/or when "
..
- "internet connection has been lost for a certain period of
time."
+ translate("Watchcat allows configuring a periodic reboot when the " ..
+ "Internet connection has been lost for a certain period of
time."
))
s = m:section(TypedSection, "watchcat")
@@ -30,8 +30,8 @@ mode:value("allwa
Re: [OpenWrt-Devel] [OT] Anyone interested in donating Broadcom development?
2014-07-27 15:07 GMT-06:00 Rafał Miłecki : > Anyone interested in helping a bit? I've PayPal account (registered > with this e-mail) or I can link items I need to order + shipping > address if you prefer. What specific items are you looking for? (Send me some model numbers.) -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OT] Anyone interested in donating Broadcom development?
2014-07-28 0:57 GMT-06:00 Rafał Miłecki : > 1) Standalone adapters are available as "Dual 12 PCIE-AM". I found > them on agreetao and mallaid (don't have any experience with them): > http://www.agreetao.com/item/20865240537 > http://www.mallaid.com/index.php/item/20865240537 > Cost at Mallaid $28 + shipping ($10 or $24) Would this work? http://www.amazon.de/dp/B004LB714M How many do you need? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OT] Anyone interested in donating Broadcom development?
2014-07-28 1:45 GMT-06:00 Rafał Miłecki : > No, this is a standard adapter PCIe <-> mini PCIe adatpter. > > BCM94331CD and BCM94360CD both use proprietary Apple connector. It > uses 6 + 12 pins instead of 8 + 18. I see. I'm not very interested in sponsoring development that only directly benefits Mac users. However, if you send me your shipping address, I would be willing to give you an Asus PCE-AC56 instead: http://www.amazon.com/dp/B00JNA337K -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OT] Anyone interested in donating Broadcom development?
2014-07-28 2:12 GMT-06:00 Rafał Miłecki : > The reason I need few different cards is to spot places in code that > need to check for the hardware version. So having Apple hardware which > is usually a bit different helps here. > > Also: working with BCM94331CD is the best way of improving general > BCM4331 support. All standalone BCM4331 cards use Apple proprietary > connector. You can't buy a BCM4331 that will simply fit into PCIe or > mini PCIe. I've heard once about UPWL6031C, but it's not possible to > find it anywhere. > So to improve support for BCM4331s (that are used in many routers), I > *have to* buy Apple BCM4331 card and an adapter. Or the whole Mac :P > > Anyway, having Asus PCE-AC56 would be great for AC-PHY development, > I'll send you my address in a minute, thanks! :) Thanks for the explanation. Still, I'd rather send you the Asus PCE-AC56. I'll forward the order confirmation to you shortly. 2014-07-27 23:59 GMT-06:00 John Crispin : > if it makes you feel better i can add the official bit, you have done > a pile of great work recently :) > > we would like to officially ask those who think that > Rafał's work on brcm is important to help him out by donating the > named/requested materials to him ... and as usual his work is on a best > effort basis So does the donation of this hardware count as a tax-deductible contribution through Software in the Public Interest? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [luci] Improve spelling and grammar
Thank you! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
Hi, I have an extra Netgear N150 WNR1000 v3 (FCC ID: PY309300117, IC: 4054A-09300117). WikiDevi says that it has 4 MiB of flash memory. Is anyone interested in working on OpenWrt support for this router? If so, I'll give it to you for free, just tell me where to mail it to. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
Is no one interested? Come on, I'm offering free hardware to play with ;-) -Alex 2014-11-01 18:55 GMT-06:00 Alex Henrie : > Hi, > > I have an extra Netgear N150 WNR1000 v3 (FCC ID: PY309300117, IC: > 4054A-09300117). WikiDevi says that it has 4 MiB of flash memory. > > Is anyone interested in working on OpenWrt support for this router? If > so, I'll give it to you for free, just tell me where to mail it to. > > -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
2014-11-11 23:51 GMT-07:00 Rafał Miłecki : > On 11 November 2014 23:26, Alex Henrie wrote: >> Is no one interested? Come on, I'm offering free hardware to play with ;-) > > I already have about 10-20 Broadcom based boars in my drawer ;) Not > that excited with another one. > > However I'd be happy to help adding support for WNR1000 v3. Could you > attach serial console to it and test some patched OpenWrt builds? It sounds like a fun project, but SGT. Garcia volunteered to work on it, and I have already mailed the device to him. I'm sure SGT. Garcia will contact you for help once he receives the device. Thanks for your work on OpenWrt! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
2014-11-27 7:50 GMT-07:00 SGT. Garcia : > Michael and Alex are sending me USB<->COM cable and USB port[?] to get the > serial console going. I just sent you the following: http://www.amazon.ca/dp/B00AHYJWWG (USB/RS-232 converter with LEDs) http://www.amazon.ca/dp/B00MJUBKQ2 (cheap DB-9 cable to cut up and solder) There are obviously multiple ways to make this work, I'm just sending you the hardware that I would use if I did it myself. Happy Thanksgiving! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
2014-11-27 23:55 GMT-07:00 Rafał Miłecki : > On 28 November 2014 at 04:39, Alex Henrie wrote: >> 2014-11-27 7:50 GMT-07:00 SGT. Garcia : >>> Michael and Alex are sending me USB<->COM cable and USB port[?] to get the >>> serial console going. >> >> I just sent you the following: >> >> http://www.amazon.ca/dp/B00AHYJWWG (USB/RS-232 converter with LEDs) >> http://www.amazon.ca/dp/B00MJUBKQ2 (cheap DB-9 cable to cut up and solder) >> >> There are obviously multiple ways to make this work, I'm just sending >> you the hardware that I would use if I did it myself. > > You are not going to use RS-232 serial console with your router... > right? Or are you trying to fry it on purpose? After I ordered it, I started wondering about the voltage levels...thanks for pointing out my mistake. I've canceled the order. Michael: At this point I think it would be best if you just sent SGT one of your cheap & simple converters as you suggested. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] I'd like to donate a Linksys WRT300N V1
Hi, I have a spare Linksys WRT300N V1, and according to the wiki, OpenWrt does not yet fully support it: http://wiki.openwrt.org/toh/linksys/wrt300n1 http://wiki.openwrt.org/toh/linksys/wrt300n I would be happy to mail this router to anyone who is willing to work on support for it. Thanks for your hard work! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Linksys WRT300N V1
2015-03-13 0:50 GMT-06:00 Rafał Miłecki : > I work on both Broadcom targets, brcm47xx and bcm53xx: > http://git.openwrt.org/?p=openwrt.git&a=search&h=HEAD&st=author&s=rmilecki > (History goes back to September only, previously Hauke was accepting my > patches) > > I'm actually quite missing some SSB based router, would be nice to > have one. So far I didn't ever test OpenWrt on one of these older > devices. > > If the shipping cost will be sane for you, I'd be happy to get this device. The shipping cost shouldn't be terrible, but I won't be able to mail it until Monday. Thanks for all your OpenWrt work! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Linksys WRT300N V1
2015-03-13 1:08 GMT-06:00 Alex Henrie : > 2015-03-13 0:50 GMT-06:00 Rafał Miłecki : >> I work on both Broadcom targets, brcm47xx and bcm53xx: >> http://git.openwrt.org/?p=openwrt.git&a=search&h=HEAD&st=author&s=rmilecki >> (History goes back to September only, previously Hauke was accepting my >> patches) >> >> I'm actually quite missing some SSB based router, would be nice to >> have one. So far I didn't ever test OpenWrt on one of these older >> devices. >> >> If the shipping cost will be sane for you, I'd be happy to get this device. > > The shipping cost shouldn't be terrible, but I won't be able to mail > it until Monday. Thanks for all your OpenWrt work! I just mailed the router. When it arrives, please send confirmation to me and to treasu...@spi-inc.org. After that, when OpenWrt support for this router is complete, please update the wiki in both places: http://wiki.openwrt.org/toh/linksys/wrt300n1 http://wiki.openwrt.org/toh/linksys/wrt300n Thanks again! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Linksys WRT300N V1
2015-03-30 16:24 GMT-06:00 Josh Berkus : > On 03/30/2015 02:43 PM, Rafał Miłecki wrote: >> On 17 March 2015 at 22:05, Alex Henrie wrote: >>> I just mailed the router. When it arrives, please send confirmation to >>> me and to treasu...@spi-inc.org. >> >> I just got it today, thanks! > > OK. Is another Thank You letter required? If so, I will write one. Yes, I would like a thank you letter. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Linksys WRT300N V1
2015-03-30 15:43 GMT-06:00 Rafał Miłecki : > On 17 March 2015 at 22:05, Alex Henrie wrote: >> I just mailed the router. When it arrives, please send confirmation to >> me and to treasu...@spi-inc.org. > > I just got it today, thanks! > > I disassembled it, it's really a PCMCIA wireless card, nice :) Quite > an unique device! > > I had some problems installing OpenWrt, not sure what they were caused > by. Ppl trying to install original firmware seemed to had these issues > too, so they may be not related to OpenWrt firmware only. I got it as > well for the original firmware, however after a reboot is suddenly > succeeded. > So I decided to install some older OpenWrt as I suspected it may be > related to flash size. 12.09 was rejected, so I tried 10.03.1. It got > accepted but I think it doesn't boot and I've soft bricked this > router. > > I'll have to install serial console (requires soldering a header) and > doing more tests, so it may take me a bit more of time. > > Anyway, I'm happy to have this device for experiments, thanks! You're welcome! Let me know if you need a serial header, they only cost about $1 and I should have mailed one to you with the router but I wasn't thinking. Anyway, keep trying, I'm sure you will get it working. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Linksys WRT300N V1
2015-04-04 17:01 GMT-06:00 Rafał Miłecki : > I got serial working, unfortunately I discovered many problems with > wireless card support. > 1) ssb believes there isn't cardbus > 2) ssb can't detect PCI is working in hostmode > 3) forcing hostmode causes reboots during PCI init > 4) fixing PCI init causes crash during first MMIO access > > That means a lot of problems, pretty hard to track & understand & fix. > This simply wouldn't be possible to handle this device without having > a physical access to it. It shares some bugs with WRT350N v1 which > unresolved for more than 2 years: > https://dev.openwrt.org/ticket/12682#comment:11 > > So far I only sent generic support for detecting WRT300N v1.0: > http://patchwork.linux-mips.org/patch/9656/ > I'll try to get some PCI patches after this long weekend. Would it help you to have a WRT350N v1 to experiment with too? I'm pretty happy to donate arbitrary hardware to OpenWrt developers. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Linksys WRT300N V1
2015-04-08 0:01 GMT-06:00 Rafał Miłecki : > WRT300N v1.0 is supported now. I did it even before CC release, hooray :) > > For few minutes of testing I got a nice 20-22 Mb/s transfer using b43 > driver (it doesn't support 802.11n features, so 802.11g speeds are > available only). Wow, that was fast. Thanks! Make sure to get back to the linux-mips guys though, as they might have ideas on how to improve this code further. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Installing OpenWrt 21.02 on the TP-Link AD7200
Hello everyone, OpenWrt 21.02 adds support for the TP-Link AD7200,[1][2] but in practice I have not been able to install it. When I try uploading any of the three images (uImage, factory, sysupgrade) through the web interface, it just says "Firmware file error." I also tried setting my computer's IP address to 192.168.0.66, making the image available over TFTP with the name AD7200_1.0_tp_recovery.bin, and booting up the router with the reset button held down. I had Wireshark open and watched the file being transferred, but when the transfer was complete, the router just rebooted into its stock firmware again. So, what is the correct procedure for installing OpenWrt on the AD7200? -Alex [1] https://git.openwrt.org/?p=openwrt%2Fopenwrt.git&a=search&h=HEAD&st=commit&s=ad7200 [2] https://downloads.openwrt.org/releases/21.02-SNAPSHOT/targets/ipq806x/generic/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Installing OpenWrt 21.02 on the TP-Link AD7200
On Tue, Apr 20, 2021 at 4:04 AM Stijn Segers wrote: > > Alex Henrie schreef op 20 april 2021 07:28:32 CEST: > > > >So, what is the correct procedure for installing OpenWrt on the AD7200? > > Try downgrading to an older firmware. If that does not work then you'll need > to hook up serial to see the messages the flashing process spits out. > > Chances are OEM firmware checks for a software version now e.g., which is > unset at this point (see tplink-safeloader.c code). Thanks for the suggestion. The firmware upload fails with the same error if I try to upload an older version of the stock firmware. The latest version of the stock firmware (which is the version that is on the router I have) is 2.0.1. I next tried setting .soft_ver to "soft_ver:2.0.1\n" and "soft_ver:2.0.1 Build 20170103 rel.71053\n" in the AD7200 section in tplink-safeloader.c, but neither worked. Attaching a serial cable is a good idea, but it will be a week or two before I can get that done. Do you have any other suggestions? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Installing OpenWrt 21.02 on the TP-Link AD7200
On Tue, Apr 20, 2021 at 11:35 PM Alex Henrie wrote: > > On Tue, Apr 20, 2021 at 4:04 AM Stijn Segers wrote: > > > > Alex Henrie schreef op 20 april 2021 07:28:32 CEST: > > > > > >So, what is the correct procedure for installing OpenWrt on the AD7200? > > > > Try downgrading to an older firmware. If that does not work then you'll > > need to hook up serial to see the messages the flashing process spits out. > > > > Chances are OEM firmware checks for a software version now e.g., which is > > unset at this point (see tplink-safeloader.c code). > > Thanks for the suggestion. The firmware upload fails with the same > error if I try to upload an older version of the stock firmware. The > latest version of the stock firmware (which is the version that is on > the router I have) is 2.0.1. I haven't gotten a serial cable hooked up yet, but I tried with another AD7200 router that is running stock firmware version 1.0.10 and was not able to upload OpenWrt to it either. Its web interface gives the error "Invalid file type." When started with the reset button held down, it looks for a file named ArcherC2600_1.0_tp_recovery.bin on TFTP, but again, the file transfers and then the device simply reboots back into its stock firmware. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Installing OpenWrt 21.02 on the TP-Link AD7200
On Fri, Apr 30, 2021 at 2:28 PM Sven Roederer wrote: > > not sure if you tried or if it even still applies to TPLink WebIf. But back in > the days there was a link in the length of the firmware filename to be > uploaded. The message was teh same "invalid firmware type". > Probably renaming the file is worth a try ... I tried renaming the file to AD7200v1-up-ver2-0-1-P1[20170103-rel71053]_2017-01-04_10.08.28.bin to match the latest stock firmware and the web interface still didn't accept it. I now have a header soldered to the four pins labeled JP4 but so far I have not been able to get serial communication. Do you happen to remember what the pinout is? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Installing OpenWrt 21.02 on the TP-Link AD7200
On Sat, May 1, 2021 at 1:17 PM Alex Henrie wrote: > > On Fri, Apr 30, 2021 at 2:28 PM Sven Roederer wrote: > > > > not sure if you tried or if it even still applies to TPLink WebIf. But back > > in > > the days there was a link in the length of the firmware filename to be > > uploaded. The message was teh same "invalid firmware type". > > Probably renaming the file is worth a try ... > > I tried renaming the file to > AD7200v1-up-ver2-0-1-P1[20170103-rel71053]_2017-01-04_10.08.28.bin to > match the latest stock firmware and the web interface still didn't > accept it. > > I now have a header soldered to the four pins labeled JP4 but so far I > have not been able to get serial communication. Do you happen to > remember what the pinout is? I got it working with help from a friend :-) The serial pinout on the AD7200 is the same as on the C2600. I have attached the complete serial output while attempting to upload OpenWrt over TFTP, but the relevant part is: Using eth1 device TFTP from server 192.168.0.66; our IP address is 192.168.0.1 Filename 'ArcherC2600_1.0_tp_recovery.bin'. Load address: 0x4200 Loading: *# # # ###o# # # ## done Bytes transferred = 6818238 (6809be hex) FirmwareRecovery: image downloaded SF: Detected MX25U25635F with page size 4 KiB, total 32 MiB FirmwareRecovery: image size :6809BE FirmwareRecovery: fw-type:"" FirmwareRecovery: md5 checked ok FirmwareRecovery: update partition got FirmwareRecovery: this image do not match the hardware,now restart FirmwareRecovery: recovery failed }FirmwareRecovery: now restart resetting ... There might be a little corruption in the output because I used a logic analyzer to decode it instead of a real UART. What should I try next? -Alex FirmwareRecovery: Now doing recovery FirmwareRecovery: trying to connect 192.168.0.66 ... Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Mac1 unit failed Mac2 unit failed Ma
Re: Installing OpenWrt 21.02 on the TP-Link AD7200
On Sun, May 2, 2021 at 6:21 AM Petr Štetiar wrote:
>
> flash OpenWrt factory image using TP-Link's web UI and provide log of serial
> console
> during that process.
Here it is, but I'm afraid that nothing informative appears on the
serial port when uploading OpenWrt firmware through the web interface:
upgrade firmware...
true
-Alex
HH2002.07 SSdandard IPP806X.DN,r8!28@ay 05 d`16 - 09:!5:14)
smem bam ptabl f/und: ver: 0 len: 5
DAM 49! MiB
~CI0 Lin+ Ijtialhjed
{oPCI1 LInk Intializd
PCI2 Link Inti!lized
SF: Detdcted
X25U25&35F vith page size 4 KiB, total 32 MiB
9 ipq_nand: unknown NAND devhe manufacturer: 0 device: 0
hpq_nand failed to identIfy ddvice
SF: DeteCted MX25U25&35F with paGe size 4 CiB, tota, 32 hB
ipq_spi: p!gesIze: 0x!00, sector_size: 0x1000, size: 8200
32 MiB
MMC:
~~{RB-bad CRC, using d%faqlt environment
In:serial
Out: serial
Err: serial
Net: *
addr:0*3:7f:ba:db:1
{7_regOh.it: complate
%57_lXn_confif ...don%
4J Done
MAC2 addr20:3tnf:ba:db:2
et(0( h1
bont i@d@sdconds
~o~~{{~oo~o~~~?KI Now doing boktipq
MMC Device 0 not found
MMC Device 0 not found
Loading from nand1, oFfs%t 0x1f
Image Name: Linup-3.4.103
Image Type: ARM Linux KerneH mage (qncompresse`)
Data Shze: 1868608 Bytes = 1.8 MiB
Load Address: 1508000
Entry Point: 41508000
~~}o~o~~{~{~~oo~~~Automatic boot of image at addr
084400 ...
Image Name: Linux-3.4.103
Image Type: ARM LInux Kernel Image (uncomppesse$)
Data Size:1868608 Bytes = 1.8 MiB
Load Address: 41508000
EntryPoint: 41508000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
info: "mtdparts" not Set
UsiNg machid 0x1260 from environment
Starting kernel ...
~~{{~~~o{{+rBooting Linux o. physica CPU 0
[ 0.00] Linux versimn 3.4.103
(tristan-xiao@tristanxiao-To-Be-filled-by-O-E-M) (gc version 4.6.3 20100201
(prerdlease)(Linaro GCC 0.6 2012.02) ) #! SMP PEEMT Tue Mar 8 17:57:36 CST
2016
[0.00] CPU: ARMv' Prgcessor [512f04d0U revision 0 (ARMT7), cr=10c5387d
[0.00] CPU: PIPT / FIPT nonaliasing dAta cabhe, PIPT instruction cache
[0.00] Machine: Qualcomm Atheros @P148 reference board
[0.00] mm_reserve_memory: 0x440, 0x60
[ *0`] msm_reservememor: x4460, 0h20
[0.00] memory po/l 3 (start 5fc0 si:e@40) initialized
[0.`0] Memory policy: ECC disabled,Data cache writeallc
[.00] smem_find(137, 80)2 wrong size 72
[0.00] socinfoinit: v6, id=202, ver=0.0, raw_id=2064, raw_fer=2064,
hw_plat=0, hw_plat_ver=6%536
@@ 0.00U accessoRy_chip=0 hw_plad_subtype=0
[0.00] PERCPU: Embeded 8 pages/cpu @c0c48000 s10240 r8192 d14336 u32768
[0.0] Built 1 zonedicts in Zone order, mobility grouping on. Total
pager: 121642
[ 0.0] Kevnal command line: cMnsole=ttyHSL1,115200n8 root=mtd:rootfs
rootfspype=squashfs
[0.00]PID hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Dentry cache hash table entries: 64536 (order: 6, 262144 "ytes)
[0.00] Inoe-cache hash table entries: 30768 (order: 5, 131072 bytes)
[0.00] Memory: 43MB 436MB = 479MB total
[0.00] Memory: 477424k/489712k vailable, 13072k reserved, 0K higmem
[0.00] Virtual kernel memory layout8
[0.0] vector : 0X - 0x1000 ( 4 kB)
[.00] fxmap : 0xfff0 -0xfffe ( 894 kB)
[0.00] vmalloc : 0xdf0 - 0xff0` ( 512 MB)
[0.00] lowmem : 0xc00 - 0xdeb0 ( 491 MB)
[0.000 00] `km!p : 0xbfd0 - 0xc000 ( 2 MB)
[0.00 000]MOdules : 0xbf00 - 0xbfe0 ( 14 MB)
[0.00] .t%xt : 0xc0008000 - 0xc0513000 (5164 +B)
K@ 0.00] .init : 0xc060 - 0x0702800 (1034 kB)
[0.00] .data : 0xc0704000 - 0xa07a0898 ( 627 kB)
S0.00].bss : 0xc07a08bc - 0xc0844ae0 ( 657 kB)
[0.0` SLUB: Gensla"s=11, HWaHign=64, Oder=0-3, MinObjects=0, CPUs=2,
Nodes=1
[0.0 ] Preempti`le hierarchical RCU implementation.
[0.00] NR_IRQS:189
[0.00] sched_cdo#k: 32 bits at 32kHz, resolution 31240ns, wraps every
134175798ms
[0.0] Console: colour dummy device 80x30
[0.150421] Ca,hbrating d%lay using timer specific routine..!2.55 BogoMIPS
(lpj=42797)
[0.150452]pid_max default: 3268 minmum: 701
[0.150921] Mount[cache hash t`ble entries: 512
[0.152421] CPU: Testing write buffer coherEncy: ok
[ 0.152608] CPU0: thread -bX cpu 0, socket 0, mpidr 8000
[0.15263] Settng up static i$entity map &o2 0x41(9b080 - 0x4189b110
[0.154920 CPU!: Bnoted secondary pRocessor
[01550!4] CPU1: thread -1, cpu 1, socket 0, mpidr 8000`001
[0.1%j107] BroUght up 2 CPUs
[0.b55007 SMP:otal nf 2 procesors activat%$ (25.01@ogoMIP).
[ @ 0.b71602] dum-y:
[ @ 0.172289] NE* Registered@rotocol family 16
[0.173039] AXI: msm_bus_fabric_init_driver(): msM_bus_fabricOinit_dr
Re: Installing OpenWrt 21.02 on the TP-Link AD7200
Eureka! I changed "product_name:Talon AD7200" to "product_name:AD7200" in tplink-safeloader.c and then the router accepted the OpenWrt firmware! So it seems that we just need to split the AD7200 target into a "Talon" target and a regular target :-) -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Installing OpenWrt 21.02 on the TP-Link AD7200
On Sun, May 2, 2021 at 3:10 PM Adrian Schmutzler wrote: > > now where you say it, I remember: > > http://lists.openwrt.org/pipermail/openwrt-devel/2021-January/033149.html > > IIRC correctly this device was merged in a generally poorly reviewed state ... Hmm, it looks like there is in fact no separate "Talon AD7200" model. So it must be that the product_name field in OpenWrt is just wrong. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] ipq806x: fix product_name of TP-Link AD7200
The stock firmware does not accept firmware with "Talon" in the name.
Signed-off-by: Alex Henrie
---
tools/firmware-utils/src/tplink-safeloader.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/firmware-utils/src/tplink-safeloader.c
b/tools/firmware-utils/src/tplink-safeloader.c
index b3d5c9151d..8a47e6a58f 100644
--- a/tools/firmware-utils/src/tplink-safeloader.c
+++ b/tools/firmware-utils/src/tplink-safeloader.c
@@ -676,7 +676,7 @@ static struct device_info boards[] = {
.vendor = "",
.support_list =
"SupportList:\r\n"
- "{product_name:Talon
AD7200,product_ver:1.0.0,special_id:}\r\n",
+
"{product_name:AD7200,product_ver:1.0.0,special_id:}\r\n",
.part_trail = 0x00,
.soft_ver = NULL,
--
2.31.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH opkg] libopkg: pkg_hash: print unresolved dependencies
On Sun, May 2, 2021 at 5:16 PM Daniel Golle wrote:
>
> On Sun, May 02, 2021 at 10:59:12PM +0200, Hauke Mehrtens wrote:
> >
> > libopkg/pkg_hash.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/libopkg/pkg_hash.c b/libopkg/pkg_hash.c
> > index a07a25e..6c04ab2 100644
> > --- a/libopkg/pkg_hash.c
> > +++ b/libopkg/pkg_hash.c
> > @@ -263,8 +263,10 @@ pkg_hash_check_unresolved(pkg_t *maybe)
> > if (unresolved) {
> > res = 1;
> > tmp = unresolved;
> > - while (*tmp)
> > + while (*tmp) {
> > + opkg_msg(ERROR, "can not find dependency %s for
> > %s\n", *tmp, maybe->name);
> ^
> Should be 'cannot', it's spelled as one word in English (natives:
> correct me if I'm wrong!)
"Cannot", "can not", and "can't" are all correct.
-Alex
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v2] tplink-safeloader: fix product_name of TP-Link AD7200
The stock firmware does not accept firmware with "Talon" in the name.
Fixes: 1a775a4fd033 ("ipq806x: add support for TP-Link Talon AD7200")
Signed-off-by: Alex Henrie
---
tools/firmware-utils/src/tplink-safeloader.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/firmware-utils/src/tplink-safeloader.c
b/tools/firmware-utils/src/tplink-safeloader.c
index b3d5c9151d..8a47e6a58f 100644
--- a/tools/firmware-utils/src/tplink-safeloader.c
+++ b/tools/firmware-utils/src/tplink-safeloader.c
@@ -676,7 +676,7 @@ static struct device_info boards[] = {
.vendor = "",
.support_list =
"SupportList:\r\n"
- "{product_name:Talon
AD7200,product_ver:1.0.0,special_id:}\r\n",
+
"{product_name:AD7200,product_ver:1.0.0,special_id:}\r\n",
.part_trail = 0x00,
.soft_ver = NULL,
--
2.31.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH v2] tplink-safeloader: fix product_name of TP-Link AD7200
Tested on firmware version 1.0.10 Build 20160902 rel. 57400 which came preinstalled, as well as latest firmware version 2.0.1 Build 20170103 rel.71053 flashed from AD7200v1-up-ver2-0-1-P1[20170103-rel71053]_2017-01-04_10.08.28.bin. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
TP-Link AD7200: WAN port is swapped with last LAN port
Hello again, On OpenWrt 21.02-rc2 (and probably earlier), the WAN port is treated as a LAN port and LAN port 4 is treated as the WAN port on the TP-Link AD7200. (Actually, all the ports show up in LuCI in reverse order from their labels on the case.) How can I fix that? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: TP-Link AD7200: WAN port is swapped with last LAN port
On Mon, May 31, 2021 at 11:58 PM Alex Henrie wrote: > > On OpenWrt 21.02-rc2 (and probably earlier), the WAN port is treated > as a LAN port and LAN port 4 is treated as the WAN port on the TP-Link > AD7200. (Actually, all the ports show up in LuCI in reverse order from > their labels on the case.) How can I fix that? I was able to get correct behavior by editing /etc/board.d/02_network. I'll send a patch shortly. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] ipq806x: fix LAN and WAN port assignments on TP-Link AD7200
LAN port 4 was swapped with the WAN port and the remaining three LAN
ports were numbered in reverse order from their labels on the case.
Fixes: 1a775a4fd033 ("ipq806x: add support for TP-Link Talon AD7200")
Signed-off-by: Alex Henrie
---
target/linux/ipq806x/base-files/etc/board.d/02_network | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/target/linux/ipq806x/base-files/etc/board.d/02_network
b/target/linux/ipq806x/base-files/etc/board.d/02_network
index abdab89857..f0a852ece8 100644
--- a/target/linux/ipq806x/base-files/etc/board.d/02_network
+++ b/target/linux/ipq806x/base-files/etc/board.d/02_network
@@ -56,7 +56,6 @@ nec,wg2600hp3)
"2:lan" "3:lan" "4:lan" "5:lan" "0@eth1" "1:wan" "6@eth0"
;;
netgear,r7800 |\
-tplink,ad7200 |\
tplink,c2600)
ucidef_add_switch "switch0" \
"1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "6@eth1" "5:wan"
"0@eth0"
@@ -71,6 +70,10 @@ qcom,ipq8064-db149)
ucidef_add_switch "switch0" \
"1:lan" "2:lan" "3:lan" "4:lan" "6u@eth1" "5:wan" "0u@eth0"
;;
+tplink,ad7200)
+ ucidef_add_switch "switch0" \
+ "2:lan" "3:lan" "4:lan" "5:lan" "6@eth1" "1:wan" "0@eth0"
+ ;;
ubnt,unifi-ac-hd)
ucidef_set_interface_lan "eth0 eth1"
;;
--
2.31.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v2] ipq806x: fix LAN and WAN port assignments on TP-Link AD7200
LAN port 4 was swapped with the WAN port and the remaining three LAN
ports were numbered in reverse order from their labels on the case.
Fixes: 1a775a4fd033 ("ipq806x: add support for TP-Link Talon AD7200")
Signed-off-by: Alex Henrie
---
v2: Explicitly assign desired port numbers.
---
target/linux/ipq806x/base-files/etc/board.d/02_network | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/target/linux/ipq806x/base-files/etc/board.d/02_network
b/target/linux/ipq806x/base-files/etc/board.d/02_network
index abdab89857..3ed3db94fc 100644
--- a/target/linux/ipq806x/base-files/etc/board.d/02_network
+++ b/target/linux/ipq806x/base-files/etc/board.d/02_network
@@ -56,7 +56,6 @@ nec,wg2600hp3)
"2:lan" "3:lan" "4:lan" "5:lan" "0@eth1" "1:wan" "6@eth0"
;;
netgear,r7800 |\
-tplink,ad7200 |\
tplink,c2600)
ucidef_add_switch "switch0" \
"1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "6@eth1" "5:wan"
"0@eth0"
@@ -71,6 +70,10 @@ qcom,ipq8064-db149)
ucidef_add_switch "switch0" \
"1:lan" "2:lan" "3:lan" "4:lan" "6u@eth1" "5:wan" "0u@eth0"
;;
+tplink,ad7200)
+ ucidef_add_switch "switch0" \
+ "2:lan:1" "3:lan:2" "4:lan:3" "5:lan:4" "6@eth1" "1:wan"
"0@eth0"
+ ;;
ubnt,unifi-ac-hd)
ucidef_set_interface_lan "eth0 eth1"
;;
--
2.31.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH luci] luci-mod-network: wireless.js: allow changing the 60 GHz radio's frequency
The text "Operating frequency" was still on the form, but there was no
drop-down next to it. Also, it was only possible to edit the 60 GHz
radio's settings once: After that, instead of a settings dialog, an
error dialog would appear that said "TypeError: chan.options[0] is
undefined".
"mhz >= 58329" appears to have been a typo. The TP-Link AD7200 reports a
channel at 58320 MHz, exactly where the 802.11 specification says it
should be.
Signed-off-by: Alex Henrie
---
.../luci-static/resources/view/network/wireless.js| 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git
a/modules/luci-mod-network/htdocs/luci-static/resources/view/network/wireless.js
b/modules/luci-mod-network/htdocs/luci-static/resources/view/network/wireless.js
index 5115a69eb6..35d76d965b 100644
---
a/modules/luci-mod-network/htdocs/luci-static/resources/view/network/wireless.js
+++
b/modules/luci-mod-network/htdocs/luci-static/resources/view/network/wireless.js
@@ -327,7 +327,7 @@ var CBIWifiFrequencyValue = form.Value.extend({
band = '5g';
else if (data[1][i].mhz >= 5925 &&
data[1][i].mhz <= 7125)
band = '6g';
- else if (data[1][i].mhz >= 58329 &&
data[1][i].mhz <= 69120)
+ else if (data[1][i].mhz >= 58320 &&
data[1][i].mhz <= 69120)
band = '60g';
else
continue;
@@ -375,7 +375,8 @@ var CBIWifiFrequencyValue = form.Value.extend({
this.bands = {
'': [
'2g', '2.4 GHz',
this.channels['2g'].length > 3,
- '5g', '5 GHz',
this.channels['5g'].length > 3
+ '5g', '5 GHz',
this.channels['5g'].length > 3,
+ '60g', '60 GHz',
this.channels['60g'].length > 3
],
'n': [
'2g', '2.4 GHz',
this.channels['2g'].length > 3,
@@ -465,7 +466,9 @@ var CBIWifiFrequencyValue = form.Value.extend({
if (hwval != null) {
this.useBandOption = false;
- if (/a/.test(hwval))
+ if (hwval == '11ad')
+ band.value = '60g';
+ else if (/a/.test(hwval))
band.value = '5g';
else
band.value = '2g';
@@ -554,7 +557,7 @@ var CBIWifiFrequencyValue = form.Value.extend({
if (this.useBandOption)
uci.set('wireless', section_id, 'band', value[1]);
else
- uci.set('wireless', section_id, 'hwmode', (value[1] ==
'2g') ? '11g' : '11a');
+ uci.set('wireless', section_id, 'hwmode', (value[1] ==
'2g') ? '11g' : (value[1] == '60g') ? '11ad' : '11a');
uci.set('wireless', section_id, 'channel', value[2]);
}
--
2.32.0.94.ge083fb24f6
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH luci] luci-mod-network: wireless.js: allow changing the 60 GHz radio's frequency
On Fri, Jul 9, 2021 at 1:50 PM Jo-Philipp Wich wrote: > > Hi Alex, > > thank you for this patch. Based on your submission I pushed a somewhat > smaller fix to LuCI master which omits the last two hunks: > https://github.com/openwrt/luci/commit/e5626ece12236f6be9dbb6da6eb90fcbb469a1f0 > > The code related to the `hwmode` option is there for backwards > compatibility reasons and should only deal with 11a and 11g. > > OpenWrt master uses the new `option band` to specify wireless frequency > bands and that should be handled correctly already without the > additional changes. Thanks Jo, your commit fixed part of the problem, but the last two hunks are still needed to fix the JavaScript error. If you'd like, I can give you a TP-Link AD7200 to play around with so that you can see what's going on for yourself. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02 status
On Sat, Jul 17, 2021 at 9:48 AM Hauke Mehrtens wrote: > > In addition there are multiple problems with specific device, if they > get fixed it would be nice otherwise we just leave it like it is now. Configuration of 60 GHz radios via LuCI is still broken (my proposed patch [1] was not accepted in its entirety [2][3]). I would love to donate a TP-Link AD7200 to anyone willing to work on the problem. -Alex [1] http://lists.openwrt.org/pipermail/openwrt-devel/2021-July/035810.html [2] http://lists.openwrt.org/pipermail/openwrt-devel/2021-July/035811.html [3] http://lists.openwrt.org/pipermail/openwrt-devel/2021-July/035815.html ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Zyxel NBG6716 support
Hello, I have a Zyxel NBG6716 that was running OpenWrt 19.07, but when I upgraded it to OpenWrt 21.02 it stopped booting. The serial console, the bootloader, and the bootloader's TFTP command still work though. I found a note in the Git logs that says that the OpenWrt kernel is now too big for this device.[1] Is anyone interested in trying to restore OpenWrt support for the NBG6716? In the end I just bought a different router, so I'd be happy to send you the borked one if you want to work on it. -Alex [1] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=5d8ea6d34f9f23d4dfff4ffcac8c9599d842c3a8 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] ath79: add Zyxel EMG2926-Q10A
The Zyxel EMG2926-Q10A is 99% the Zyxel NBG6716, but the bootloader
expects a different product name when flashing over TFTP. Also, the
EMG2926-Q10A always has 128 MiB of NAND flash whereas the NBG6716
reportedly can have either 128 MiB or 256 MiB.
Signed-off-by: Alex Henrie
---
See https://github.com/openwrt/openwrt/pull/4536
---
.../etc/hotplug.d/ieee80211/00-wifi-migration | 1 +
.../ath79/dts/qca9558_zyxel_emg2926_q10a.dts | 8 ++
target/linux/ath79/image/nand.mk | 26 +++
.../nand/base-files/etc/board.d/02_network| 1 +
.../etc/hotplug.d/firmware/11-ath10k-caldata | 1 +
.../etc/hotplug.d/ieee80211/10-fix-wifi-mac | 1 +
.../base-files/lib/preinit/10_fix_eth_mac.sh | 1 +
7 files changed, 39 insertions(+)
create mode 100644 target/linux/ath79/dts/qca9558_zyxel_emg2926_q10a.dts
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/00-wifi-migration
b/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/00-wifi-migration
index d2df0533fe..35e7c4452c 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/00-wifi-migration
+++ b/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/00-wifi-migration
@@ -16,6 +16,7 @@ migrate_wifi_path() {
case "$board" in
tplink,archer-c7-v1|\
tplink,archer-c7-v2|\
+ zyxel,emg2926-q10a|\
zyxel,nbg6716)
path="pci:00/:00:00.0"
WIFI_PATH_CHANGED=1
diff --git a/target/linux/ath79/dts/qca9558_zyxel_emg2926_q10a.dts
b/target/linux/ath79/dts/qca9558_zyxel_emg2926_q10a.dts
new file mode 100644
index 00..c00109a5b4
--- /dev/null
+++ b/target/linux/ath79/dts/qca9558_zyxel_emg2926_q10a.dts
@@ -0,0 +1,8 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+
+#include "qca9558_zyxel_nbg6716.dts"
+
+/ {
+ compatible = "zyxel,emg2926-q10a", "zyxel,nbg6716", "qca,qca9558";
+ model = "ZyXEL EMG2926-Q10A";
+};
diff --git a/target/linux/ath79/image/nand.mk b/target/linux/ath79/image/nand.mk
index d31aba1abc..27a63fdf7e 100644
--- a/target/linux/ath79/image/nand.mk
+++ b/target/linux/ath79/image/nand.mk
@@ -289,6 +289,32 @@ define Device/netgear_wndr4500-v3
endef
TARGET_DEVICES += netgear_wndr4500-v3
+define Device/zyxel_emg2926_q10a
+ SOC := qca9558
+ DEVICE_VENDOR := ZyXEL
+ DEVICE_MODEL := EMG2926-Q10A
+ DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k-ct \
+ ath10k-firmware-qca988x-ct
+ RAS_BOARD := AAVK-EMG2926Q10A
+ RAS_ROOTFS_SIZE := 29696k
+ RAS_VERSION := "OpenWrt Linux-$(LINUX_VERSION)"
+ KERNEL_SIZE := 4096k
+ BLOCKSIZE := 128k
+ PAGESIZE := 2048
+ LOADER_TYPE := bin
+ KERNEL := kernel-bin | append-dtb | lzma | loader-kernel | uImage none | \
+ zyxel-buildkerneljffs | check-size 4096k
+ IMAGES := sysupgrade.tar sysupgrade-4M-Kernel.bin factory.bin
+ IMAGE/sysupgrade.tar/squashfs := append-rootfs | pad-to (BLOCKSIZE) | \
+ sysupgrade-tar rootfs=@ | append-metadata
+ IMAGE/sysupgrade-4M-Kernel.bin/squashfs := append-kernel | \
+ pad-to (KERNEL_SIZE) | append-ubi | pad-to 263192576 | gzip
+ IMAGE/factory.bin := append-kernel | pad-to (KERNEL_SIZE) | append-ubi |
\
+ zyxel-factory
+ UBINIZE_OPTS := -E 5
+endef
+TARGET_DEVICES += zyxel_emg2926_q10a
+
define Device/zyxel_nbg6716
SOC := qca9558
DEVICE_VENDOR := ZyXEL
diff --git a/target/linux/ath79/nand/base-files/etc/board.d/02_network
b/target/linux/ath79/nand/base-files/etc/board.d/02_network
index 76cdab18f8..98aa27f5f2 100644
--- a/target/linux/ath79/nand/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/nand/base-files/etc/board.d/02_network
@@ -42,6 +42,7 @@ ath79_setup_interfaces()
ucidef_add_switch "switch0" \
"0@eth0" "1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1"
;;
+ zyxel,emg2926-q10a|\
zyxel,nbg6716)
ucidef_add_switch "switch0" \
"0@eth0" "1:lan" "2:lan" "3:lan" "4:lan" "5:wan"
"6@eth1"
diff --git
a/target/linux/ath79/nand/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
b/target/linux/ath79/nand/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 03e225ddde..b9a51c6588 100644
---
a/target/linux/ath79/nand/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++
b/target/linux/ath79/nand/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -26,6 +26,7 @@ case "$FIRMWARE" in
netgear,r6100)
caldata_extract "caldata" 0x5000 0x844
;;
+ zyxel,emg2926-q10a|\
zyxel,nbg6716)
Re: [PATCH] ath79: add Zyxel EMG2926-Q10A
On Sat, Feb 19, 2022 at 12:01 PM Petr Štetiar wrote: > > Alex Henrie [2022-01-20 22:06:07]: > > Hi, > > it looks like you need just this two variables: > > DEVICE_MODEL := EMG2926-Q10A > RAS_BOARD := AAVK-EMG2926Q10A > > so following copy&pasta seems a bit much against my DRY taste: > > > +define Device/zyxel_emg2926_q10a > > + SOC := qca9558 > > + DEVICE_VENDOR := ZyXEL > > + DEVICE_MODEL := EMG2926-Q10A > > + DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k-ct \ > > + ath10k-firmware-qca988x-ct > > + RAS_BOARD := AAVK-EMG2926Q10A > > + RAS_ROOTFS_SIZE := 29696k > > + RAS_VERSION := "OpenWrt Linux-$(LINUX_VERSION)" > > + KERNEL_SIZE := 4096k > > + BLOCKSIZE := 128k > > + PAGESIZE := 2048 > > + LOADER_TYPE := bin > > + KERNEL := kernel-bin | append-dtb | lzma | loader-kernel | uImage none | > > \ > > + zyxel-buildkerneljffs | check-size 4096k > > + IMAGES := sysupgrade.tar sysupgrade-4M-Kernel.bin factory.bin > > + IMAGE/sysupgrade.tar/squashfs := append-rootfs | pad-to (BLOCKSIZE) > > | \ > > + sysupgrade-tar rootfs=@ | append-metadata > > + IMAGE/sysupgrade-4M-Kernel.bin/squashfs := append-kernel | \ > > + pad-to (KERNEL_SIZE) | append-ubi | pad-to 263192576 | gzip > > + IMAGE/factory.bin := append-kernel | pad-to (KERNEL_SIZE) | > > append-ubi | \ > > + zyxel-factory > > + UBINIZE_OPTS := -E 5 > > +endef > > +TARGET_DEVICES += zyxel_emg2926_q10a > > so I would simply abstract the common bits into something like this: > > define Device/zyxel_nand_common > SOC := qca9558 > DEVICE_VENDOR := ZyXEL > DEVICE_MODEL := EMG2926-Q10A > DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k-ct \ > ath10k-firmware-qca988x-ct > ... > end > > and then do: > > define Device/zyxel_nbg6716 >$(Device/zyxel_nand_common) >DEVICE_MODEL := NBG6716 >RAS_BOARD := NBG6716 > endef > > define Device/zyxel_emg2926_q10a >$(Device/zyxel_nand_common) >DEVICE_MODEL := EMG2926-Q10A >RAS_BOARD := AAVK-EMG2926Q10A > endef Thanks for showing me! I didn't know that I could do that. How about we make Device/zyxel_emg2926_q10a inherit from Device/zyxel_nbg6716, similar to how qca9558_zyxel_emg2926_q10a.dts inherits from qca9558_zyxel_nbg6716.dts? I'll send a v2 shortly. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v2] ath79: add Zyxel EMG2926-Q10A
The Zyxel EMG2926-Q10A is 99% the Zyxel NBG6716, but the bootloader
expects a different product name when flashing over TFTP. Also, the
EMG2926-Q10A always has 128 MiB of NAND flash whereas the NBG6716
reportedly can have either 128 MiB or 256 MiB.
Signed-off-by: Alex Henrie
---
v2: Avoid duplication in nand.mk
---
.../base-files/etc/hotplug.d/ieee80211/00-wifi-migration | 1 +
target/linux/ath79/dts/qca9558_zyxel_emg2926_q10a.dts | 8
target/linux/ath79/image/nand.mk | 7 +++
target/linux/ath79/nand/base-files/etc/board.d/02_network | 1 +
.../base-files/etc/hotplug.d/firmware/11-ath10k-caldata | 1 +
.../base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac| 1 +
.../ath79/nand/base-files/lib/preinit/10_fix_eth_mac.sh | 1 +
7 files changed, 20 insertions(+)
create mode 100644 target/linux/ath79/dts/qca9558_zyxel_emg2926_q10a.dts
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/00-wifi-migration
b/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/00-wifi-migration
index d2df0533fe..35e7c4452c 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/00-wifi-migration
+++ b/target/linux/ath79/base-files/etc/hotplug.d/ieee80211/00-wifi-migration
@@ -16,6 +16,7 @@ migrate_wifi_path() {
case "$board" in
tplink,archer-c7-v1|\
tplink,archer-c7-v2|\
+ zyxel,emg2926-q10a|\
zyxel,nbg6716)
path="pci:00/:00:00.0"
WIFI_PATH_CHANGED=1
diff --git a/target/linux/ath79/dts/qca9558_zyxel_emg2926_q10a.dts
b/target/linux/ath79/dts/qca9558_zyxel_emg2926_q10a.dts
new file mode 100644
index 00..c00109a5b4
--- /dev/null
+++ b/target/linux/ath79/dts/qca9558_zyxel_emg2926_q10a.dts
@@ -0,0 +1,8 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+
+#include "qca9558_zyxel_nbg6716.dts"
+
+/ {
+ compatible = "zyxel,emg2926-q10a", "zyxel,nbg6716", "qca,qca9558";
+ model = "ZyXEL EMG2926-Q10A";
+};
diff --git a/target/linux/ath79/image/nand.mk b/target/linux/ath79/image/nand.mk
index 2d7892db94..9f209368e4 100644
--- a/target/linux/ath79/image/nand.mk
+++ b/target/linux/ath79/image/nand.mk
@@ -344,3 +344,10 @@ define Device/zyxel_nbg6716
UBINIZE_OPTS := -E 5
endef
TARGET_DEVICES += zyxel_nbg6716
+
+define Device/zyxel_emg2926_q10a
+ $(Device/zyxel_nbg6716)
+ DEVICE_MODEL := EMG2926-Q10A
+ RAS_BOARD := AAVK-EMG2926Q10A
+endef
+TARGET_DEVICES += zyxel_emg2926_q10a
diff --git a/target/linux/ath79/nand/base-files/etc/board.d/02_network
b/target/linux/ath79/nand/base-files/etc/board.d/02_network
index e26a5e4ddf..2c6e676ae9 100644
--- a/target/linux/ath79/nand/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/nand/base-files/etc/board.d/02_network
@@ -49,6 +49,7 @@ ath79_setup_interfaces()
ucidef_add_switch "switch0" \
"0@eth0" "1:lan:4" "2:lan:3" "3:lan:2" "5:lan:1"
;;
+ zyxel,emg2926-q10a|\
zyxel,nbg6716)
ucidef_add_switch "switch0" \
"0@eth0" "1:lan" "2:lan" "3:lan" "4:lan" "5:wan"
"6@eth1"
diff --git
a/target/linux/ath79/nand/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
b/target/linux/ath79/nand/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index d47e296853..e5c26d6bb5 100644
---
a/target/linux/ath79/nand/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++
b/target/linux/ath79/nand/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -21,6 +21,7 @@ case "$FIRMWARE" in
netgear,r6100)
caldata_extract "caldata" 0x5000 0x844
;;
+ zyxel,emg2926-q10a|\
zyxel,nbg6716)
caldata_extract "art" 0x5000 0x844
ath10k_patch_mac $(macaddr_add $(mtd_get_mac_ascii u-boot-env
ethaddr) 1)
diff --git
a/target/linux/ath79/nand/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
b/target/linux/ath79/nand/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
index 730a5f9943..20974248c1 100644
--- a/target/linux/ath79/nand/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
+++ b/target/linux/ath79/nand/base-files/etc/hotplug.d/ieee80211/10-fix-wifi-mac
@@ -15,6 +15,7 @@ case $board in
[ "$PHYNBR" -eq 0 ] && \
macaddr_add $(mtd_get_mac_binary art 0x0) 2 >
/sys${DEVPATH}/macaddress
;;
+ zyxel,emg2926-q10a|\
zyxel,nbg6716)
# Set mac address for 2.4g device
[ "$PHYNBR" -eq 1 ] && \
diff --git a/target/linux/
I'd like to donate a GL-AXT1800
Dear OpenWrt developers, I was recently given a GL-AXT1800 router for free. The stock firmware is a fork of OpenWrt 21.02, but there is no official build of OpenWrt available. I will gladly donate this hardware to anyone willing to work on supporting it. Just tell me where in the world to send the box to :-) -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Developer Meeting November 2022
"some pull requests are adding hardware but nobody has the hardware and the skills to build an image" I don't really have time to help review pull requests, but I'd be happy to find and donate hardware to the people who are reviewing them. Is there any particular device that would be helpful right now? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Developer Meeting November 2022
On Mon, Dec 5, 2022 at 1:07 AM Enrico Mioso wrote: > > If i am asked directly, I am happy to buy the hardware and help testing, > putting apart required time and resources. > Still, as you may know by now, I am blind person so if soldering is required, > I can't help in short time. I can do the soldering, so I can save you the trouble and send you devices with a debug header preattached. Just let me know. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] 12.09.1 build error: rt2x00lib.ko is missing
When I try to compile OpenWRT, I get the following error: mkdir -p /home/alex/workspace/openwrt/bin/ar71xx/packages /home/alex/workspace/openwrt/build_dir/linux-ar71xx_generic/compat-wireless-2013-06-27/ipkg-ar71xx/kmod-rt2x00-lib/CONTROL /home/alex/workspace/openwrt/staging_dir/target-mips_r2_uClibc-0.9.33.2/pkginfo ERROR: module '/home/alex/workspace/openwrt/build_dir/linux-ar71xx_generic/compat-wireless-2013-06-27/drivers/net/wireless/rt2x00/rt2x00lib.ko' is missing. make[3]: *** [/home/alex/workspace/openwrt/bin/ar71xx/packages/kmod-rt2x00-lib_3.3.8+2013-06-27-1_ar71xx.ipk] Error 1 make[3]: Leaving directory `/home/alex/workspace/openwrt/package/mac80211' make[2]: *** [package/mac80211/compile] Error 2 make[2]: Leaving directory `/home/alex/workspace/openwrt' make[1]: *** [/home/alex/workspace/openwrt/staging_dir/target-mips_r2_uClibc-0.9.33.2/stamp/.package_compile] Error 2 make[1]: Leaving directory `/home/alex/workspace/openwrt' make: *** [world] Error 2 I am running Lubuntu 13.10 x64 and building r38863 for the Buffalo WZR-HP-AG300H. I followed the instructions at https://dev.openwrt.org/wiki/GetSource and http://wiki.openwrt.org/doc/howto/easy.build To be honest, all I really want is IPv6 support. Will there be an official 12.09.1 binary that I can use soon? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] 12.09.1 build error: rt2x00lib.ko is missing
2013/11/30 Jacek Kikiewicz : > If you really don't care about compiling newest version just try some > older revision... Do you know when an official 12.09.1 binary will be available? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] I'd like to donate an Asus RT-N56U
Hi, I have an Asus RT-N56U and I am disappointed that OpenWrt does not currently support it. If you feel it would be helpful to the OpenWrt project, I'd be happy to give you a free Asus RT-N56U. Just tell me where to mail it to. -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] How do I improve LuCI's Catalan translations?
I've tried submitting "suggested translations" to http://i18n.luci.subsignal.org/pootle/ca/ but they are never approved. In fact, that page says that there has been no activity on the Catalan LuCI translation since 2012. Many other open source projects have accepted Catalan translations from me. Could I take over as the maintainer of LuCI's Catalan translation? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How do I improve LuCI's Catalan translations?
2014-05-28 11:52 GMT-06:00 Jo-Philipp Wich : > Hi Alex, > > please try again. The permissions on the catalan language group have > been misconfigured. > > Regards, > Jow I can submit translations now, but the "Accept suggestion" and "Reject suggestion" buttons don't work. When I try to use them, the Firebug console says "NetworkError: 403 FORBIDDEN - http://luci.subsignal.org/pootle/ca/luci/base.po/review/5/";. I'm attaching the body of the response, which includes the more specific error message "CSRF verification failed. Request aborted." Could you please look into this? After googling "pootle 403 forbidden", I think the Pootle server just needs to be updated to be compatible with Django: http://sourceforge.net/p/translate/mailman/message/27412066/ Thanks, -Alex Title: 403 Forbidden Forbidden (403) CSRF verification failed. Request aborted. More information is available with DEBUG=True. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How do I improve LuCI's Catalan translations?
2014-05-31 6:33 GMT-06:00 Jo-Philipp Wich : > I applied a fix for that - should work now. Updating Pootle is not > feasable at this stage is it is customized quite a bit. It works now, thanks! -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] LuCI make po
Hi, I'm trying to make a patch to update LuCI's translation string files because I'm sure they're out of sync with the strings in the source code. But when I try to run `make po`, I get "/bin/sh: 2: build/i18n-lua2po.pl: not found". The commands I'm using are: sudo apt-get install liblua5.1.0-dev -y git clone git://git.openwrt.org/project/luci.git cd luci make What's going wrong? -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Changing to Diget
2014-06-03 20:44 GMT-06:00 Peter Fraser : > How do I change my subscription to digest mode? https://lists.openwrt.org/cgi-bin/mailman/options/openwrt-devel?email=pjfrase...@gmail.com -Alex ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] [luci] i18n: Fix `make po` missing file error
build/i18n-lua2po.pl was deleted in 2012 because it is obsolete. The
new script to update the PO and POT files is build/i18n-sync.sh.
Signed-off-by: Alex Henrie
---
Makefile | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/Makefile b/Makefile
index 362eed6..db53f9c 100644
--- a/Makefile
+++ b/Makefile
@@ -83,10 +83,7 @@ nixiodocs: hostenv
build/hostenv.sh $(realpath host) $(LUA_MODULEDIR) $(LUA_LIBRARYDIR)
"build/makedocs.sh libs/nixio/ nixiodocs"
po: host
- for L in $${LANGUAGE:-$$(find i18n/ -path 'i18n/*/luasrc/i18n/*' -name
'default.*.lua' | \
- sed -e 's!.*/default\.\(.*\)\.lua!\1!')}; do \
- build/i18n-lua2po.pl . $(realpath host)/po $$L; \
- done
+ build/i18n-sync.sh
run:
# make run is deprecated #
--
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
