WIFI - Solving Error: Reason: 3=DEAUTH_LEAVING

Kernels & Hardware, configuring network, installing services

WIFI - Solving Error: Reason: 3=DEAUTH_LEAVING

Postby maja_ldm » 2018-12-31 03:21

I freshly installed Debian Stretch and I'm trying to get a wirelss internet connection from the same usb dongle that was used during the netinst installation of the system. The same dongle worked when Debian was installed and still works on a Windows 10 installation on the same machine. According to lsusb the dongle's name is D-Link Corp. DWA-121 802.11n Wireless N 150 Pico Adapter [Realtek RTL8188CUS] and it requires the driver rtlwifi/rtl8192cufw_TMSC.bin which is installed as part of the non-free package firmware-realtek_20161130-4_all.deb and loads correctly according to the dmesg output.

The device name is an unusually long string: wlx10bef501e1cd. The same name was used successfully during installation of Debian (connecting through ipv6). During previous start up of the system I recorded the following output: rtl8192cu 1-3:1.0 wlx10bef501e1cd: renamed from wlan0, but I can't find that same line in more recent attempts. Also, in a previous installation (which used mate instead of Gnome) the following error appeared several times, indicating that the name was too long, but in the current installation this output has disappeared:

Code: Select all
wlx10bef501e1cd: authenticate with 90:94:e4:e7:99:cc
wlx10bef501e1cd: send auth to 90:94:e4:e7:99:cc (try 1/3)
wlx10bef501e1cd: authenticated
wlx10bef501e1cd: aborting authentication with 90:94:e4:e7:99:cc by local choice (Reason: 3=DEAUTH_LEAVING)


This is an example output of attempting a connection through the dongle:

Code: Select all
___@DESK:~$ sudo ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 4c:cc:6a:2a:58:c7 brd ff:ff:ff:ff:ff:ff
3: wlx10bef501e1cd: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 7a:f2:a4:51:a8:5a brd ff:ff:ff:ff:ff:ff

___@DESK:~$ sudo ip link set wlx10bef501e1cd upmaja@DESK:~$ sudo iwlist wlx10bef501e1cd scanwlx10bef501e1cd  Scan completed :
          Cell 01 - Address: 90:94:E4:E7:99:CC
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=70/70  Signal level=-40 dBm 
                    Encryption key:on
                    ESSID:"dlink_DIR-506L"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=00000001045fc5d5
                    Extra: Last beacon: 4ms ago
                    IE: Unknown: 000E646C696E6B5F4449522D3530364C
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 03010B
                    IE: Unknown: 2A0100
                    IE: Unknown: 32040C183060
                    IE: Unknown: 2D1A6E1117FF000000010000000000000000000000000C0000000000
                    IE: Unknown: 3D160B000600000000000000000000000000000000000000
                    IE: Unknown: 3E0100
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                    IE: Unknown: 0B05020020127A
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F0101
                    IE: Unknown: DD07000C4307000000
                    IE: Unknown: 0706545720010B10
                    IE: Unknown: DD7D0050F204104A0001101044000101103B000103104700102880288028801880A8809094E4E799CC10210004416D697410230009334720526F75746572102400085742522D303030311042000831323334353637381054000800060050F20400011011000E646C696E6B5F4449522D3530364C10080002200C103C000101

___@DESK:~$ sudo iwconfig wlx10bef501e1cd essid dlink_DIR-506L key s:___{password}___
Error for wireless request "Set Encode" (8B2A) :
    SET failed on device wlx10bef501e1cd ; Invalid argument.


Also, after modifying /etc/network/interfaces with:

Code: Select all
auto wlx10bef501e1cd
iface wlx10bef501e1cd inet dhcp
        wpa-ssid dlink_DIR-506L
        wpa-psk ___{password}___


I tried the following:

Code: Select all
sudo dhclient wlx10bef501e1cd


which after about a minute results in no output in the terminal and no connection established, it also results in the connection hanging indefinetely at startup as shown by the GUI with a "waiting"symbol in the connection selection and by the following output:

Code: Select all
sudo iwconfig wlx10bef501e1cd essid dlink_DIR-506L key s:___{password}___
Error for wireless request "Set ESSID" (8B1A) :
    SET failed on device wlx10bef501e1cd ; Operation already in progress.


I'm also including some relevant lines from the most recent dmesg output:

Code: Select all
[    9.446494] rtl8192cu: Chip version 0x10
[    9.481477] rtl8192cu: Board Type 0
[    9.483475] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[    9.485500] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[    9.568252] usb 1-3: firmware: direct-loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[    9.591858] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[    9.592048] usbcore: registered new interface driver rtl8192cu
[    9.647402] intel_rapl: Found RAPL domain package
[    9.647934] intel_rapl: Found RAPL domain core
[    9.648414] intel_rapl: Found RAPL domain dram
[   10.477794] Adding 16722940k swap on /dev/sdb3.  Priority:-1 extents:1 across:16722940k FS
[   11.046475] rtl8192cu 1-3:1.0 wlx10bef501e1cd: renamed from wlan0
[   17.813048] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   17.850402] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168h-2.fw
[   17.907529] r8169 0000:02:00.0 enp2s0: link down
[   17.909597] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   17.921049] IPv6: ADDRCONF(NETDEV_UP): wlx10bef501e1cd: link is not ready
[   17.924911] rtl8192cu: MAC auto ON okay!
[   17.937484] rtl8192cu: Tx queue select: 0x05
[   18.315671] IPv6: ADDRCONF(NETDEV_UP): wlx10bef501e1cd: link is not ready
[   18.321641] rtl8192cu: MAC auto ON okay!
[   18.332597] rtl8192cu: Tx queue select: 0x05
[   18.711138] IPv6: ADDRCONF(NETDEV_UP): wlx10bef501e1cd: link is not ready
[   18.962939] IPv6: ADDRCONF(NETDEV_UP): wlx10bef501e1cd: link is not ready
[   51.572026] fuse init (API version 7.26)


