Re: WDS stopped working in 21.02, looking for bug in netifd, BUG FOUND!

2021-09-23 Thread Daniel Haid
Hi everyone, I think I finally located the problem! There is a race condition between hostapd and netifd. In hostapd, src/drivers/driver_nl80211.c, look at the function i802_set_wds_sta. There are calls to 1) nl80211_create_iface and 2) linux_br_add_if. Now call 1) seems to trigger netifd

Master failing to compile: patch 379-mac80211-fix-starting-aggregation-sessions-on-mesh-i fails to apply

2021-09-23 Thread Federico Capoano
Hi Everyone, I want to compile on the current master to see if some of the issues that are affecting me on the openwrt-21.02 branch are fixed (if these bugs aren't fixed I may be able to send a proper bug report after ruling out they're not fixed in master). However, the compilation fails here:

Re: [PATCH] ramips: switch to 5.10 kernel

2021-09-23 Thread Ilya Lipnitskiy
Oops, this is a duplicate of https://patchwork.ozlabs.org/project/openwrt/patch/20210909084441.1756-1-rsalvate...@gmail.com/, please disregard. On Thu, Sep 23, 2021 at 11:20 AM Ilya Lipnitskiy wrote: > > 5.10 has been working for many months on ramips targets - time to > promote it from testing

Re: WDS stopped working in 21.02, looking for bug in netifd

2021-09-23 Thread Bastian Bittorf
On Thu, Sep 23, 2021 at 03:17:15PM +0200, Daniel Haid wrote: > Is there any way to dump a detailed state of the wlan driver in the kernel? > Or the state of netifd? Sould I enable some debug options? at least you can try to debug with 2 terminals an running: iw event ip monitor bye, Bastian

[PATCH] ramips: switch to 5.10 kernel

2021-09-23 Thread Ilya Lipnitskiy
5.10 has been working for many months on ramips targets - time to promote it from testing to default. Signed-off-by: Ilya Lipnitskiy --- target/linux/ramips/Makefile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/target/linux/ramips/Makefile b/target/linux/ramips/Makefile

Re: WDS stopped working in 21.02, looking for bug in netifd

2021-09-23 Thread Daniel Haid
Another update: If I issue the following commands: 1. /etc/init.d/network restart 2. ip addr 3. ip addr 4. ip addr Then, in a "bad case", if the timing is right, 2. shows that the interface wlan0.sta1 is DOWN, 3. shows that it is UP and 4. shows that is DOWN again. Then it stays DOWN. This

Re: [PATCH] dnsmasq: add match_tag for --dhcp-host

2021-09-23 Thread Paul D
Did not understand significance of vendorclass. Should this give a new option for uci, match_tag? On 2021-09-23 09:28, Paul Fertser wrote: A set of tags can be specified for --dhcp-host option to restrict the assignment to the requests which match all the tags. Example usage: config

[PATCH] dnsmasq: add match_tag for --dhcp-host

2021-09-23 Thread Paul Fertser
A set of tags can be specified for --dhcp-host option to restrict the assignment to the requests which match all the tags. Example usage: config vendorclass option networkid 'udhcp' option vendorclass 'udhcp' config host option mac '*:*:*:*:*:*' list match_tag