From nobody Fri Sep 24 10:59:02 2021 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 70FEE17CEADE for ; Fri, 24 Sep 2021 10:59:14 +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" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HG8DK3WZHz4hqc for ; Fri, 24 Sep 2021 10:59:13 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 6E1D58D4A20E; Fri, 24 Sep 2021 10:59:06 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id EF9ABE707B5; Fri, 24 Sep 2021 10:59:05 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id beiqNmNoekL1; Fri, 24 Sep 2021 10:59:03 +0000 (UTC) Received: from nv.sbone.de (nv.sbone.de [IPv6:fde9:577b:c1a9:31::2013:138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 74F46E707B3; Fri, 24 Sep 2021 10:59:03 +0000 (UTC) Date: Fri, 24 Sep 2021 10:59:02 +0000 (UTC) From: "Bjoern A. Zeeb" To: freebsd@walstatt-de.de cc: freebsd-wireless@freebsd.org Subject: Re: iwm: loosing connection to AP very often In-Reply-To: <20210912112924.088e6b91@hermann.fritz.box> Message-ID: References: <20210912112924.088e6b91@hermann.fritz.box> 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: 4HG8DK3WZHz4hqc X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 195.201.62.131 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[zabbadoz.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; RCVD_TLS_LAST(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sun, 12 Sep 2021, freebsd@walstatt-de.de wrote: Hallo, > I observe a very negative and unpleasant development and behaviour with Intel iwm driver > in FreeBSD recently. Using this WiFi adapter in a Lenovo E540 (technical specs see below, > output of pciconf -lvbc), this adapter ran stable with FreeBSD 12-CURRENT some time ago, > until I moved to 13-STABLE on that notebook. > > I use a "typical" wlan0/re0/lagg0 configuration on that notebook, since I have to switch > very often between WiFi and wired LAN. The FreeBSD 13-STABLE (most recent incarnation) is > configured dual stack IPv4 and IPv6. > > The overall observation is that the WiFi connection is, no matter what kind of AP I used > to be connected to, that the connection is highly unstable! While ifconfig still reports > attached IPs (both IPv4 and IPv6) on lagg0 and allegedly beeing associated via wlan0 to > the AP, there is no connection any more and the only salvation is service netif restart > or bringin down and up IF and all associated services. This problem gets worse, the more > the WiFi is crowded with other stations, but even in sparsely populated WiFi areas the > loose of connection/association is only a matter of time, sometimes the death of the > connection comes rather quickly. > > I can only report my observations. I used to use the very same notebook with FreeBSD > CURRENT and lately with 13-STABLE with FreeBSD since I purchased it in 2014 and used the > same wlan0/re0/lagg0 configuration I use these days, but with I never faced an > instability like the reported with 12-STABLE I face with 13-STABLE. The problem is > present almost 1 1/2 years for now and even with newer commits to WiFi in FreeBSD I did > not see a mitigation. Without much more data this is hard to diagnose remotely. I'd suggest (if you are okay with the extra logging) to enable wlandebug such as: wlandebug_wlan0="+state +crypto +node +auth +assoc +dot1xsm +wpa" in rc.conf. See wlandebug(8) for more information. That might give you a hint maybe of what is going wrong. > I also realized that iwm() is limited by its FreeBSD driver to 802.11b and 802.11g, and 11a. > although it claims to be an 802.11ac driver. Is this about to change in a measurable > timeframe for a human lifetime? That is underway with the iwlwifi efforts. See the posting with the reference to the wiki earlier this month on this list: https://lists.freebsd.org/archives/freebsd-wireless/2021-September/000068.html Fair warnings: It's probably not quite fully ready/stable enough for your roaming usage but if you are willing to test you are more than welcome. I am also not aware anyone having tested iwlwifi with a 7000 series card yet and I don't happen to have one either to do so. Could be an extra bumpy ride. > [...] > iwm0@pci0:5:0:0: class=0x028000 rev=0x73 hdr=0x00 vendor=0x8086 device=0x08b2 > subvendor=0x8086 subdevice=0x4262 vendor = 'Intel Corporation' > device = 'Wireless 7260' >From what I can see this is a very early 11n-only device so 11ac won't help with it; but 11n would hopefully help you a bit. -- Bjoern A. Zeeb r15:7