Daniel Golle

Generally this seems to be performance/timing related. The bug in hostapd/wpa_supplicant/wpad which caused those symptoms when using WolfSSL previously was to use a too costly function to generate random numbers...

I'm trying to understand how this call to `iw` is happening. In OpenWrt, we are automatically replacing `HT40` with `HT40-` or `HT40+` depending on band and channel, see https://github.com/openwrt/openwrt/blob/master/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh#L726 and...

I've picked that into master and as it is a fix, I'll cherry-pick it to 19.07 in a couple of days once more people have tested it.

I agree with @G10h4ck about the use of VLAN to allow interoperability with linux bridge on the same physical interface. I know this is a problem with some (few) switches...

As with Kernel 5.4 we switch MT7621 to the upstream DSA driver instead of swconfig it'd be interesting to test with with OpenWrt master snapshot and see if the issue...

So this is one nice network setup you are describing there, similar to what we have here (and using libremesh develop branch on top of OpenWrt snapshots for that). And...

Why only use `libremesh.mk` for packages which depend on `lime-system`? I thought it was mostly to automate versioning (like for luci-* packages)...?

> > Why only use `libremesh.mk` for packages which depend on `lime-system`? > > I'm not sure I got the question, but I try to answer: inside `libremesh.mk` there is...

> Pitbull does not have an initial plan for bandwith rating for now, but may have in the future. > It is also relevant what was said in the mailing...

> On bmx7 it seems to change and distribute the hostname even without a restarting/reloading bmx7 nor running lime-config Yes, because procd is handling the reloads...