[PATCH] ramips: overwrite reset gpio properties in EX6150 DTS.

The Netgear EX6150 can, just like the D-Link DIR-860L rev B1, fail to initialise both radios in some cases. Add the reset GPIOs explicitly so the PCI-E devices get re-initialised properly. See also FS #3632. Error shows up in dmesg as follows: [1.560764] mt7621-pci 1e14.pcie: pcie1 no

Re: Re: uboot-envtools build error in openwrt-21.02.

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, maybe I can add some

Re: uboot-envtools build error in openwrt-21.02.

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 --- On 19.02.21, 01:10, "Etan

Re: [PATCH] lantiq: ARV752DPW22: set the usb led trigger via devicetree

2/19/21 2:17 PM, Adrian Schmutzler: -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Mathias Kresin Sent: Dienstag, 16. Februar 2021 19:35 To: openwrt-devel@lists.openwrt.org Subject: [PATCH] lantiq: ARV752DPW22: set the usb led trigger

Re: [PATCH] wireguard-tools: Add dependency on kmod-wireguard

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 18 feb. 2021, om 18:48 heeft

[PATCH 1/1] firewall3: remove last remaining sprintf()

From: Philip Prindeville Signed-off-by: Philip Prindeville --- iptables.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/iptables.c b/iptables.c index 9e8fa743c99f84222307128047d40d657916aa75..49b34394dfec4df361ec1cf6778cade831454c7c 100644 --- a/iptables.c +++

[PATCH] LuCI: implement TLS client certificate authentication

When available, pass TLS client certificate data (subject name & cert hash) to the rpcd daemon for authentication (as username and password). Add an extra mode='cert' parameter, so the rpcd is aware they come from certificate and are treated accordingly Signed-off-by: Luka Logar ---

[PATCH] rpcd: implement certificate authentication

When the TLS client certificate is used for LuCI authentication, ubus session login is called with username = subject name password = certificate hash mode = 'cert' Extra parameter 'mode' is needed to differentiate a regular username/password login attempt from the client certificate

[PATCH] OpenWRT: add option to uhttpd init script for enabling TLS client cert auth

Add option client_auth=path_to_ca_cert_file to the uhttpd config file. Only client certificates issued by a specified CA can be used for client authentication. Signed-off-by: Luka Logar --- package/network/services/uhttpd/files/uhttpd.config | 3 +++

LuCI client certificate authentication

The above series of patches puts everything in place for the LuCI TLS client certificate authentication. The authentication is disabled by default and must be enabled in uhttpd config by setting uci set uhttpd.main.client_auth='/etc/ssl/certs/clientCA.crt' Also, user/certificate must be added

[PATCH] uhttpd: implement TLS client certificate authentication

Enable client certificate authentication by specifying a -b path_to_ca_cert_file on the command line. When this parameter is set, TLS server requests a client certificate (signed by the specified CA). If client certificate authentication is successful, client cert data is stored in

[PATCH] ustream-ssl: store TLS peer cert data in a ustream_ssl structure

Store peer certificate, it's sha256 hash and subject name in ustream_ssl struct, so the upper layer can access and use this data. This data can then be used, for example, in client authentication. Signed-off-by: Luka Logar --- ustream-openssl.c | 22 ++ ustream-ssl.c |

Re: [PATCH 0/5] mvebu: add support for Linux 5.10

Compile mvebu targets caiman, cobra, mamba, shelby, rango, venom with PR3852 yielding size with 5.10.17 kernel for the two with partition issue 3336591 Feb 19 11:33 linksys_wrt1900ac-v1-kernel.bin 3331919 Feb 19 11:33 linksys_wrt32x-kernel.bin Run test on mamba OpenWrt SNAPSHOT,

Strongswan testers wanted

Hi, I have some patches to Strongswan (mostly in packaging and UCI generation, not the Strongswan binaries themselves) that I'd like independent testing and verification. The maintainers have limited bandwidth to test, so others testing and finding bugs and me fixing them first might be more

[PATCH 0/5] mvebu: add support for Linux 5.10

This series adds initial support for 5.10 on mvebu. Build/runtime-tested on a Turris Omnia, no regressions noticed. Rui Salvaterra (5): mvebu: add 5.10 kernel config mvebu: copy 5.4 patches to 5.10 mvebu: refresh 5.10 patches mvebu: update the Turris Omnia device tree mvebu: add 5.10 as

[PATCH 4/5] mvebu: update the Turris Omnia device tree

Include support for the multicolor LEDs (software controlled, for now) and fix the hardware buffer management support, due to a missing mbus window. Signed-off-by: Rui Salvaterra --- ...-dts-turris-omnia-update-device-tree.patch | 276 ++ 1 file changed, 276 insertions(+)

[PATCH 1/5] mvebu: add 5.10 kernel config

Basically make kernel_oldconfig from 5.4. Signed-off-by: Rui Salvaterra --- target/linux/mvebu/config-5.10 | 439 + 1 file changed, 439 insertions(+) create mode 100644 target/linux/mvebu/config-5.10 diff --git a/target/linux/mvebu/config-5.10

[PATCH 5/5] mvebu: add 5.10 as a testing kernel

Keep 5.4 as stable until further validation. Signed-off-by: Rui Salvaterra --- target/linux/mvebu/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/mvebu/Makefile b/target/linux/mvebu/Makefile index 1e67bcfacb..1550309a92 100644 ---

Re: [PATCH] wireguard-tools: Add dependency on kmod-wireguard

https://github.com/openwrt/openwrt/pull/3890 Voila -- here's a potentially much, much nicer approach in the long term. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

RE: [PATCH v2] lantiq: vr9: set the usb led trigger via devicetree

> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Mathias Kresin > Sent: Mittwoch, 17. Februar 2021 20:52 > To: openwrt-devel@lists.openwrt.org > Subject: [PATCH v2] lantiq: vr9: set the usb led trigger via devicetree > > Assign the

RE: [PATCH] lantiq: ARV752DPW22: set the usb led trigger via devicetree

> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Mathias Kresin > Sent: Dienstag, 16. Februar 2021 19:35 > To: openwrt-devel@lists.openwrt.org > Subject: [PATCH] lantiq: ARV752DPW22: set the usb led trigger via devicetree > >

RE: [PATCH] wireguard-tools: Add dependency on kmod-wireguard

Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Ilya Lipnitskiy > Sent: Freitag, 19. Februar 2021 02:45 > To: Hannu Nyman > Cc: Jason A . Donenfeld ; openwrt-devel de...@lists.openwrt.org>; Adrian Schmutzler > Subject: Re:

Re: [PATCH] wireguard-tools: Add dependency on kmod-wireguard

On Fri, Feb 19, 2021 at 5:48 AM Rosen Penev wrote: > > On Thu, Feb 18, 2021 at 8:31 PM Ilya Lipnitskiy > wrote: > > > > Hi, > > On Thu, Feb 18, 2021 at 5:57 PM Jason A. Donenfeld wrote: > > > > > > I've backported WireGuard patch-by patch to 5.4, in a series that you > > > can simply apply to

Re: [PATCH v2] ramips: overwrite reset gpio properties in DIR-860L DTS

On Thu, Feb 18, 2021 at 2:13 PM Stijn Segers wrote: > > As suggested by Sergio, this adds GPIOs 19 and 8 explicitly into the > DIR-860L DTS, so the PCI-E ports get reset and the N radio (radio1) > on PCI-E port 1 comes up reliably. > > Fixes the following error that popped up in dmesg: > > [