From owner-freebsd-wireless@freebsd.org Thu Sep 19 22:04:07 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C02AE12FABF; Thu, 19 Sep 2019 22:04:07 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z9qB4NR1z4LNY; Thu, 19 Sep 2019 22:04:06 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id B4WuivIsHIhW9B4Wvib1WB; Thu, 19 Sep 2019 16:04:03 -0600 X-Authority-Analysis: v=2.3 cv=FcFJO626 c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=J70Eh1EUuV4A:10 a=pGLkceISAAAA:8 a=9bHR7MVLAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=f7zcvYf-h5ur5gTkv84A:9 a=_m-7wGuwNc3mVfFE:21 a=2YSe1PtFNj0BYo3z:21 a=QEXdDO2ut3YA:10 a=I7KxNEAtLM9g1UmuDjRu:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from 5CG5030TVK-N.esitwifi.local (S0106788a207e2972.gv.shawcable.net [70.66.154.233]) by spqr.komquats.com (Postfix) with ESMTPSA id 25F4D16E; Thu, 19 Sep 2019 15:03:59 -0700 (PDT) Date: Thu, 19 Sep 2019 15:03:35 -0700 In-Reply-To: References: <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD.org> <6985.1568738188@critter.freebsd.dk> <20190919122804.GA80037@tom-desk.erg.abdn.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: wlan can't discover known networks after relocating To: freebsd-current@freebsd.org, Adrian Chadd , "freebsd-wireless@freebsd.org" CC: Tom Jones , Poul-Henning Kamp , FreeBSD Current , Johannes Lundberg From: Cy Schubert Message-ID: X-CMAE-Envelope: MS4wfJGC0FZ51Tg7c36DeNaHMdHKDHHWcTMv9weqzv1sKu2XejnboSWP/OwCwZ2H0ArYfurGgMTFeOq/k6juKT7fCeigKdcW4lE4gJ9JViWSISKPbPVHnDWp ZG28Qw063Bqa+dARFbUYcZ89wtTyttDh80ZC575RHSZEm9U4ALgJpO6VPHtWTgSGgxKBsgJml/xLQhDAMpooErZOME/Y3UdO0XsjZHsvvftfAqItep0AyBoy rPF1dR5B8qghf+GcXP7B95u6q+6OA1R0PlRHvhycAx+dh5XHx+0j0Wp2TRzBPfppn+q+EqeU2UDiBewbtpyDkA== X-Rspamd-Queue-Id: 46Z9qB4NR1z4LNY X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 64.59.136.138) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-2.92 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-2.32)[ip: (-6.02), ipnet: 64.59.128.0/20(-3.08), asn: 6327(-2.40), country: CA(-0.09)]; RCVD_IN_DNSWL_NONE(0.00)[138.136.59.64.list.dnswl.org : 127.0.5.0]; RCPT_COUNT_SEVEN(0.00)[7]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; SUSPICIOUS_RECIPS(1.50)[]; RECEIVED_SPAMHAUS_PBL(0.00)[233.154.66.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11, 17.125.67.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Sep 2019 22:04:07 -0000 On September 19, 2019 8:20:07 AM PDT, Adrian Chadd wrote: >Roaming is done in wpa_supplicant when it's running=2EThat's where the >smarts >need to be=2E :( > > > >-adrian > > >On Thu, 19 Sep 2019 at 05:44, Bjoern A=2E Zeeb > >wrote: > >> On 19 Sep 2019, at 12:28, Tom Jones wrote: >> >> Hi, >> >> freebsd-wireless might be a better list for all this =2E=2E >> >> >> > On Tue, Sep 17, 2019 at 04:36:28PM +0000, Poul-Henning Kamp wrote: >> >> -------- >> >> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f477@FreeBSD=2Eorg>, >> >> Johannes Lundber >> >> g writes: >> >> >> >>> For a long time now I have had this problem with iwm and wlan0=2E >> >>> Whenever >> >>> I move between work and home it won't reconnect automatically and >I >> >>> have >> >>> to do wlan0 scan manually for it to pick up the different >network=2E >> >> >> >> I suffer from the dreaded "reason=3D0" when I move inside my house: >> >> >> >> > scan >> >> OK >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 >(SSID=3D'Palombia' >> >> freq=3D2452 MHz) >> >> <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:3d:a2:e9 reason=3D0 >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> <3>Trying to associate with 6c:3b:6b:ab:ce:d4 >(SSID=3D'Palombia' >> >> freq=3D2412 MHz) >> >> <3>Associated with 6c:3b:6b:ab:ce:d4 >> >> >> >> a2:e9 is the loudest AP here in my office, but my I have been in >the >> >> other end of the house iwn consistently fails to associate with it >> >> and >> >> and keeps picking the weaker AP in the far end=2E >> >> >> >> Eventually (hours!) it disconnects from the weaker ap, also with >> >> "reason=3D0" and gets it right: >> >> >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:ab:ce:d4 >[GTK=3DCCMP] >> >> <3>CTRL-EVENT-DISCONNECTED bssid=3D6c:3b:6b:ab:ce:d4 reason=3D0 >> >> <3>CTRL-EVENT-SCAN-RESULTS >> >> <3>Trying to associate with 6c:3b:6b:3d:a2:e9 >(SSID=3D'Palombia' >> >> freq=3D2452 MHz) >> >> <3>Associated with 6c:3b:6b:3d:a2:e9 >> >> <3>WPA: Key negotiation completed with 6c:3b:6b:3d:a2:e9 >[PTK=3DCCMP >> >> GTK=3DCCMP] >> >> <3>CTRL-EVENT-CONNECTED - Connection to 6c:3b:6b:3d:a2:e9 >> completed >> >> [id=3D3 id_str=3D] >> >> <3>WPA: Group rekeying completed with 6c:3b:6b:3d:a2:e9 >[GTK=3DCCMP] >> >> >> >> And yes, working roaming would be nice too=2E=2E=2E >> > >> > I have the problem that when roaming networks become disabled >> > >> > $ wpa_cli >> > Selected interface 'wlan0' >> > >> > Interactive mode >> > >> > > list_networks >> > network id / ssid / bssid / flags >> > 0 network1 any [CURRENT] >> > 1 network2 any [DISABLED] >> > 2 network3 any [DISABLED] >> > 3 network4 any [DISABLED] >> > 4 network5 any [DISABLED] >> > Selected interface 'wlan0' >> > >> > >> > I address this by doing network_enable x in wpa_cli and it all >comes >> > back=2E I asked Adrian about this in the past, but it needs some >> > debugging >> > to pin down=2E >> >> >> Is this iwm(4) as well in your case or another card? >> >> /bz >> _______________________________________________ >> freebsd-wireless@freebsd=2Eorg mailing list >> https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >"freebsd-wireless-unsubscribe@freebsd=2Eorg >> " >> >_______________________________________________ >freebsd-current@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscribe@freebsd=2Eorg" With wpa_supplicant running roaming is set to manual=2E Bgscan should be e= nabled=2E =20 At home we have two n (and 2 g) wifi networks=2E When powering off one ap = it connects to the other (in addition to using lagg to failover from ethern= et to wifi and back)=2E Your wpa_supplicant should contain each ssid you intend to use=2E A wildca= rd can be used for open networks=2E It's a while since I've tested this functionality but I can test again whe= n I get home tonight=2E=20 --=20 Pardon the typos and autocorrect, small keyboard in use=2E Cheers, Cy Schubert FreeBSD UNIX: Web: http://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E