From nobody Mon Jul 10 19:39:05 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 4R0Dpz1yKbz2thYr for ; Mon, 10 Jul 2023 19:39:39 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp5.goneo.de [IPv6:2001:1640:5::8:30]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4R0Dpy750rz4D0T for ; Mon, 10 Jul 2023 19:39:38 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; none Received: from hub2.goneo.de (hub2.goneo.de [85.220.129.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id AC9F010A32CA; Mon, 10 Jul 2023 21:39:34 +0200 (CEST) Received: from hub2.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPS id 1EF92105C63A; Mon, 10 Jul 2023 21:39:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1689017973; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=kNG/QoA2HOegq5aapfwbh6uc/sh7BpG4rSkr5VxJhBA=; b=PfAIBt8EujGwZVnH4q1aNZkX2A831GNMEtRHMrjQ9ln5hbiOLCUqL8gzsUpygAgucwHXFw n1jb5kPXdXkCZcBpUkLQgt9lk/ti00O5VZqnJZa3M0x7Hct89ri2tGhkE24m5chn4EsWcj 3vnuqqRgUUEeylthscZ99dFBc50ggqnYWLEWSU4s92xqPLp9MIgPsbXjSaG8U9Sp5pFD7B 12+Bn8gC4TGMzAJaTy8myXTCAhsA3iTOuLxVQucuUb4UOa5dlTiWEOmIb0qhBF83KDfY87 arz07/q6qblgI5xWuDzWuIYwW5oZd9tcXr2tScgNdrbQQxeCyADyoo9L2I52cw== Received: from thor.intern.walstatt.dynvpn.de (dynamic-077-191-145-176.77.191.pool.telefonica.de [77.191.145.176]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hub2.goneo.de (Postfix) with ESMTPSA id D6642105C65A; Mon, 10 Jul 2023 21:39:32 +0200 (CEST) Date: Mon, 10 Jul 2023 21:39:05 +0200 From: FreeBSD User To: "Bjoern A. Zeeb" Cc: freebsd-wireless Subject: Re: wpa_supplicant: lagg0 not working anymore (if_iwm/if_iwlwifi) Message-ID: <20230710213932.67cbeb1d@thor.intern.walstatt.dynvpn.de> In-Reply-To: <481nrq96-315o-p931-838n-0p36s57s510s@yvfgf.mnoonqbm.arg> References: <20230709133558.45d1a39b@thor.intern.walstatt.dynvpn.de> <481nrq96-315o-p931-838n-0p36s57s510s@yvfgf.mnoonqbm.arg> Organization: walstatt-de.de 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 Content-Transfer-Encoding: 7bit X-Rspamd-UID: 8a5804 X-Rspamd-UID: dd0893 X-Rspamd-Queue-Id: 4R0Dpy750rz4D0T X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Am Mon, 10 Jul 2023 00:46:45 +0000 (UTC) "Bjoern A. Zeeb" schrieb: > 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. Hello, > > 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? I use a "classical" straight forward failover configuration between NIC (em0) and WiFi (iwm0 or, now, iwlwifi0). Last time I changed something on that config lies in the past around a year for now when trying if_iwlwifi on the T560 Laptop with i8260 WiFi chipset, which didn't work well with iwlwifi that time. I do mention this particular fact since I update the software (13-STABLE) from time to time to be prepared for lab-work when needed, so a couple of weeks ago I realized that WiFi wasn't working anymore as expected (still the mentioned failover/lagg config). As mentioned initially, configuring each interface, WiFi (no matter whether iwm0 or iwlwifi0) works as expected. With the failover config it fails. I found the culprit! In my former config, the WiFi was given the MAC address of the NIC via "config_args_wlan0="ether MAC-ADDRESS ...." or ifconfig_wlan0="ether MAC-ADDRESS-OF-NIC ...." (latter one seems correct, since it seems omitting the ether part assigns the NICs MAC address automatically to the WiFi, so I thing using config_args_wlan0="" is the worng place to do so...). Now I simply swapped this relation by giving the NIC the MAC-of-the-WiFi via "ether ..." - and surprise, surprise, it works! I do not know whether this is intentionally, the opposite around worked for a while since, as mentioned, I didn't change the config for almost a year and used the Notebook in a campaign with both WiFi and NIC via lagg/failover (my only metric here ...). The problem is with if_iwm and if_iwlwifi the same way, so I guess it might be something strange with if_lagg handling the ether? Kind regards, Oliver > > 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 > -- O. Hartmann