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 ---
Barely a hint but I think the issu
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 s
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
--- a/tools/firmware-utils/
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
.../ramips/dts/mt7621_zyxel_lte3301-plus.dts | 213
On Fri, May 14, 2021 at 11:31:27PM +0200, Hauke Mehrtens wrote:
> On 5/14/21 12:17 PM, Paul Spooren wrote:
> > Hi,
> >
> > On 5/13/21 1:32 AM, Hauke Mehrtens wrote:
> > > Instead of adding all public signature keys from the openwrt-keyring
> > > repository only add the key which is used to sign th
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 ---
Added patch 030-make-documentatio
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 ---
This provides a way to override t
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 ---
This adjusts the Makefile to use
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 ---
This is an alternative solution t
Merged, thanks for the fix!
On 11-03-21, Youfu Zhang wrote:
> or uclient-fetch will stall until timeout for 2XX (except 204) response
> with content-length of 0
>
> Signed-off-by: Youfu Zhang
> ---
> uclient-http.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/ucli
On 5/14/21 12:17 PM, Paul Spooren wrote:
Hi,
On 5/13/21 1:32 AM, Hauke Mehrtens wrote:
Instead of adding all public signature keys from the openwrt-keyring
repository only add the key which is used to sign the master feeds.
If one of the other keys would be compromised this would not affect
us
Hi All,
Le ven. 14 mai 2021 à 05:00, Petr Štetiar a écrit :
>
> Fernando Frediani [2021-05-11 20:13:18]:
>
> Hi,
>
> > I am no sure https support should still be something by default in the
> > images as it's not something really essential
>
> to me it's like discussion about telnet versus SSH.
From: Rafał Miłecki
Bridge aggregates multiple ports so use a more accurate name ("ports").
For backward compatibility add a temporary config translation.
Config example:
config interface 'lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
Signed-off-by: Rafa
Paul Spooren writes:
> On 5/13/21 1:32 AM, Hauke Mehrtens wrote:
>> The signature verification of sysupgrade images is currently not used as
>> far as I know, so normal we do not need the keys for of other releases.
>
> If the `ucert` package is installed and the env variable
> `REQUIRE_IMAGE_SIG
Hi,
On 5/13/21 1:32 AM, Hauke Mehrtens wrote:
Instead of adding all public signature keys from the openwrt-keyring
repository only add the key which is used to sign the master feeds.
If one of the other keys would be compromised this would not affect
users of master snapshot builds.
Signed-off
On 5/14/21 10:32 AM, Petr Štetiar wrote:
OpenWrt 21.02 currently ships with wolfssl and LuCI for http. It would
be nice to also have https support included in the default images.
To add this the following packages have to be added:
* luci-ssl (969 Bytes ipkg)
* px5g-wolfssl (5216 byt
From: Rafał Miłecki
Bridge aggregates multiple ports so use a more accurate name ("ports")
and format (array) for storing them in board.json.
Example:
"network": {
"lan": {
"ports": [
"lan1",
"lan2",
Fernando Frediani [2021-05-11 20:13:18]:
Hi,
> I am no sure https support should still be something by default in the
> images as it's not something really essential
to me it's like discussion about telnet versus SSH. (Puting aside, that one
shouldn't be using password at all) If it's fine with
OpenWrt 21.02 currently ships with wolfssl and LuCI for http. It would
be nice to also have https support included in the default images.
To add this the following packages have to be added:
* luci-ssl (969 Bytes ipkg)
* px5g-wolfssl (5216 bytes ipkg)
The ath79 images increased by 2.2 KB
On 13.05.2021 17:47, Felix Fietkau wrote:
On 2021-05-13 15:58, Rafał Miłecki wrote:
Current /etc/config/network design and netifd implementation are quite a
bit messy:
1. There is no clear layer 2 vs. layer 3 distinction
I think aside from a few legacy compatibility hacks (e.g. the infamous
int
20 matches
Mail list logo