When the dmesg output reported Reason: 3=DEAUTH_LEAVING errors I attempted to create a permenent rule in /etc/udev/rules.d/70-persistent-net.rules with the following (after getting values from udevadm info), without success and since since I can't see the same error at start up anymore I gave up on this line.

Code: Select all
SUBSYSTEM=="usb",ACTION=="add",DRIVERS=="usb",ATTRS{product}=="802.11n WLAN Adapter",ATTR{dev_id}=="0x0",ATTR{type}=="1",KERNEL=="1-3", NAME="wlan1"


Since the dongle was used to download the system during installation I believe it can be used to connect to the internet, but I don't seem to be able to figure out how making it work. What steps can I attempt next (also, consider I'm not an experience user and I'll probably need to be spoonfed each command one by one).
Last edited by maja_ldm on 2018-12-31 13:58, edited 1 time in total.
maja_ldm
 
Posts: 12
Joined: 2013-02-22 15:19

Re: Wifi dongle used during installation can't connect anymo

Postby Head_on_a_Stick » 2018-12-31 08:28

Can you connect using static addresses? If so, check your router for any expired leases.
"French riots get results! U lot are instagram zzzombies" — graffiti over Euston underpass
User avatar
Head_on_a_Stick
 
Posts: 8610
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Wifi dongle used during installation can't connect anymo

Postby Dai_trying » 2018-12-31 08:32

I have a usb device with the rtl8192cu chipset and had to use a github fix to prevent the signal dropping after a few minutes, I would guess it might help you too.
https://github.com/pvaret/rtl8192cu-fixes
The readme states it is now deprecated from kernel 4.4 onwards (aimed at ubuntu but the fix works for debian), but I have it in use on a couple of machines that occasionally need to use wifi with my TL-WN822N
YMMV
Dai_trying
 
Posts: 577
Joined: 2016-01-07 12:25

Re: Wifi dongle used during installation can't connect anymo

Postby maja_ldm » 2018-12-31 13:57

Head_on_a_Stick wrote:Can you connect using static addresses? If so, check your router for any expired leases.


I wouldn't know how to do that, but I logged in my router and verified there aren't any expired leases.

Dai_trying wrote:I have a usb device with the rtl8192cu chipset and had to use a github fix to prevent the signal dropping after a few minutes, I would guess it might help you too.
https://github.com/pvaret/rtl8192cu-fixes
The readme states it is now deprecated from kernel 4.4 onwards (aimed at ubuntu but the fix works for debian), but I have it in use on a couple of machines that occasionally need to use wifi with my TL-WN822N
YMMV


I was getting ready to install the repackaging (which was a cumbersome operation since I had zero access to the internet), but then I realized the renaming and DEAUTH error were still in the dmesg output and headed over to stack exchange to ask how to avoid the device being renamed (https://unix.stackexchange.com/questions/491754/why-is-my-wlan-device-being-renamed-reason-3-deauth-leaving-error?noredirect=1#comment902488_491754), which ended up working since now I have a functional interent connection.

For further reference writing a correct renaming rule would also probably have worked.
maja_ldm
 
Posts: 12
Joined: 2013-02-22 15:19

Re: WIFI - Solving Error: Reason: 3=DEAUTH_LEAVING

Postby elissabsmith » 2019-01-05 05:22

Yea I am getting about your problem, all what I have done is to figure out about the right Wireless router and the right Router table. But as I am not sure, I don't know how to get the router table, all I can suggest is you to get the suggestions from the community member.
Thanks!
elissabsmith
 
Posts: 1
Joined: 2019-01-05 04:49

Re: WIFI - Solving Error: Reason: 3=DEAUTH_LEAVING

Postby Head_on_a_Stick » 2019-01-05 10:29

tommiecollins wrote:Then calling to my internet connector, he told me that you need a right router table so that it can support your Internet cable. Then you will be installing the Wi-Fi dongle and it will work out.

This will show the routing table for your machine:
Code: Select all
ip route

The configuration is usually taken care of by the networking software (such as NetworkManager) but you can do it manually if you want.
"French riots get results! U lot are instagram zzzombies" — graffiti over Euston underpass
User avatar
Head_on_a_Stick
 
Posts: 8610
Joined: 2014-06-01 17:46
Location: /dev/chair


Return to System configuration

Who is online

Users browsing this forum: No registered users and 10 guests

fashionable