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 Stefan and Daniel,
On 8/2/20 8
As it appears, these devices just needed a resize of their os-image
partition. Increase it to 0x30, so we have some extra space left
for future kernels.
Note that this only adjusts the partioning scheme, but since I
do not own the device I cannot say whether the bootloader will
actually cope w
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Andre Valentin
> Sent: Dienstag, 4. August 2020 17:48
> To: openwrt-devel@lists.openwrt.org
> Subject: Re: Fate of 4.14 targets / samsung odroid HC1 support
>
> Hi!
>
> I've enabled
On 04.08.2020 09:57, Jo-Philipp Wich wrote:
Regarding parsing events stream, event names with spaces seem to be OK:
https://html.spec.whatwg.org/multipage/server-sent-events.html#parsing-an-event-stream
To me it feels quirky to separate the path and the type of the event by space.
Personally I
On 04.08.2020 09:43, Andre Valentin wrote:
Am 03.08.20 um 07:49 schrieb Rafał Miłecki:
On 31.07.2020 13:02, Andre Valentin wrote:
this is really great stuff. It would help me to get forward with my wifi
controller.
Could it be possible to subsribe to multiple sources to limit the connections
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Andre Valentin
> Sent: Dienstag, 4. August 2020 17:48
> To: openwrt-devel@lists.openwrt.org
> Subject: Re: Fate of 4.14 targets / samsung odroid HC1 support
>
> Hi!
>
> I've enabled
Hi!
I've enabled support for the odoid HC1 in the samsung target a month ago, it
only needs generic 5.4 kernel and is a subtarget.
https://www.hardkernel.com/shop/odroid-hc1-home-cloud-one/
Only open thing is the boodloader on the sdcard, which is a binary for
hardkernel.
If there is interest I
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Baptiste Jonglez
> Sent: Donnerstag, 30. Juli 2020 20:58
> To: openwrt-devel@lists.openwrt.org
> Cc: Thomas Endt
> Subject: Upcoming 19.07.4 and 18.07.9 stable releases
>
> Hi,
>
>
Hi,
for ramips/mt7621, the wpad-basic package is not selected by default, but added
for every device individually.
While this might be technically correct if the SoC does not come with a Wifi
module, only 18 of 97 devices for that platform are set up _without_ wpad-basic
currently.
Therefore,
Hi together,
with bcm47xx/bcm53xx bumped to 5.4 now (thanks!), we are left we the following
targets that (most likely) won't be moved to 5.4 anymore:
4.19: cns3xxx
4.14: ar71xx, at91, ath25, pistachio, rb532, samsung, uml
Now, where 20.xx comes closer, I wonder whether we should remove the 4.14
From: Petr Štetiar
In order to support SAE/WPA3-Personal in default images. Replaced almost
all occurencies of wpad-basic and wpad-mini with wpad-basic-wolfssl for
consistency. Keeping out ar71xx from the list in order to make the
backports easier.
Signed-off-by: Petr Štetiar
[rebase]
Signed-of
From: Petr Štetiar
Add package which provides size optimized wpad with support for just
WPA-PSK, SAE (WPA3-Personal), 802.11r and 802.11w.
Signed-off-by: Petr Štetiar
[adapt to recent changes, add dependency for WPA_WOLFSSL config]
Signed-off-by: Adrian Schmutzler
---
include/target.mk
Most targets have been updated to consistently use the vendor_model
scheme for device definitions and thus, image names.
Apply this to bcm53xx as well. This does _not_ apply any other
specific naming changes.
Cc: Rafał Miłecki
Signed-off-by: Adrian Schmutzler
---
target/linux/bcm53xx/image/Mak
Hi,
I have a TP-Link TL-WR841N v13 with OpenWrt 19.07.3 connected to a HP
switch trough the WAN port.
Very often there is the following trouble:
Tue Aug 4 14:35:52 2020 kern.info kernel: [ 5603.569886] rt3050-esw
1011.esw: link changed 0x10
Tue Aug 4 14:35:54 2020 kern.info kernel: [ 5
We want to be able to make full system images for this system too, just
as we now can for the MT7623 platforms.
The package directory (mt7623n) is now a bit misnamed as it's overly
specific, but the precise set of platforms which we support this way
is evolving and we'll fix it up when the dust se
Now that my patches have been merged into upstream U-Boot, resync the
cosmetic changes and the commit IDs from the final commits.
Signed-off-by: David Woodhouse
---
.../patches/006-mt7623-pinctrl-fix.patch | 7 ++--
.../patches/007-env-fat-use-bootdevice.patch | 35 ---
..
Hi Rui,
On 03.08.20 22:14, Rui Salvaterra wrote:
BusyBox ip (rule) applet supports fwmark for policy routing (albeit through the
old and deprecated RTA_PROTOINFO message attribute), but fwmask is completely
unsupported. For this reason, mwan3 depends on ip(-tiny), which compiles to
over 280 kiB
BusyBox ip (rule) applet supports fwmark for policy routing (albeit through the
old and deprecated RTA_PROTOINFO message attribute), but fwmask is completely
unsupported. For this reason, mwan3 depends on ip(-tiny), which compiles to
over 280 kiB on MIPS32 (-mips16 -mtune=74kc -O2).
This pending [
Hi,
> Regarding parsing events stream, event names with spaces seem to be OK:
> https://html.spec.whatwg.org/multipage/server-sent-events.html#parsing-an-event-stream
To me it feels quirky to separate the path and the type of the event by space.
Personally I'd only report the type as "event:" an
Hi!
Am 03.08.20 um 07:49 schrieb Rafał Miłecki:
> On 31.07.2020 13:02, Andre Valentin wrote:
>> this is really great stuff. It would help me to get forward with my wifi
>> controller.
>> Could it be possible to subsribe to multiple sources to limit the
>> connections to ubus?
>> 2 SSIDs with 2.4
Hi,
Keep in mind master sets CONFIG_KERNEL_KALLSYMS whereas stable builds
do not. That alone makes a bit of a size difference (never checked how
much). Other than that, 5.4 needs more space than 4.14 does (again, how
much exactly I have not quantified).
Thanks for that hint. Disabling CONFIG_
Before this commit, if uci option "dnssec" was set, we pass "--dnssec"
and friends to dnsmasq, let it start and decide whether to quit and
whether to emit message for diagnosis
# dnsmasq --dnssec; echo $?
dnsmasq: DNSSEC not available: set HAVE_DNSSEC in src/config.h
1
DNSSEC as a feature i
22 matches
Mail list logo
