From nobody Wed Feb 01 09:25:08 2023
X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P6GjN2KsGz3bRtH
	for <freebsd-wireless@mlmmj.nyi.freebsd.org>; Wed,  1 Feb 2023 09:25:12 +0000 (UTC)
	(envelope-from developer@lorenzosalvadore.it)
Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
	 client-signature RSA-PSS (4096 bits) client-digest SHA256)
	(Client CN "protonmail.com", Issuer "R3" (verified OK))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4P6GjN18p5z3ldr
	for <freebsd-wireless@freebsd.org>; Wed,  1 Feb 2023 09:25:12 +0000 (UTC)
	(envelope-from developer@lorenzosalvadore.it)
Authentication-Results: mx1.freebsd.org;
	none
Date: Wed, 01 Feb 2023 09:25:08 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lorenzosalvadore.it;
	s=protonmail; t=1675243510; x=1675502710;
	bh=hI3byOmWNuxfKCMKIEaM5vApW00czQzp8AKzdRsSTuU=;
	h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References:
	 Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
	 Message-ID:BIMI-Selector;
	b=IyD3lYHEtSd9Xm3zeRX3NFBKZiuxF6KvXc/KXzNd8xmfKlWQyjfuJMpWEe/wMIcFD
	 W23ix5q/q8gQQKomRNOG3zOPngAYbxarmdfou3M54/kIL4CUdNt70p4RWmpAw9r9qU
	 nxJy5qNjeQStA7jPJ40oZ4uOnuiGIz4eh868IjfMJjLp0i6J2WQftb3hnUtBos+aqw
	 D173vwlTpNU6ZD7+uNCGCSuqRHDLTrsWwl9Pg5gqSQN3OvBdjzbSRSvvAVq/TuxvN9
	 Lbis6ssTHjdrCmrG6nsqEBD7gA/fpAEt3+7VO3yJ9159nV29u0d7ciaPdvsLZmgPZj
	 moG6AhfZk2zVA==
To: User Ngor <ihor@antonovs.family>
From: Lorenzo Salvadore <developer@lorenzosalvadore.it>
Cc: freebsd-wireless@freebsd.org
Subject: Re: 5GhZ on AX201?
Message-ID: <Z2NPXR5lX76VEJqIJu6cVBcXnUAjJoua7EYxMx8ezQm3WfaBf4xrUmH-rXA_ZoAypE720xNOH3fHmBHfpayGHHrZ2ehnwI0DBNN0YOjjRiU=@lorenzosalvadore.it>
In-Reply-To: <c531bb85-5745-c42d-996e-4114d872ec2b@antonovs.family>
References: <c531bb85-5745-c42d-996e-4114d872ec2b@antonovs.family>
Feedback-ID: 53711648:user:proton
List-Id: Discussions <freebsd-wireless.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-wireless
List-Help: <mailto:wireless+help@freebsd.org>
List-Post: <mailto:wireless@freebsd.org>
List-Subscribe: <mailto:wireless+subscribe@freebsd.org>
List-Unsubscribe: <mailto:wireless+unsubscribe@freebsd.org>
Sender: owner-freebsd-wireless@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Rspamd-Queue-Id: 4P6GjN18p5z3ldr
X-Spamd-Bar: ----
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-ThisMailContainsUnwantedMimeParts: N

------- Original Message -------
On Wednesday, February 1st, 2023 at 5:27 AM, User Ngor <ihor@antonovs.famil=
y> wrote:


>
>
> Hello list,
>
> Is 5GhZ wifi expected to work in my situation? 2.4 GHz works pretty much
> out of the box (only necessary rc.conf configuration)
>
> FreeBSD-14 Current, built yesterday.
> ThinkPad X1 Yoga Gen6
> Chip: Intel AX201 (vendor=3D0x8086 device=3D0xa0f0)
>
> I have 2 wireless networks at home 2.4 and 5 GhZ respectively
> Home-2: SSID for 2.4 GHz b/g/n
> Home-5: SSID for 5 GHz a/n/ac
>
> Other devices (smartphones, OSX and Linux laptops work fine on 5)
>
>
> wpa_supplicant.conf (good):
>
> network=3D{
> ssid=3D"Home-2"
> psk=3D"xxxx"
> }
>
>
>
> wpa_supplicant.conf (bad):
>
> network=3D{
> ssid=3D"Home-5"
> psk=3D"xxxx"
> }
>
> Changing SSID to 5GHz results in no wifi.
> `service netif restart` finishes, with wlan0 device with no carrier.
> Is there a way to make 5GHz work in my situation or is it not yet support=
ed?

I am using 5 GHz right now on my Intel AX201 (vendor=3D0x8086 device=3D0xa0=
f0).
FreeBSD-14 Current (2aaccae35db4) on Asus X515.

I did had issues once, yesterday. But it was an exeception and it probably
was not due to the FreeBSD driver.

Cheers,

Lorenzo Salvadore