Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
User-Agent: Cyrus-JMAP/3.3.0-dev0-504-g204cd6f-fm-20200527.002-g204cd6f2
Mime-Version: 1.0
Message-Id: <f78191c6-3093-4d97-a959-068dce1da552@www.fastmail.com>
In-Reply-To: <7406af4a9e852d99735e1b1af63deed2f0c5d703.camel@sipsolutions.net>
References: <afef8a7d-053e-4aaa-ace7-d320c32e8b7c@www.fastmail.com>
 <(sfid-20200528_174911_413757_32DBA783)>
 <a185a4283c1230965b520de52737427c91af9c22.camel@sipsolutions.net>
 <99c4ece3-15ca-42cb-aa09-c86d466d6429@www.fastmail.com>
 <7406af4a9e852d99735e1b1af63deed2f0c5d703.camel@sipsolutions.net>
Date:   Thu, 28 May 2020 14:57:54 -0400
From:   "Bruno Dantas" <wireless@dantas.airpost.net>
To:     "Johannes Berg" <johannes@sipsolutions.net>,
        linux-wireless@vger.kernel.org
Subject: Re: iwlist scanning: how to exclude old scan results from output?
Content-Type: text/plain
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

> Does it go away if you wait long enough for the "last seen" to go above
> 30 seconds (30000ms)? You should use "iw wlan0 scan dump" (no need for
> sudo, and don't scan again) to check.
> 
> Because if not, then there's a bug in the references, and the entry is
> just being kept alive by ... something. Did you previously connect to
> it? Does it also happen if you never connect? Then I guess we'll need to
> know what the kernel version is too. :)

Yes, it goes way if I wait 30 seconds. Whether I had connected to the hotspot or not makes no difference. Kernel version is 5.4.3.

I thought discovering *currently-available* hotspots would be a common need. I'm a bit surprised that getting this information is tricky.

Like I said, reloading the wireless interface's kernel module does the trick. I was just hoping that there'd be a more elegant solution. Thanks for the help, anyway.