If gettext-full happens to be built after glib2/host, it picks up the
host build and tries to link to it with an inappropriate rpath. Instead
of working around the issue, just use the included glib to avoid it.
Signed-off-by: Rosen Penev
---
package/libs/gettext-full/Makefile | 6 +++---
1 file
On 7/24/20 11:56 AM, Petr Štetiar wrote:
> Refreshed patches. Removed upstreamed patches:
>
> 001-remove-stime-function-calls.patch
> 110-no_static_libgcc.patch
>
> Run tested on x86_64 under QEMU.
>
> Signed-off-by: Petr Štetiar
> ---
> package/utils/busybox/Makefile| 4 +-
On 2020-07-24 18:44, Jo-Philipp Wich wrote:
> Hi Felix,
>
>> [...]
>>
>> For a simple default config, you could have this:
>>
>> # network
>> config device
> option type bridge # I assume this is needed as well
>> option name switch0
Correct.
>> config bridge-vlan
>> option
Hi Felix,
> [...]
>
> For a simple default config, you could have this:
>
> # network
> config device
option type bridge # I assume this is needed as well
> option name switch0
>
> config bridge-vlan
> option vlan 1
> option ports "lan1 lan2 lan3 lan4"
>
>
The required BusyBox applets are enabled by default, so we can rely on them
being present in the system. This way, we make sure there are no conflicts with
less featured variants of these same applets which might also be present in the
system.
v3: Make sure the required applets are enabled at
Hi, Henrique,
On Fri, 24 Jul 2020 at 16:51, Henrique de Moraes Holschuh
wrote:
>
> Hmm, why not fix this for *good* and not depend on they being enabled in
> busybox "by default"?
>
> I'd just depend on the required busybox features and applets explicitly
> (or select them) *on top of what your
On 24/07/2020 11:29, Petr Štetiar wrote:
As there is now WolfSSL included by default due to SAE/WPA3 we can
finally switch to TLS/SSL in other parts as well.
+DEFAULT_PACKAGES:= \
+ base-files libc libgcc busybox dropbear mtd uci opkg netifd \
+ fstools uclient-fetch logd
On 24/07/2020 12:07, Rui Salvaterra wrote:
The required BusyBox applets are enabled by default, so we can rely on them
being present in the system. This way, we make sure there are no conflicts with
Hmm, why not fix this for *good* and not depend on they being enabled in
busybox "by default"?
Hi,
On 24-07-20, Yousong Zhou wrote:
> Fixes FS#3231
It looks like this bug also affects 18.06 and 19.07, so the fix should
probably be backported.
Baptiste
> Signed-off-by: Yousong Zhou
> ---
> zones.c | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/zones.c b/zones.c
>
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Petr Štetiar
> Sent: Freitag, 24. Juli 2020 16:30
> To: openwrt-devel@lists.openwrt.org
> Cc: Petr Štetiar
> Subject: [PATCH 2/3] treewide: use wpad-basic-wolfssl as default
>
The required BusyBox applets are enabled by default, so we can rely on them
being present in the system. This way, we make sure there are no conflicts with
less featured variants of these same applets which might also be present in the
system.
Fixes: 0bd7dfa3ed60588ec83a8f60f48b6991ebb16940
The required BusyBox applets are enabled by default, so we can rely on them
being present in the system. This way, we make sure there are no conflicts with
less featured variants of these same applets which might also be present in the
system.
Fixes: 0bd7dfa3ed60588ec83a8f60f48b6991ebb16940
On Fri, Jul 24, 2020 at 04:29:38PM +0200, Petr Štetiar wrote:
> Add package which provides wpad with WPA-PSK, SAE (WPA3-Personal),
> 802.11r and 802.11w support.
I think this should be merged with wpad-mesh. It's almost the same, but
only adds support for 802.11s mesh in addition.
>
>
Hi,
it has been discussed several times and some of core developers would like to
include SSL/TLS and WPA3-Personal/SAE support in the next release as we've
dropped support for 4/32M devices officialy with 19.07 and it's time to move
on and improve the default security features in official
In order to support SAE/WPA3-Personal in default images.
Signed-off-by: Petr Štetiar
---
target/linux/apm821xx/image/sata.mk | 2 +-
target/linux/apm821xx/nand/target.mk | 2 +-
.../apm821xx/sata/profiles/00-default.mk | 2 +-
target/linux/ar71xx/generic/target.mk
Add package which provides wpad with WPA-PSK, SAE (WPA3-Personal),
802.11r and 802.11w support.
Signed-off-by: Petr Štetiar
---
include/target.mk | 2 +-
package/network/services/hostapd/Config.in | 2 ++
package/network/services/hostapd/Makefile | 20
As there is now WolfSSL included by default due to SAE/WPA3 we can
finally switch to TLS/SSL in other parts as well.
Signed-off-by: Petr Štetiar
---
README | 2 +-
include/target.mk | 6 +-
include/version.mk | 2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
diff --git
On some of the devices pressing Wifi button does not disable the Wifi.
Current rfkill code execute "wifi up" command instead of only "wifi".
This patch fix it.
Todor Colov (1):
Fix Wifi Button - off function not working
package/base-files/files/etc/rc.button/rfkill | 2 +-
1 file changed, 1
Signed-off-by: Todor Colov
---
package/base-files/files/etc/rc.button/rfkill | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/base-files/files/etc/rc.button/rfkill
b/package/base-files/files/etc/rc.button/rfkill
index fbdda40ed5..2d4f0f86ff 100755
---
This problem has been fixed in upstream commit
6b6a3d9339f1c08efaa18a7fb7357e20b48bdc95. This patch now (harmlessly)
adds the same definition a second time.
Signed-off-by: Magnus Kroken
---
.../patches/130-mconf_missing_sigwinch.patch| 13 -
1 file changed, 13 deletions(-)
Hi, Petr,
On Fri, 24 Jul 2020 at 11:08, Petr Štetiar wrote:
>
> perhaps you should send such dependencies as patch series next time.
Will do, for sure. At the time I was still working on my git workflow
and didn't know how to reorder patches in my tree, sorry about that.
> Using /sbin/swapon
Am 24.07.2020 um 10:34 schrieb Rui Salvaterra:
> Do you by chance have block-mount installed? The block-mount swapon
> utility is more limited than the one BusyBox provides. I sent patches
> to remove swapon/swapoff from block-mount (they're not needed to
> handle fstab/hotplug swap mounts), but
Hi again, Jason,
On Fri, 24 Jul 2020 at 10:12, Jason A. Donenfeld wrote:
>
> This might be a typical use case for you, but some people are running
> scripts that generate lots of keys. There may be a good argument that
> if you're doing that kind of thing, a tiny MIPS router isn't the right
>
Rui Salvaterra [2020-07-24 09:34:58]:
Hi,
> Do you by chance have block-mount installed? The block-mount swapon
> utility is more limited than the one BusyBox provides. I sent patches
> to remove swapon/swapoff from block-mount (they're not needed to
> handle fstab/hotplug swap mounts),
Refreshed patches. Removed upstreamed patches:
001-remove-stime-function-calls.patch
110-no_static_libgcc.patch
Run tested on x86_64 under QEMU.
Signed-off-by: Petr Štetiar
---
package/utils/busybox/Makefile| 4 +-
.../001-remove-stime-function-calls.patch | 84
On 2020-07-24 10:37, Jo-Philipp Wich wrote:
> Hi Luiz,
>
> I mostly agree with your proposal (though I'd call "device_for" simply
> "bridge" instead but that's details).
>
> I don't think everything can be simply switched in one go but I do think your
> proposal could be broken down into the
Hi David,
> Instead of using the overlay filesystem du jour, perhaps it makes more
> sense to simply put the tarball itself, raw, on the loop device
> immediately after the end of the squashfs?
I suppose the limiting factor for the maximum backup size would be the amount
of available RAM then?
We were playing on IRC with a way to write the backup file directly out
alongside the root file system for block devices, similar to the way
that it happens with 'mtd write -j sysupgrade.tgz'.
A lot of devices currently put it in a FAT "recovery" partition but
it's not clear that will always be
On Fri, Jul 24, 2020 at 11:05 AM Rui Salvaterra wrote:
>
> On Fri, 24 Jul 2020 at 09:53, Jason A. Donenfeld wrote:
> >
> > Testing the process once like that isn't a good testing methodology
> > representative of anything at all.
>
> I completely agree, this wasn't an objective test at all. I
On Fri, 24 Jul 2020 at 09:53, Jason A. Donenfeld wrote:
>
> Testing the process once like that isn't a good testing methodology
> representative of anything at all.
I completely agree, this wasn't an objective test at all. I was merely
illustrating what a normal user will do, generate a key pair
On Fri, Jul 24, 2020 at 10:39 AM Rui Salvaterra wrote:
>
> Well…
>
> On Fri, 24 Jul 2020 at 09:32, Rosen Penev wrote:
> >
> > > On Jul 24, 2020, at 1:14 AM, Jason A. Donenfeld wrote:
> > >
> > > Seems probably fine to me, but would you let me know if the
> > > performance of `wg pubkey` suffers
Well…
On Fri, 24 Jul 2020 at 09:32, Rosen Penev wrote:
>
> > On Jul 24, 2020, at 1:14 AM, Jason A. Donenfeld wrote:
> >
> > Seems probably fine to me, but would you let me know if the
> > performance of `wg pubkey` suffers as a result?
> Of course. I imagine it’s very tiny. Logging in to the
Hi Luiz,
I mostly agree with your proposal (though I'd call "device_for" simply
"bridge" instead but that's details).
I don't think everything can be simply switched in one go but I do think your
proposal could be broken down into the following measures.
The simple things:
- Rename "config
Hi,
On Fri, 24 Jul 2020 at 08:43, e9hack wrote:
>
> Hi,
>
> zram-swap is since commit 'zram-swap: enable swap discard' broken. Starting
> zram results in this:
>
> root@WLAN-DSL8:~# /etc/init.d/zram start
> zram_start: activating '/dev/zram2' for swapping (60 MegaBytes)
> zram_reset: enforcing
> On Jul 24, 2020, at 1:14 AM, Jason A. Donenfeld wrote:
>
> On Fri, Jul 24, 2020 at 10:03 AM Rui Salvaterra
> wrote:
>>
>> The wg utility compiles and runs without issues in MIPS16 mode, despite
>> setting
>> PKG_USE_MIPS16:=0 in the makefile. Let's remove this, allowing for a
>>
On Fri, Jul 24, 2020 at 10:03 AM Rui Salvaterra wrote:
>
> The wg utility compiles and runs without issues in MIPS16 mode, despite
> setting
> PKG_USE_MIPS16:=0 in the makefile. Let's remove this, allowing for a
> substantial
> size reduction of the wg executable. Since wg is a just a
The wg utility compiles and runs without issues in MIPS16 mode, despite setting
PKG_USE_MIPS16:=0 in the makefile. Let's remove this, allowing for a substantial
size reduction of the wg executable. Since wg is a just a configuration utility,
it shouldn't be performance-critical, as the crypto
Hi,
> Fixes FS#3231
>
> Signed-off-by: Yousong Zhou
Acked-by: Jo-Philipp Wich
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi,
zram-swap is since commit 'zram-swap: enable swap discard' broken. Starting
zram results in this:
root@WLAN-DSL8:~# /etc/init.d/zram start
zram_start: activating '/dev/zram2' for swapping (60 MegaBytes)
zram_reset: enforcing defaults via /sys/block/zram2/reset
zram_comp_algo: Set
39 matches
Mail list logo
