To be honest, I have always used it without many troubles on many machines and never checked that. By the way, on the same T61p I was doing the same test there is also a W10 partition, it runs as fast as it can on that hardware, but the driver is ancient and from time to time I am getting BSODs, sometimes a few times a day. It probably is some hardware fault, as under NetBSD I occasionally get resets and the interface stops working, but I only have to restart rc.d/network and all is ok, no panics. The only problem I have is that for some reason my wifi netbsd hosts (two laptops and a Raspberry Pi Zero) lose or mess up their arp tables to other wireless hosts - but never to the machines connected to the router via an Ethernet cable (at the moment another Raspberry Pi model B running my local unbound server and some other stuff), so I have to jump trough it and tell them to ping, or even to remove the arp entry which shows as 'incomplete'. Go figure, but it is not a problem. I actually added 'arp -s' commands in /etc/rc.local, this seems to help and I am getting the same problem rarely now.
Chavdar On 19 November 2017 at 20:34, Michael van Elst <mlel...@serpens.de> wrote: > ci4...@gmail.com (Chavdar Ivanov) writes: > >>Here my point was that iwn used to work under XEN3_DOM0 a few months >>ago and is not working now, > > Hmm. iwn is working on bare metal for me. It should work on XEN3_DOM0. > >>which may indicate some problem or >>regression elsewhere, which was the main reason for my question. By >>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 > > Our wifi code currently only supports 802.11a/b/g but not n or ac. > > > -- > -- > Michael van Elst > Internet: mlel...@serpens.de > "A potential Snark may lurk in every tree." -- ----