Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <3dc55975efed3f48625d3741408d0242d992e1b4.camel@sipsolutions.net>
Subject: Re: Bug in iw ... scan  output for Ad-Hoc (IBSS) output
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Bill Unruh <unruh@physics.ubc.ca>, linux-wireless@vger.kernel.org
Date:   Fri, 26 Jul 2019 09:18:42 +0200
In-Reply-To: <alpine.LMD.2.03.1907251251170.5032@physics.ubc.ca> (sfid-20190725_221110_893806_9B5DB0EE)
References: <alpine.LMD.2.03.1907251251170.5032@physics.ubc.ca>
         (sfid-20190725_221110_893806_9B5DB0EE)
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On Thu, 2019-07-25 at 13:04 -0700, Bill Unruh wrote:
> The output of iw .. scan output for Ad-Hoc (IBSS) does not have a carriage
> return running it into the next access point output
> 
> 
> BSS f6:63:9f:d1:f9:17(on wlp58s0)
>          TSF: 0 usec (0d, 00:00:00)
>          freq: 2437
>          beacon interval: 100 TUs
>          capability: IBSS ShortPreamble (0x0022)
>          signal: -69.00 dBm
>          last seen: 6040 ms ago
>          Information elements from Probe Response frame:
>          SSID: hpsetup
>          Supported rates: 1.0* 2.0* 5.5* 11.0*
>          DS Parameter set: channel 6
>          IBSS ATIM window: 0 TUsBSS 34:31:c4:39:63:ef(on wlp58s0)
> 
> Note the last line-- that is the BSS of the next access point output of iw

Thanks for the report, pushed a fix.

johannes