Difference between revisions of "Talk:WPA supplicant"

From ArchWiki
Jump to: navigation, search
(wpa_cli: reopening)
(Name of page: Wish to rename page to "wpa_supplicant")
 
(18 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== wpa_cli ==
+
== Name of page ==
  
article says
+
The name of the program is stylized "wpa_supplicant" in its man page ({{man|8|wpa_supplicant}} and is "an implementation of the WPA Supplicant component" according to that page. I think it might be appropriate to rename this page "wpa_supplicant" since it is about the program, not the component it is implementing. -- [[User:Rdeckard|Rdeckard]] ([[User_talk:Rdeckard|talk]]) 02:53, 23 November 2017 (UTC)
 
 
"At this point run:
 
 
 
# wpa_cli "  
 
 
 
but isn't that misleading? In order to get wpa_cli to 'connect' to the wpa_supplicant process I had to issue # wpa_cli -p /run/wpa_supplicant
 
[[User:Rdata|Rdata]] ([[User talk:Rdata|talk]]) 22:53, 12 July 2015 (UTC)
 
 
 
:wpa_cli takes the path to socket from the wpa_supplicant's config, so it either is not configured there or wpa_cli could not find it. Anyway, the {{ic|-p}} option is described in a tip, so I think everything is fine. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:03, 13 July 2015 (UTC)
 
::Hm. Now I realize I'm not using the default config file for wpa_supplicant. I created a second config file in /etc/wpa_supplicant - maybe that's why wpa_cli can't find the socket by itself? According to the tip, if no location is given "the first found wireless interface managed by wpa_supplicant will be used" - but that's not happening here.[[User:Rdata|Rdata]] ([[User talk:Rdata|talk]]) 22:39, 14 July 2015 (UTC)
 
 
 
:::That part of the tip is about the {{ic|-i}} option. It assumes that wpa_cli has been able to connect to wpa_supplicant, which for you it likely isn't. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 05:14, 15 July 2015 (UTC)
 
 
 
::::Re-reading the article, I think I just followed the instructions. I created /etc/wpa_supplicant/e.conf containing the line "ctrl_interface=/run/wpa_supplicant". Then # wpa_supplicant -i wlan0 -B -c /etc/wpa_supplicant/e.conf works just fine. And then wpa_cli only finds the wpa_supplicant process if I use the -p /run/wpa_supplicant switch. Anyway, maybe there's some small mistake or detail I'm missing. Thanks for your time Lahwaacz.[[User:Rdata|Rdata]] ([[User talk:Rdata|talk]]) 22:21, 15 July 2015 (UTC)
 
 
 
:::::Well, closer investigation showed that wpa_cli does not read the wpa_supplicant config to get the socket path, it has only a hardcoded default value ({{ic|/var/run/wpa_supplicant}}). It's strange that this does not work for you, {{ic|/var/run/}} should be a symlink to {{ic|/run/}} on Arch. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:37, 16 July 2015 (UTC)
 

Latest revision as of 02:53, 23 November 2017

Name of page

The name of the program is stylized "wpa_supplicant" in its man page (wpa_supplicant(8) and is "an implementation of the WPA Supplicant component" according to that page. I think it might be appropriate to rename this page "wpa_supplicant" since it is about the program, not the component it is implementing. -- Rdeckard (talk) 02:53, 23 November 2017 (UTC)