On 05/18/2018 04:24 PM, John Andersen wrote:
Is that an issue these days? N has been common for years and b shouldn't be used as it isn't secure. It will also cause a significant performance hit. My access point is configured for n only.
Yes, it is an issue these days. Apparently the driver is upstream, delivered with the kernel, and as of 4.14 it was still wrong on Manjaro. Maybe this fix never was backported to Opensuse's 4.12 kernel until very recently.
Are there really that many b or n networks where being stuck on n would cause a problem? I don't have a single device that won't work on n, so I configured my AP to be n only. Is there anyone still using b? One big problem with it is that is uses a different modulation method than all the other letters. This means that when a g or n device hears a b signal, it has to first send a b frame to reserve time for the g or n frame to follow. This causes the performance hit. With all other types, it's only necessary to send the frame header at the slower rate and then the data at whatever rate is possible. This results in a far smaller hit when, for example, there's a g device that's heard by an n. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org