You are not logged in.
Pages: 1
I am having problems with my wireless link, because it continuously switches to mode Dormant.
# ip link
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: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 2c:60:0c:0e:6e:89 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 10:08:b1:57:35:61 brd ff:ff:ff:ff:ff:ff
When I try to connect to an access point it seems to connect without a problem:
# iwconfig
enp3s0 no wireless extensions.wlp2s0 IEEE 802.11abgn ESSID:"Lantech"
Mode:Managed Frequency:2.412 GHz Access Point: 00:E0:20:22:67:2C
Bit Rate=26 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=64/70 Signal level=-46 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:4 Missed beacon:0lo no wireless extensions.
but, I presume because the mode is DORMANT, the connection is not recognised, so I am not actually on the network.
The hardware is
product: AR9462 Wireless Network Adapter [168C:34]
vendor: Qualcomm Atheros [168C][
using
driver: ath9k
driverversion: 4.5.1-1-ARCH
Arch has been updated today.
Any help would be very much appreciated.
PS When I was googling the problem I found this which I tried without success
# ip link set wlp2s0 up
# wifi-menu
# dhcpcd wlp2s0
# iw wlp2s0 link
but wifi-menu returns an error:
● netctl@wlp2s0\x2dLantech.service - Networking for netctl profile wlp2s0-Lantech
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2016-04-23 12:49:04 CEST; 51s ago
Docs: man:netctl.profile(5)
Process: 11009 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 11009 (code=exited, status=1/FAILURE)Apr 23 12:49:04 acer systemd[1]: Starting Networking for netctl profile wlp2s0-Lantech...
Apr 23 12:49:04 acer network[11009]: Starting network profile 'wlp2s0-Lantech'...
Apr 23 12:49:04 acer network[11009]: The interface of network profile 'wlp2s0-Lantech' is already up
Apr 23 12:49:04 acer systemd[1]: netctl@wlp2s0\x2dLantech.service: Main process exited, code=exited, status=1/FAILURE
Apr 23 12:49:04 acer systemd[1]: Failed to start Networking for netctl profile wlp2s0-Lantech.
Apr 23 12:49:04 acer systemd[1]: netctl@wlp2s0\x2dLantech.service: Unit entered failed state.
Apr 23 12:49:04 acer systemd[1]: netctl@wlp2s0\x2dLantech.service: Failed with result 'exit-code'.
Thanks
Andrew
Last edited by fdservices (2016-04-25 07:32:31)
Offline
So it seems that the problem had nothing to do with the DORMANT/DEFAULT issue after all. It was the DHCP server on the router which has stopped working correctly.
I would still be interested in understanding the difference between the modes DORMANT and DEFAULT, if anyone knows?
Andrew
Offline
Pages: 1