Re: Flagship AX routers

2021-05-18 Thread John Crispin
On 19.05.21 00:09, Paul Spooren wrote: Hi, On 5/18/21 11:52 PM, Philip Prindeville wrote: Hi all, I noticed that there are several AX routers from TP-Link, Netgear, D-Link, etc. and some of them have even had OpenWRT ported to them. Which of these various platforms has the most

Re: opkg fails to install manually downloaded packages

2021-05-18 Thread Sven Roederer
Hauke, thanks for the pointer. My comments in the original thread. Sven Am Sonntag, 16. Mai 2021, 23:34:04 CEST schrieb Hauke Mehrtens: > > I debugged a similar problem a week ago and added this patch to opkg: > https://patchwork.ozlabs.org/project/openwrt/patch/20210502205912.23753-1-ha >

Re: [PATCH opkg] libopkg: pkg_hash: print unresolved dependencies

2021-05-18 Thread Sven Roederer
Hi, Am Montag, 3. Mai 2021, 19:46:22 CEST schrieb Hauke Mehrtens: > On 5/3/21 2:38 PM, Baptiste Jonglez wrote: > > Hi, > > > > On 02-05-21, Hauke Mehrtens wrote: > >> When a package is not installed because it has unresolved dependencies > >> > >> normally we get only an error message like

Re: Flagship AX routers

2021-05-18 Thread Paul Spooren
Hi, On 5/18/21 11:52 PM, Philip Prindeville wrote: Hi all, I noticed that there are several AX routers from TP-Link, Netgear, D-Link, etc. and some of them have even had OpenWRT ported to them. Which of these various platforms has the most CPU/RAM/FLASH? A few are discussed, but I'm not

Flagship AX routers

2021-05-18 Thread Philip Prindeville
Hi all, I noticed that there are several AX routers from TP-Link, Netgear, D-Link, etc. and some of them have even had OpenWRT ported to them. Which of these various platforms has the most CPU/RAM/FLASH? A few are discussed, but I'm not seeing consensus on "the best one currently is this..."

[PATCH] base-files: migrate old UCI network sections defining bridges

2021-05-18 Thread Rafał Miłecki
From: Rafał Miłecki Old "interface" sections for bridges were mixing layer 2 and layer 3. That syntax got deprecated and UCI section "device" is used for bridge configuration now. Backward compatibility may be dropped from netifd soon now so migrate old configs using uci-defaults script.

[PATCH v3 2/2] ramips: mt7621: Add support for ZyXEL LTE3301-Plus

2021-05-18 Thread André Valentin
The ZyXEL LTE3301-Plus is an 4G indoor CPE with 2 external LTE antennas. Specifications: - SoC: MediaTek MT7621AT - RAM: 256 MB - Flash: 128 MB MB NAND (MX30LF1G18AC) - WiFi: MediaTek MT7615E - Switch: 4 LAN ports (Gigabit) - LTE: Quectel EG506 connected by USB3 to SoC - SIM: 1 micro-SIM

[PATCH v3 1/2] firmware-utils: zytrx: Add support for ZyXEL LTE3301-Plus

2021-05-18 Thread André Valentin
This adds a new device id to the image tools. Signed-off-by: André Valentin --- tools/firmware-utils/src/zytrx.c | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/firmware-utils/src/zytrx.c b/tools/firmware-utils/src/zytrx.c index 302efc6010..b3bbbe3c69 100644 ---

[PATCH v3 0/2] Add support for ZyXEL LTE3301-Plus

2021-05-18 Thread André Valentin
This set adds support for the ZyXEL LTE3301-Plus, an indoor 3G/4G indoor LTE router with Wifi. André Valentin (2): firmware-utils: zytrx: Add support for ZyXEL LTE3301-Plus ramips: mt7621: Add support for ZyXEL LTE3301-Plus package/boot/uboot-envtools/files/ramips | 1 +

[PATCH 2/2] hostapd: wolfssl: add RNG to EC key

2021-05-18 Thread David Bauer
Since upstream commit 6467de5a8840 ("Randomize z ordinates in scalar mult when timing resistant") WolfSSL requires a RNG for the EC key when built hardened which is the default. Set the RNG for the EC key to fix connections for OWE clients. Signed-off-by: David Bauer ---

[PATCH 0/2] Fix OWE mode with hostapd-wolfssl

2021-05-18 Thread David Bauer
OWE operation of WolfSSL hostapd and wpad daemons has been broken since WolfSSL was updated to 4.5.0. This is due to the fact WolfSSL now requires a RNG for EC keys, however there is no stable interface available for hardened as well as non-hardened builds. Patch hostapd to add the RNG to the EC

