ff02::2 multicast is not working in nanostation xw, but roger pueyo find
a way to solve it: revert commit
c8c2ef1d495dd3fd3096ac508e91a02f9c583ea8 (which is very short)
I don't know the implications of doing it. But it fixes a bug that
affects us a lot (we have lots of these devices and they do
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of pedrowrt
> Sent: Dienstag, 5. Mai 2020 10:36
> To: openwrt-devel@lists.openwrt.org
> Cc: yn...@true.cz
> Subject: [OpenWrt-Devel] Multicast issue in 19.07.x release and master,
I tested it using Staging tree of Chuanhong Guo [1], and it worked. Good
job. What are the next steps related to this?
I understand to not be included in future release (no problem, we can
inject the patch on our own), but in fact, it is not just a bug, it is a
regression, because it worked in
Move the image receipts into separate per-subtarget files like it is
done on most other targets.
Signed-off-by: David Bauer
---
target/linux/mpc85xx/image/Makefile | 100 +---
target/linux/mpc85xx/image/p1010.mk | 36 ++
target/linux/mpc85xx/image/p1020.mk | 41
The mpc85xx-generic subtarget supports the QorIQ SoCs of the p1010
family. Rename the subtarget to reflect this affiliation as it's the
case with the other mpc85xx subtargets.
Signed-off-by: David Bauer
---
target/linux/mpc85xx/Makefile | 2 +-
Hi Florian,
Actually I was preparing the same patch just a moment ago, and found out
that LEDS_TRIGGER_MTD is a bool, not tristate.
On 2020-05-04 19:26, Florian Eckert wrote:
Not every target needs this LED trigger. Therefore this trigger can be
installed as kernel module.
Signed-off-by:
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,
Thanks Chuanghong, I was
Hey Jeonghum,
> Thank you for the very kind message!
> I tried "mmcli -L" and received an error message:
> root at LEDE:~# mmcli -L
> error: couldn't create manager: Timeout was reached
>
This is extremely weird, and it would show some issue with your setup,
maybe with how DBus is
Hi!
On Wed, May 6, 2020 at 1:36 AM pedrowrt wrote:
>
> I tested it using Staging tree of Chuanhong Guo [1], and it worked. Good
> job. What are the next steps related to this?
>
> I understand to not be included in future release (no problem, we can
> inject the patch on our own), but in fact,
Hi,
> +include p1010.mk
> endif
You may take up John's idea for [1] here and just do
include $(SUBTARGET).mk
without all the ifs.
Best
Adrian
[1]
https://github.com/openwrt/openwrt/commit/220f43e0f2a0870305d40add4c3314edf150f9be
openpgp-digital-signature.asc
Description: PGP signature
From: Rafał Miłecki
As blockd uses uloop calling any script and using waitpid() can easily
result in a lock. It's enough for script to use /bin/ubus to cause that.
It's not an option to drop waitpid() as it's important to e.g. call
mount scripts with ACTION=remove before unmounting devices. So
Hello Alexander and people in the list,
Let me provide some additional information and new test log messages.
The problem I reported is improved one setp. Originally it was like:
root at LEDE:~# mmcli -L
error: couldn't create manager: Timeout was reached
Now it is like:
root@LEDE:~#
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,
You're right, it's a bug and
We discussed a bit in IRC, Chuanhong coded a new patch and suggested me
to try it
https://git.openwrt.org/?p=openwrt/staging/981213.git;a=commit;h=b34165fd386158cbb4d8c09e2c5127b3dee3219a
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
14 matches
Mail list logo
