Thanks for the tip! On Sun, 19 Nov 2017 at 18:31, <[email protected]> wrote:
> On Sun, Nov 19, 2017 at 11:11:44AM +0000, Chavdar Ivanov wrote: > > Here my point was that iwn used to work under XEN3_DOM0 a few months > > ago and is not working now, which may indicate some problem or > > regression elsewhere, which was the main reason for my question. > > 'Git bisect' is a good way to quickly point out issues, you can > probably bisect iwn file changes only. > > > the way, speedtest.net maybe a lame way to test a wifi connection, but > > on mine (200mb/s cable) connection, running -current with iwn gives me > > about 23mb/s, whereas on the same hardware / dns / router etc. some > > Linux gives me about 57 mb/s ( I do get my full about 212mb/s when > > running the test over AC7275 wifi from my W10 laptop, so it is not the > > infrastructure, with the possible exception that NetBSD runs off a > > HDD, whereas the Linux distro off an SSD, but that probably doesn't > > matter here. ). > > it looks like in your scenario: > netbsd: 802.11g > linux: 802.11n > windows : 802.11ac > > netbsd lacks stack support for 802.11n/ac, but also would need to adapt > the driver for it once it happens. >