[PATCH 1/2] wolfssl: always export wc_ecc_set_rng

2021-05-18 Thread David Bauer
Since commit 6467de5a8840 ("Randomize z ordinates in scalar mult when timing resistant") wolfssl requires a RNG for an EC key when the hardened built option is selected. wc_ecc_set_rng is only available when built hardened, so there is no safe way to install the RNG to the key regardless whether

Re: [PATCH] mvebu: 5.10: fix DVFS caused random boot crashes

2021-05-18 Thread Robert Marko
On Tue, May 18, 2021 at 8:36 PM Hauke Mehrtens wrote: > > On 5/18/21 7:03 PM, Robert Marko wrote: > > 5.10.37 introduced a lot of DVFS changes for Armada 37xx from 5.13 kernel. > > > > Unfortunately commit: > >

Re: [PATCH] mvebu: 5.10: fix DVFS caused random boot crashes

2021-05-18 Thread Hauke Mehrtens
On 5/18/21 7:03 PM, Robert Marko wrote: 5.10.37 introduced a lot of DVFS changes for Armada 37xx from 5.13 kernel. Unfortunately commit:

Resize of ath79 / ZyXEL NBG6716 kernel partition

2021-05-18 Thread Andre Valentin via openwrt-devel
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi! The NBG6716 has recently

[PATCH] mvebu: 5.10: fix DVFS caused random boot crashes

2021-05-18 Thread Robert Marko
5.10.37 introduced a lot of DVFS changes for Armada 37xx from 5.13 kernel. Unfortunately commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/cpufreq/armada-37xx-cpufreq.c?h=v5.10.37=a13b110e7c9e0dc2edcc7a19d4255fc88abd83cc This patch actually corrects the

Re: [RFC] OpenWrt within a Docker container

2021-05-18 Thread Paul Spooren
On 5/17/21 11:09 PM, Fernando Frediani wrote: Hello Certainly run /sbin/init or 'procd' to have *OpenWrt-like experience* is a better approach in my view. So do you prefer to disable some services and make some init-scripts "container aware"? Regards Fernando On 17/05/2021 15:39,

[PATCH] busybox: use $(AUTORELEASE) and SPDX

2021-05-18 Thread Paul Spooren
use AUTORELEASE since BusyBox is often updaten and PKG_RELEASE is not consistently bumped. Also use SPDX license headers to be machine readable and bump the copyright year to 2021. Signed-off-by: Paul Spooren --- I'd like to see this backported as well. package/utils/busybox/Makefile | 9

Re: Uniquely identifying a platform programmatically

2021-05-18 Thread Daniel Golle
On Mon, May 17, 2021 at 04:43:24PM -0600, Philip Prindeville wrote: > Hi, > > I was wondering what the best way to map a running box back to a candidate > image would be. > > It seems like the tuple ($CONFIG_TARGET_BOARD, $CONFIG_TARGET_SUBTARGET, > $CONFIG_TARGET_PROFILE) would provide this,

Re: [PATCH luci] luci-mod-network: use "ports" option for setting bridge ports

2021-05-18 Thread Rafał Miłecki
On 17.05.2021 14:10, Rafał Miłecki wrote: From: Rafał Miłecki netifd has been recently patched to use more accurate "ports" option instead of "ifname" Signed-off-by: Rafał Miłecki --- .../htdocs/luci-static/resources/tools/network.js | 4 ++-- 1 file changed, 2 insertions(+),

Re: [PATCH netifd] interface: rename "ifname" attribute to "device"

2021-05-18 Thread Paul Oranje via openwrt-devel
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- > Op 17 mei 2021, om 17:47

Re: Uniquely identifying a platform programmatically

2021-05-18 Thread Petr Štetiar
Philip Prindeville [2021-05-17 16:43:24]: > I could grovel the target profile out of /etc/board.json, but then my > scripting needs to support 'jq', etc. $ ubus call system board | jsonfilter -e @.model -e @.board_name -- ynezz ___ openwrt-devel

Re: Uniquely identifying a platform programmatically

2021-05-18 Thread Philip Prindeville
Okay, I've created a PR to make this change: https://github.com/openwrt/openwrt/pull/4184 > On May 17, 2021, at 4:43 PM, Philip Prindeville > wrote: > > Hi, > > I was wondering what the best way to map a running box back to a candidate > image would be. > > It seems like the tuple