Hello Stefan, thanks for you reply and - as stated in the other message - sorry for wasting your time!
Rest of my reply below, inline... s...@stsp.name (Stefan Sperling), 2019.06.10 (Mon) 10:35 (CEST): > On Mon, Jun 10, 2019 at 10:30:21AM +0200, Stefan Sperling wrote: > > On Sun, Jun 09, 2019 at 07:57:29PM +0200, Marcus Merighi wrote: > > > >Synopsis: iwn(4) and urtwn(4) no network on x220 > > > >Category: system amd64 wireless 802.11 > > > >Environment: > > > System : OpenBSD 6.5 > > > Details : OpenBSD 6.5-current (GENERIC.MP) #11: Sat Jun 8 12:30:43 > > > MDT 2019 > > > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > > > Architecture: OpenBSD.amd64 > > > Machine : amd64 > > > >Description: > > > No network via iwn(4) and urtwn(4), holmer* are wanted ones via > > > "join", holmer5 exists but does not show up: > > > > holmer5 sounds like a 5ghz AP. > > urtwn devices do not support 5ghz so they can't work with this AP. I have iwn(4) built in and used urtwn(4) just for testing. > > > iwn0: + 04:f0:21:3b:cb:f4 1 +219 54M ess privacy rsn "holmern" > > > iwn0: SCAN -> AUTH > > > iwn0: sending auth to 04:f0:21:3b:cb:f4 on channel 1 mode 11g > > > iwn0: AUTH -> SCAN > > > > Your AP "holmern" is not responding to our AUTH requests, so naturally > > we won't try to associate to it. This is the OpenBSD Access Point, mentioned in the other message, and, combined with my PEBKAC, the actual problem. > Forgot to add: Your iwn should work with a 5ghz AP but you need to > give it some time to scan and connect. The firmware tends to miss > beacons on 5ghz channels for reasons unkown to me; connecting on 5ghz > with iwn is known to be flaky. iwm(4) works much better in this regard. I haven't noticed it's flaky, yet. It is my home setup, used daily. Will watch out... Marcus
