From nobody Thu Oct 05 15:59:28 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 4S1bq618Stz4vsnF for ; Thu, 5 Oct 2023 15:59:46 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4S1bq52gQKz3Pl9 for ; Thu, 5 Oct 2023 15:59:45 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=a9e3hJCK; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::b2f as permitted sender) smtp.mailfrom=kob6558@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-d8afe543712so1297800276.0 for ; Thu, 05 Oct 2023 08:59:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696521584; x=1697126384; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=soqIaVQlqY1q5YWe6iQsmb8UU/bHlfZXxxyCJcvCHTw=; b=a9e3hJCKsmaknx/YCNTKvFuKamu4DKET+Xa721r088lXU6chgUHo4uavHIo23RUlNM X1Na5xYyKmNAVVGPp3ykoARQGPKX73xuQGU6ReQ3y5srFd2B9GVC3J+FlX/flxvs2qQ1 WevjZPW2Y2gBIAXRO4GJAMlNtoie8sRNiuwrMJOGZFSWJoWWPORpXpCCO+mYoHfmNaAV RfhG5OArg4jxGoYTqAbzqrIWUHVaCnyF17ex++uML8Yrwn/3DPX7OkwWlljHY7+0VHjX Rpdnx2lo3eZleNLyYcg5ZfMY4/3HKebqwQi4bF3nqmQPF+Wu2IXq2KADrLclrkkfmJ2g KUuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696521584; x=1697126384; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=soqIaVQlqY1q5YWe6iQsmb8UU/bHlfZXxxyCJcvCHTw=; b=JCBmWNYo75dO3vMxjrlFkAJlLGdYKUwySrI1s8WRFCxgeDPLMrcuCUcTDgMiPRPgky YgHU7XfKzxNFfx2rCofngrWsW1iSMCl3Tq7/8jdalfDhostb0WGeAScn28rOJKbfM8oD mjlUcT+kaJQtj1BB3u8/yIXzKHI+d9Ys72qqvqq6yR0ZVz4H+y+OmaHOakiATacfF5vn nD4pkPi1Gm3lFbKbNlkvvPeejNWQWTb4s2MYUJqyG7RmUHcYhqjFK1aHHy6nh2OCO64K 7+vxaJBCNVGEnjm4giu4KNan5v5eMRFOq0LCn0xAmkTu91vJRMeeNHi4BIM6YPsRNh5b btKw== X-Gm-Message-State: AOJu0YyfYf1XJ8tOar8YT80aSvKuoHEv9yeJLIqHrQFOiho6bczrYXB3 zBiOo7uzQAhE3BVVdGEo1sj8DaXrO5nRXbpcv2LoJv5S X-Google-Smtp-Source: AGHT+IHs+wH2z5aqwkEqD+GwSeILyjKwSXGqMQLGHPPC1No8+5DadwMBbZGBYnw0DHsWW8ZLWJ+VrpKo9R7C5lnXVWI= X-Received: by 2002:a25:ac07:0:b0:d7f:d512:2663 with SMTP id w7-20020a25ac07000000b00d7fd5122663mr5650596ybi.54.1696521584491; Thu, 05 Oct 2023 08:59:44 -0700 (PDT) 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 From: Kevin Oberman Date: Thu, 5 Oct 2023 08:59:28 -0700 Message-ID: Subject: Issues associating with "unusual" networks To: FreeBSD Wireless Content-Type: multipart/alternative; boundary="00000000000065c4500606fa361e" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.70 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2f:from]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-wireless@freebsd.org] X-Rspamd-Queue-Id: 4S1bq52gQKz3Pl9 --00000000000065c4500606fa361e Content-Type: text/plain; charset="UTF-8" I am currently away from home running on my ThinkPad laptop. I have been unable to connect to the hotel guest network with errors similar to the issue of connecting to virtual APs that was fixed in the wpa_supplicant about a year ago. Oddly, I am also having issues connecting to my phone hotspot when in the hotel. After a few "service netif restart wlan0" operations, I can usually connect, but I suspect that the issue is that "list aps" shows about 80 BSSIDs and, when the connection failed, my phone was not one of them. The hotel mesh SSID accounted for almost all, though few others are always included. I suspect that this is pointing to the problem, although my familiarity with how the driver determines the BSSIDs to maintain is near zero. Once associated with my phone, things just work as long as I keep the hotspot and my laptop active. I would like to know if there's any data I might collect while I am here that should help troubleshoot this. I have about 24 hours until I check out. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --00000000000065c4500606fa361e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I am currently away from home running on my Thin= kPad laptop. I have been unable to connect to the hotel guest network with = errors similar to the issue of connecting to virtual APs that was fixed in = the wpa_supplicant about a year ago. Oddly, I am also having issues connect= ing to my phone hotspot when in the hotel.

After a few "service netif restart wlan0" operations, I can us= ually connect, but I suspect that the issue is that "list aps" sh= ows about 80 BSSIDs and, when the connection failed, my phone was not one o= f them. The hotel mesh SSID accounted for almost all, though few others are= always included. I suspect that this is pointing to the problem, although = my familiarity with how the driver determines the BSSIDs to maintain is nea= r zero.

Once associated with my phone, t= hings just work as long as I keep the hotspot and my laptop active.

I would like to know if there's any data I = might collect while I am here that should help troubleshoot this. I have ab= out 24 hours until I check out.
--
Kevin Oberman, Part time kid herder and retired N= etwork Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA7= 8E3B78C1694B318AB39EF1B055683
--00000000000065c4500606fa361e--