[FS#4099] Mesh 802.11s blackhole due to bogus mpath routes with nexthop 00:00:00:00:00:00

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#4099 - Mesh 802.11s blackhole due to bogus mpath routes with nexthop 00:00:00:00:00:00
User who did this - John T (jonozzz)

----------
I'm running on slightly older master: [[https://github.com/openwrt/openwrt/commit/0470159552|0470159552]]

I used to experience something similar, albeit not as many null nexthops in my mpath dump. I remember seeing 2-3 at a time. I have a mesh between a Netgear EA8500 and an EX6400, not sure if that matters at all.

For me, when this issue was happening the radio the mesh network was on (in my case 5ghz) was going down for no reason. All my APs share the same SSID for both 2ghz and 5ghz so the way I was able to tell that one of the radios on APs was dead was to use WifiMan app on my phone. The workaround was to shutdown the radio and start it again, or trigger a scan (iw dev mesh0 scan freq 5785)

However, about 3 weeks ago I changed these 802.11r options on all APs:
        option reassociation_deadline '20000'
        option ft_over_ds '0'
and surprisingly I haven't had any issues since.

So, I'm still not sure what's happening and I don't have any repro steps.

I'll update if, for some reason, it starts happening again.


----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=4099#comment10223

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.