From nobody Mon Jul 10 00:46:45 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 4Qzlgy0kXmz2tsK0 for ; Mon, 10 Jul 2023 00:46:54 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Qzlgx3FFjz43qr for ; Mon, 10 Jul 2023 00:46:53 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; none Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id C1B018D4A142; Mon, 10 Jul 2023 00:46:49 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id A91E05C3A82F; Mon, 10 Jul 2023 00:46:48 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id 2YNN4Tom6_HX; Mon, 10 Jul 2023 00:46:47 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (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) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 2864C5C3A82E; Mon, 10 Jul 2023 00:46:46 +0000 (UTC) Date: Mon, 10 Jul 2023 00:46:45 +0000 (UTC) From: "Bjoern A. Zeeb" To: FreeBSD User cc: freebsd-wireless Subject: Re: wpa_supplicant: lagg0 not working anymore (if_iwm/if_iwlwifi) In-Reply-To: <20230709133558.45d1a39b@thor.intern.walstatt.dynvpn.de> Message-ID: <481nrq96-315o-p931-838n-0p36s57s510s@yvfgf.mnoonqbm.arg> References: <20230709133558.45d1a39b@thor.intern.walstatt.dynvpn.de> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Rspamd-Queue-Id: 4Qzlgx3FFjz43qr X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Sun, 9 Jul 2023, FreeBSD User wrote: > Hello, > > running 13-STABLE (13.2-STABLE #29 stable/13-n255792-d295e418ae7e: Sun Jul 9 10:08:25 CEST > 2023 amd64) on a Lenovo T560 with Intel i8260 WiFi chipset, combining the LAN (if_em) and WiFi > (if_iwm) via if_lagg for convenient switching between LAN and WiFi APs of our departments, > worked fine until recently. > > Althoug running wlan0 with several debug options, I can't fathom what is going wrong, there > seems to be an authentication problem. If lagg stopped working with iwm (what's your last good version for that?) then this is likely an issue outside of wireless as "legacy" wireless (iwm or net80211) haven't changed much if at all in the last months. Networking on the other hand had a reasonable amount of changes. Would be interesting for someone to use two ethernet and see if it works there? Probably asking on freebsd-net as a start would be good. The logs below are hard to read given they are wrapped but it seems there's little information on lagg in there? Can you explain the actual problem you encounter a bit more? Does switching from ethernet to wifi work? Does switching from wifi to ethernet work? In each case what happens to packets, networking, lagg, wpa, wifi state? What do the link states of the underlying interfaces say (in ifconfig)? /bz -- Bjoern A. Zeeb r15:7