[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#930271: marked as done (iw: cannot scan if two cells on 2.4Ghz and 5Gz have same SSID)

Your message dated Mon, 29 Sep 2025 18:08:50 +0200
with message-id <e45c9f601f3ed437639ded39fc2e85773ff2b1d2.camel@decadent.org.uk>
and subject line Re: Bug#930271: iw: cannot scan if two cells on 2.4Ghz and 5Gz have same SSID
has caused the Debian Bug report #930271,
regarding iw: cannot scan if two cells on 2.4Ghz and 5Gz have same SSID
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
930271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930271
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: iw
Version: 5.0.1-1
Severity: normal

Dear Maintainer,

   * What are you trying to do?

I'm trying to scan networks in a place where two cells on 2.4Ghz and 5Gz have
the same SSID.

   * What was the outcome of this action?

The scan returns only one cell (not the one with double frequency, a third
one), and subsequent scan return nothing. It seems that the scan itself somehow
crashes.

   * What outcome did you expect instead?

The scan would return all cells.

   * What's a potential explanation?

Somewhere in the stack, there is a confusion regarding having the same SSID in
both the 2.4Ghz and 5Gz frequency range.

Best regards,

--Martin



-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iw depends on:
ii  libc6             2.28-10
ii  libnl-3-200       3.4.0-1
ii  libnl-genl-3-200  3.4.0-1

Versions of packages iw recommends:
ii  crda  3.18-1

iw suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Paride Legovini wrote:
> Martin Monperrus wrote on 14/06/2019:
> > Hi Paride,
> > 
> > Thanks for your answer. Would you recommend to report it on
> > https://bugzilla.kernel.org/?
> 
> Hi Martin,
> 
> I'd say the bug belongs there, but keep in mind that for your report to
> be considered I think you'll be asked to compile the latest version of
> the vanilla kernel.
> 
> IF your WiFi adapter needs a firmware it may be worth trying to use the
> latest version released by the manufacturer.
> 
> Paride

On Fri, 21 Jun 2019 05:06:40 -0700 Martin Monperrus
<martin.monperrus@gnieh.org> wrote:
> Thanks Paride for the advice.

There was no further update, and I didn't find any bug report from
Martin at bugzilla.kernel.org.  So I don't think there is any point
keeping this report open.

Feel free to reopen if this bug can still be reproduced in a supported
Debian version, but please:

- Also test with a current kernel and firmware versions (and say exactly
which versions those are)
- Say which driver and device is being used (information from
"lspci -vnn" or "lsusb -v")

Ben.

-- 
Ben Hutchings
Horngren's Observation:
              Among economists, the real world is often a special case.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: