[Solved]How do i know that i use nl80211 or wext?

sorkaud · 2017-06-13 10:37:25

Hello

I am a light user of arch linux on my laptop

In the past, i uses only one wifi with "wifi-menu ; netctl".

But, recently i move around and i have to use "wpa2-enterprise ?" wifi (i'm not sure but it needs my id and passwd of my univ account)

So, i learned about wifi configuration on wiki page.

And i realize that i used automatic network control and have to study manual mathod "wpa-supplicant"

when i do

 sudo wpa_supplicant -i wlp2s0 -c /etc/wpa_supplicant/example.conf 
sudo wpa_cli

then

wpa_cli v2.6
Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.


Selected interface 'p2p-dev-wlp2s0'

Interactive mode

But the commnad scan does not work (i mean it is very slow and it work seldom)

scan
ok
scan_results
bssid / frequency / signal level / flags / ssid

like above

but when i give a option -D wext
then

wpa_cli v2.6
Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.


Selected interface 'wlp2s0'

Interactive mode

there is no p2p-dev and it work well as i follow steps (and dhcpcd)

But i don't think that my machine does not support nl80211 because my netctl profile does not have WPAdriver option (default will be nl80211,wext am i right?)

and i think the problem is that wpa_supplicant option -i does not work

whenever i give -D nl80211 then it gives me p2p-dev-wlp2s0, not wlp2s0

so i want correct this

or maybe i'm wrong about my maching (i thought it support nl80211 but in fact, it does not)

The possible explanation will be "netctl automatically select wext"

So im in confuse right now is there anyway i can figure out my status and eventually success to use WPA2-enterprise?

by the way

[archie@arch ~]$ iw dev
phy#0
	Unnamed/non-netdev interface
		wdev 0x9
		addr 34:e6:ad:51:6a:3b
		type P2P-device
		txpower 0.00 dBm
	Interface wlp2s0
		ifindex 3
		wdev 0x1
		addr 34:e6:ad:51:6a:3a
		type managed
		channel 11 (2462 MHz), width: 40 MHz, center1: 2452 MHz
		txpower 22.00 dBm

 [archie@arch ~]$ lspci -k |grep Network
02:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)

my question looks like ambiguous but help me plz.

Last edited by sorkaud (2017-06-21 04:13:25)

Trilby · 2017-06-13 10:43:25

There is almost never any reason to use the '-D' flag for wpa_supplicant. It far more often causes problems than it does solve them.

But for the initial symptom that led you to think there would be a problem ... how slow is the scan? wpa_cli sends commands to the wpa_supplicant process to run asyncronously. The scan command can take a few moments to complete. Do not try to get scan_results until wpa_cli reports the response from wpa_supplicant saying results are available. This can take a few seconds. If it's taking more than 10 seconds I'd suspect a problem, but it is certainly no where near instantaneous. So how long does your scan take?

R00KIE · 2017-06-13 13:07:26

Did you disable whatever you were using before to manage your wifi connection?

sorkaud · 2017-06-15 01:42:34

Trilby wrote:

There is almost never any reason to use the '-D' flag for wpa_supplicant. It far more often causes problems than it does solve them.
But for the initial symptom that led you to think there would be a problem ... how slow is the scan? wpa_cli sends commands to the wpa_supplicant process to run asyncronously. The scan command can take a few moments to complete. Do not try to get scan_results until wpa_cli reports the response from wpa_supplicant saying results are available. This can take a few seconds. If it's taking more than 10 seconds I'd suspect a problem, but it is certainly no where near instantaneous. So how long does your scan take?

If i use option -D wext then it would take about 10 seconds to scan but if i don't use -D (i.e. if i use nl80211) then it doesn't work.

("seldom" was my misperception)

I highly suspect that the problem is orginated from the interfaces "p2p-dev-wlp2s0" and "wlp2s0"

I complete commands to find the command leading me to change interface but i don't know which is and even i don't know it is possible.

anyway, thanks for your advice.

Display all 157 possibilities? (y or n)
abort_scan                p2p_service_del
add_cred                  p2p_service_flush
add_network               p2p_service_rep
all_sta                   p2p_service_update
ap_scan                   p2p_set
autoscan                  p2p_stop_find
blacklist                 p2p_unauthorize
bss                       passphrase
bss_expire_age            password
bss_expire_count          pin
bss_flush                 ping
bssid                     pktcnt_poll
chan_switch               pmksa
deauthenticate            pmksa_flush
disable_network           preauthenticate
disassociate              quit
disconnect                radio_work
driver_flags              raw
dump                      reassociate
dup_network               reattach
enable_network            reauthenticate
erp_flush                 reconfigure
flush                     reconnect
ft_ds                     relog
get                       remove_cred
get_capability            remove_network
get_cred                  resume
get_network               roam
get_pref_freq_list        save_config
help                      scan
ibss_rsn                  scan_interval
identity                  scan_results
ifname                    select_network
interface                 set
interface_add             set_cred
interface_list            set_network
interface_remove          signal_monitor
level                     signal_poll
license                   sim
list_creds                sta
list_networks             sta_autoconnect
log_level                 status
logoff                    stkstart
logon                     suspend
mac_rand_scan             tdls_cancel_chan_switch
mib                       tdls_chan_switch
neighbor_rep_request      tdls_discover
new_password              tdls_link_status
nfc_get_handover_req      tdls_setup
nfc_get_handover_sel      tdls_teardown
nfc_report_handover       terminate
note                      vendor
otp                       vendor_elem_add
p2p_asp_provision         vendor_elem_get
p2p_asp_provision_resp    vendor_elem_remove
p2p_cancel                wfd_subelem_get
p2p_connect               wfd_subelem_set
p2p_ext_listen            wmm_ac_addts
p2p_find                  wmm_ac_delts
p2p_flush                 wmm_ac_status
p2p_get_passphrase        wps_ap_pin
p2p_group_add             wps_cancel
p2p_group_member          wps_check_pin
p2p_group_remove          wps_er_config
p2p_invite                wps_er_learn
p2p_listen                wps_er_nfc_config_token
p2p_lo_start              wps_er_pbc
p2p_lo_stop               wps_er_pin
p2p_peer                  wps_er_set_config
p2p_peers                 wps_er_start
p2p_presence_req          wps_er_stop
p2p_prov_disc             wps_nfc
p2p_reject                wps_nfc_config_token
p2p_remove_client         wps_nfc_tag_read
p2p_serv_disc_cancel_req  wps_nfc_token
p2p_serv_disc_external    wps_pbc
p2p_serv_disc_req         wps_pin
p2p_serv_disc_resp        wps_reg
p2p_service_add

sorkaud · 2017-06-15 01:43:58

R00KIE wrote:

Did you disable whatever you were using before to manage your wifi connection?

of course.

To be sure, i disable auto boot-up netctl and reboot and test it.

sorkaud · 2017-06-15 07:00:45

Thanks for you guys attention!!

I solve the problem

by

 sudo wpa_cli -i wlp2s0

or i figured out later that in the cli envirnment,

 interface wlp2s0

chages interface from p2p to none p2p

and now i use wpa2 enterprise wifi

For those who want to know about my wpa_supplicant config

ctrl_interface=/var/run/wpa_supplicant
update_config=1

#typical example
network={
 ssid="wifi name"
     key_mgmt=WPA-EAP
    pairwise=CCMP TKIP
    group=CCMP TKIP
    eap=PEAP
    identity="id"
    password="password"
    ca_cert="your certi if you need"
}

thanks

jasonwryan · 2017-06-15 07:04:46

Please use [Solved]. Closed denotes a locked thread.

Arch Linux

#1 2017-06-13 10:37:25

[Solved]How do i know that i use nl80211 or wext?

#2 2017-06-13 10:43:25

Re: [Solved]How do i know that i use nl80211 or wext?

#3 2017-06-13 13:07:26

Re: [Solved]How do i know that i use nl80211 or wext?

#4 2017-06-15 01:42:34

Re: [Solved]How do i know that i use nl80211 or wext?

#5 2017-06-15 01:43:58

Re: [Solved]How do i know that i use nl80211 or wext?

#6 2017-06-15 07:00:45

Re: [Solved]How do i know that i use nl80211 or wext?

#7 2017-06-15 07:04:46

Re: [Solved]How do i know that i use nl80211 or wext?

Board footer