On 11:28 Fri 10 Jan, Stefan Sperling wrote: > On Fri, Jan 10, 2020 at 12:52:44PM +0300, Consus wrote: > > On 20:06 Thu 09 Jan, Marc Espie wrote: > > > It's been that way for ages. But no-one volunteered > > > to work on this. > > > > Anyone even knows about this? Aside from OpenBSD developers (who have > > their plates full already) how an average person can find out that there > > is rusty piece of code that should be taken care of? > > Don't start looking at other people's problems before you can help yourself. > Rewriting automounter for Theo as a first contribution is not likely to work. > Find something small that annoys *you* and get involved by fixing that first. > Learn how to approach and debug issues that affect you directly. > > How did I get into OpenBSD wifi? > Because my OpenBSD access point stopped accepting new associations after > one about week of usage. It turned out this was one of those problems > which had been known for years and all this time people had been switching > to non-OpenBSD APs to work around it. I had lived with the problem for > about a year or two, resetting the wifi interface on the AP whenever it > happened. > > Then I noticed that 'ifconfig ath0 scan' showed a very long list of known > MAC addresses whenever the problem occurred. So I looked for a way trigger > the problem faster than in one week and succeeded by running this loop > on the client which made the problem appear after a few minutes: > > ifconfig iwn0 up > while sleep 5; do ifconfig iwn0 lladdr random; done > > Looking at the code I found that known MACs never expired! Once the AP had > reached its limit of learned MACs it accepted no new associations because > no room was made for new MAC addresses. Fix was a 3-line diff, which I > could verify with my above test.
Neat. Though I'm using OpenBSD only for a router and since issues preventing me from using it on a desktop (or NAS) are pretty huge to be my "good first issues" that's not an option, sadly. So only donations / occasional bug reports from me :D
