confiring wireless manually from the command line
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Hi
I have been attempting to configure wireless manually from the command line on my Thinkpad 400, but have been unable to get a connection. I am using Trisquel 8.0 which I believe is based on Debian:
$ uname -a
Linux technoethical-t400s-b9d0 4.19.0-gnu #1 SMP Mon Oct 22 06:05:01 PDT 2018 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/os-release
NAME="Trisquel GNU/Linux"
VERSION="8.0, Flidas"
ID=trisquel
ID_LIKE=debian
PRETTY_NAME="Trisquel GNU/Linux Flidas (8.0)"
VERSION_ID="8.0"
HOME_URL="https://trisquel.info/"
SUPPORT_URL="https://trisquel.info/wiki"
BUG_REPORT_URL="https://trisquel.info/project/issues"
I am using the following commands to configure:
# disable NetworkManager
systemctl disable NetworkManager
#kill existing wpa_supp
ps -ef | grep wpa
pid=`ps -ef | grep wpa | grep -v grep | awk '{print $2}'`
kill -s SIGQUIT "${pid}"
#check interfaces and find wireles device name
$ iw dev | grep Interface
Interface wlp2s0
#check device is up
$ ip link show wlp2s0 | grep UP
#if not bring it up
$ ip link set wlp2s0 up
# backup config file
$ cp /etc/wpa_supplicant.conf /etc/wpa_supplicant.conf.bu
# check ssid can be scanned
$ iw wlp2s0 scan | grep lcwire
SSID: lcwire
# create wpa_supplicant.conf
wpa_passphrase lcwire [passphrase] > /etc/wpa_supplicant.conf
# check driver
$ lsmod | grep 9k
ath9k 151552 0
ath9k_common 36864 1 ath9k
ath9k_hw 479232 2 ath9k_common,ath9k
ath 32768 3 ath9k_common,ath9k,ath9k_hw
mac80211 798720 1 ath9k
cfg80211 659456 4 ath9k_common,ath9k,ath,mac80211
$ wpa_supplicant
....
drivers:
nl80211 = Linux nl80211/cfg80211
wext = Linux wireless extensions (generic)
wired = Wired Ethernet driver
none = no driver (RADIUS server/WPS ER)
....
# run wpa_supplicant
wpa_supplicant -B -D nl80211 -i wlp2s0 -c /etc/wpa_supplicant.conf -d
After doing this the syslog seem to indicate theat the conneciton is contiually being deauthenticated.
I have attached files with output from journalctl (syslog.txt) and the debug output from wpa_supplicant.
I have a machine with fedora on it where I do a similar set of commands (different driver - use-D ext) and it connects fine.
If I use NetworkManager (which came enabled when I got the system) it also connects fine, though for some reason I have to reboot after powerup for it to work.
Other Notes:
1./
ifconfig gives me the following:
wlp2s0 Link encap:Ethernet HWaddr c0:cb:38:61:98:59
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:2460 errors:0 dropped:0 overruns:0 frame:0
TX packets:1046 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:421705 (421.7 KB) TX bytes:162400 (162.4 KB)
wlp2s0:avahi Link encap:Ethernet HWaddr c0:cb:38:61:98:59
inet addr:169.254.7.124 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Not sure where wlp2s0:avahi comes from - I do not see this on my fedora machine or when I use NetworkManager to bring it up, only the interface with the locally configured ipaddress received from the router.
hen the interface is working after rebooting with NetworkManager enabled ifcoinfi shows:
wlp2s0 Link encap:Ethernet HWaddr c0:cb:38:61:98:59
inet addr:192.168.2.26 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: 2002:5201:e7e1:1234:2e5d:3fc9:79d5:2799/64 Scope:Global
inet6 addr: fe80::d195:9bc6:b6d:ad17/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7586 (7.5 KB) TX bytes:9256 (9.2 KB)
2./
$ rfkill list
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Has anyone any idea why I am seeing the deauthentication ?
Does anyone know what the wlp2s0:avahi interface is ? - It seems to have a random (external?) ip addess assigned.
hen the interface is working after rebooting with NetworkManager enabled ifcoinfi shows:
wlp2s0 Link encap:Ethernet HWaddr c0:cb:38:61:98:59
inet addr:192.168.2.26 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: 2002:5201:e7e1:1234:2e5d:3fc9:79d5:2799/64 Scope:Global
inet6 addr: fe80::d195:9bc6:b6d:ad17/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7586 (7.5 KB) TX bytes:9256 (9.2 KB)
2./
$ rfkill list
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Has anyone any idea why I am seeing the deauthentication ?
Does anyone know what the wlp2s0:avahi interface is ? - It seems to have a random (external?) ip addess assigned.
When the interface is working after rebooting with NetworkManager enabled ifcoinfi shows:
wlp2s0 Link encap:Ethernet HWaddr c0:cb:38:61:98:59
inet addr:192.168.2.26 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: 2002:5201:e7e1:1234:2e5d:3fc9:79d5:2799/64 Scope:Global
inet6 addr: fe80::d195:9bc6:b6d:ad17/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7586 (7.5 KB) TX bytes:9256 (9.2 KB)
2./
$ rfkill list
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Can anyone see/is able to guess what might be wrong with the configuration ?
Has anyone any idea why I am seeing the deauthentication ?
Does anyone know how I can get information from NetworkManager - config files, logs etc. to see if I can tell what it is doing differently ?
Does anyone know what the wlp2s0:avahi interface is and why it is generated ? - It seems to have a random (external?) ip addess assigned.
Pièce jointe | Taille |
---|---|
wpaop.txt | 7.94 Ko |
syslog.txt | 3.46 Ko |
Adding attachment containing output from jounalctl for NetworkManager when it is running
Pièce jointe | Taille |
---|---|
jcnetman.log | 33.23 Ko |
- Vous devez vous identifier ou créer un compte pour écrire des commentaires