SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I do not use /etc/rc.d/rc.inet1.conf to handle my device, but I do note the double quote character at the end of WPAPSK= in the information in your original post.
My /etc/wpa_supplicant.conf
Code:
ctrl_interface=/var/run/wpa_supplicant
# By default, only root (group 0) may use wpa_cli
ctrl_interface_group=root
eapol_version=1
ap_scan=1
fast_reauth=1
#country=US
# WPA2 protected network, supply your own ESSID and WPAPSK here:
network={
scan_ssid=0
# ssid="your_essid_here"
#old ssid="OPTUSA4680E8"
# RSN is WPA2 protocol
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
# psk=your_64_char_psk_here
#old psk=a895812ddbd2c70ece741f4c2765da52e7da966829b91450fc731d4f63d83a68
# or psk="<my_password>" as quoted string
#old psk="PFSLYHUMQTHHSQH47982"
priority=10
}
I note that I do not have WPA in the proto= line.
To use wpa_supplicant, I run, as root, this script.
Code:
#!/bin/sh
# Script to start wireless networking
# Stop NetworkManager daemon
/etc/rc.d/rc.networkmanager stop
# kill any existing wpa_supplicant processes
pkill wpa_supplicant
# Unblock any blocked wireless
rfkill unblock wlan
# Bring up the wlan0 interface - Not necessary, just use wpa_supplicant
#ip link set wlan0 up
# Start wpa_supplicant
wpa_supplicant -B -c/etc/wpa_supplicant.conf -iwlan0
# Get IP address
dhcpcd wlan0
# Run firewall script
/etc/rc.d/rc.firewall_wlan0
hello Allend,
First thank's for your answer. Then, you mean that with you configuration your wifi is working I imagine .
You say you don't use rc.inet.1.conf to manage your device, so what does your rc.inet1.conf looks like ?
And then, is it possible to handle the device with rc.inet1.conf instead your script ? ( just to simply manage as indicate Alien in his wiki
I have the device in a netbook where I manage network devices (wired, wireless and USB modem) using Network Manager.
As I use Network Manager, the /etc/rc.d/rc.inet1.conf does not contain any entries.
It should be possible to handle the device using rc.inet1.conf. The reason for posting the script was to show commands that directly handle the device, so you can find your problem, which I suspect is in authentication.
I uncommented the lines talking about wifi in rc.inet1.conf ; started your script, and here is the answer :
./TestWifi
Stopping NetworkManager: stopped
Bogus unblock argument 'wlan1'.
Successfully initialized wpa_supplicant
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
wlan1: adding address fe80::f164:ca22:2e79:fca4
wlan1: waiting for carrier
timed out
dhcpcd exited
./TestWifi: line 18: /etc/rc.d/rc.firewall_wlan1: No such file or directory
I don't understand why it's talked about wlan0 , when I asked ifconfig I get :
wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether c2:53:7d:a9:68:43 txqueuelen 1000 (Ethernet)
!!!!??????
and here is the answer of syslog :
<warn> [1557319487.6084] device (wlan1): Activation: (wifi) asking for new secrets
May 8 14:44:54 Slack NetworkManager[1834]: <warn> [1557319494.8119] sup-iface[0xd3da90,wlan1]: connection disconnected (reason 15)
May 8 14:45:12 Slack NetworkManager[1834]: <warn> [1557319512.0188] sup-iface[0xd3da90,wlan1]: connection disconnected (reason 15)
May 8 14:45:12 Slack NetworkManager[1834]: <warn> [1557319512.6033] device (wlan1): Activation: (wifi) association took too long
May 8 14:45:12 Slack NetworkManager[1834]: <warn> [1557319512.6049] device (wlan1): Activation: failed for connection 'freeMEUNIER'
May 8 14:50:59 Slack dhcpcd[2091]: exited: interface not found or invalid
May 8 14:53:53 Slack dhcpcd[1845]: script_runreason: /usr/libexec/nm-dhcp-helper: WEXITSTATUS 1
May 8 14:53:53 Slack dhcpcd[1845]: script_runreason: /usr/libexec/nm-dhcp-helper: WEXITSTATUS 1
May 8 14:54:28 Slack dhcpcd[2145]: timed out
/sbin/ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:26:9e:7b:52:6e brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether 3a:f3:da:86:7d:40 brd ff:ff:ff:ff:ff:ff
I think it is better. Your device is now recognised as wlan0.
Quote:
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether 3a:f3:da:86:7d:40 brd ff:ff:ff:ff:ff:ff
The device shows as DOWN.
You will need to update your /etc/rc.d/rc.inet1.conf from IFNAME[4]="wlan1" to IFNAME[4]="wlan0".
Well, well, well , it's much better, but not yet perfect ; no wifi for the while.
Here is cat /var/log/syslog :
Quote:
NetworkManager[1332]: <warn> [1557393365.0391] device (wlan0): Activation: (wifi) asking for new secrets
May 9 11:16:05 Slack NetworkManager[1332]: <warn> [1557393365.1196] sup-iface[0x1f4b290,wlan0]: connection disconnected (reason -3)
May 9 11:16:15 Slack NetworkManager[1332]: <warn> [1557393375.0819] sup-iface[0x1f4b290,wlan0]: connection disconnected (reason -3)
May 9 11:16:29 Slack named[1367]: checkhints: b.root-servers.net/A (199.9.14.201) missing from hints
May 9 11:16:29 Slack named[1367]: checkhints: b.root-servers.net/A (192.228.79.201) extra record in hints
May 9 11:16:29 Slack named[1367]: checkhints: b.root-servers.net/AAAA (2001:500:200::b) missing from hints
May 9 11:16:29 Slack named[1367]: checkhints: b.root-servers.net/AAAA (2001:500:84::b) extra record in hints
May 9 11:16:29 Slack named[1367]: checkhints: h.root-servers.net/A (198.97.190.53) missing from hints
May 9 11:16:29 Slack named[1367]: checkhints: h.root-servers.net/A (128.63.2.53) extra record in hints
May 9 11:16:29 Slack named[1367]: checkhints: h.root-servers.net/AAAA (2001:500:1::53) missing from hints
May 9 11:16:29 Slack named[1367]: checkhints: h.root-servers.net/AAAA (2001:500:1::803f:235) extra record in hints
May 9 11:16:29 Slack named[1367]: checkhints: l.root-servers.net/AAAA (2001:500:9f::42) missing from hints
May 9 11:16:29 Slack named[1367]: checkhints: l.root-servers.net/AAAA (2001:500:3::42) extra record in hints
May 9 11:16:30 Slack NetworkManager[1332]: <warn> [1557393390.0342] device (wlan0): Activation: (wifi) association took too long
May 9 11:16:30 Slack NetworkManager[1332]: <warn> [1557393390.0385] device (wlan0): Activation: (wifi) asking for new secrets
May 9 11:16:30 Slack NetworkManager[1332]: <warn> [1557393390.1278] sup-iface[0x1f4b290,wlan0]: connection disconnected (reason -3)
May 9 11:16:40 Slack NetworkManager[1332]: <warn> [1557393400.1312] sup-iface[0x1f4b290,wlan0]: connection disconnected (reason -3)
May 9 11:16:55 Slack NetworkManager[1332]: <warn> [1557393415.0352] device (wlan0): Activation: (wifi) association took too long
May 9 11:16:55 Slack NetworkManager[1332]: <warn> [1557393415.0366] device (wlan0): Activation: failed for connection 'freeMEUNIER'
NetworkManager[1332]: <warn> [1557393365.0391] device (wlan0): Activation: (wifi) asking for new secrets
You are using Network Manager, which people usually find to be easier to configure.
You seem to have missed this note on the wiki page you linked.
Quote:
If you want to use NetworkManager, you will have to remove any network interface configuration information from /etc/rc.d/rc.inet1.conf in order to prevent a struggle for power between Network Manager and Slackware's rc.inet1 script.
When changing to use Network Manager, follow the official advice. The relevant paragraph is reproduced here.
I think i 'm gone make a little rest for my neurons ; at the moment I'm said to be wifi connected, but as I am a little bit suspicious, I'm gone wait and let things settle for a while and see what happens at the next reboot.
Thank's for all; I'll be back to tell you .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.