LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 10-11-2014, 08:32 PM   #1
MisterBark
Member
 
Registered: Jul 2012
Location: Republic of Krakozhia
Distribution: Slackware & Zenwalk core + compile
Posts: 104

Rep: Reputation: 6
Question NetworkManager can scan but iwlist gives [Interface doesn't support scanning]


Hi!

Everything is in the title.

NetworkManager + nm-applet works fine, but when I kill them and want to handle things manually with ifconfig & iwlist, the interface cannot scan.
I already tried to make down, then up, with ifconfig, which works, the interface is up but still doesn't scan.

Code:
# ps auxm | grep -i network
(nothing)

# ps auxm | grep -i nm
(nothing)

# ps auxm | grep -i dhcp
(nothing)

# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.11  netmask 255.255.255.0  broadcast 192.168.10.255
        ether 00:25:90:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 504  bytes 43142 (42.1 KiB)
        RX errors 0  dropped 22  overruns 0  frame 0
        TX packets 1350  bytes 1986168 (1.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xd3600000-d3620000  

eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.200.1  netmask 255.255.255.0  broadcast 192.168.200.255
        ether 68:05:ca:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2  bytes 357 (357.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xd3120000-d3140000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 0  (Local Loopback)
        RX packets 2743  bytes 211876 (206.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2743  bytes 211876 (206.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:c0:ca:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 186254  bytes 166903582 (159.1 MiB)
        RX errors 0  dropped 55  overruns 0  frame 0
        TX packets 173028  bytes 26153212 (24.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

# iwlist wlan0 s
wlan0     Interface doesn't support scanning.

# lsmod | grep -i rtl
rtl8187                49229  0 
eeprom_93cx6            1929  1 rtl8187
mac80211              261306  1 rtl8187
cfg80211              165192  2 mac80211,rtl8187

# lsusb
...
Bus 002 Device 008: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
How can a driver be loaded, the interface be fine in ifconfig but not in iwlist?
Any idea is welcome!

Thank you

Last edited by MisterBark; 10-11-2014 at 08:33 PM.
 
Old 10-11-2014, 08:44 PM   #2
prushik
Member
 
Registered: Mar 2009
Location: Pennsylvania
Distribution: gentoo
Posts: 372

Rep: Reputation: 29
This happens to me too. I don't understand it yet, but I also haven't tried hard to figure it out. Anyways, I found that using iw instead of iwconfig works. iw seems to be a nicer tool overall anyway, so I don't worry about it much.
 
Old 10-11-2014, 08:53 PM   #3
MisterBark
Member
 
Registered: Jul 2012
Location: Republic of Krakozhia
Distribution: Slackware & Zenwalk core + compile
Posts: 104

Original Poster
Rep: Reputation: 6
Ah!!!
That's right iw works!
I'm very curious about that... how is this possible?
 
Old 05-09-2016, 03:09 AM   #4
kaz2100
Senior Member
 
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: SlackWare > Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy .. bullseye bookworm
Posts: 1,834

Rep: Reputation: 108Reputation: 108
I ran into same problem.

Yes, iw works and iwlist chokes.

Another interesting observation is that
with debian repo kernel, no symptom.

With my custom kernel, things go wrong.

cheers

++ added on edit.
Most probably
Code:
CONFIG_WEXT
is the one.

Last edited by kaz2100; 05-10-2016 at 03:26 AM.
 
Old 05-09-2016, 03:58 AM   #5
tshikose
Member
 
Registered: Apr 2010
Location: Kinshasa, Democratic Republic of Congo
Distribution: RHEL, Fedora, CentOS
Posts: 525

Rep: Reputation: 95
Hi,

My recommendation would be to use new tools (such as NetworkManager, nmcli, ip, ss...), and stop using old ones (such as network, ifconfig, netstat...).
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] interface doesn't support scanning: network is down Broadcom BCM4318 trishface Linux - Newbie 7 09-17-2011 10:54 AM
"iwlist wlan0 scanning" doesn't see my AP. darkmaster977 Linux - Wireless Networking 5 11-22-2009 07:04 AM
iwlist error: Interface doesn't support scanning chr15t0 Linux - Wireless Networking 3 02-09-2006 07:36 PM
Inteface doesn't support scanning NTolerance Linux - Wireless Networking 5 02-09-2006 07:30 PM
iwlist scan: interface doesn't support scanning. tdb Linux - Wireless Networking 3 01-14-2006 07:10 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 05:53 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration