What "wireless=unassociated" means?

BrayaON · 11-08-2018, 08:44 PM

Code:

sudo journalctl -f > output.txt

Thank you for your answers.

You're right. I've was seeing that I have this directory /etc/netplan/01-network-manager-all.yaml

This https://pastebin.com/wmRTXvJg is the link of the output when I typed

Code:

sudo journalctl -f > output.txt

I can't understand that output, but I hope that you can help me.

ferrari · 11-09-2018, 03:21 AM

I don't know the underlying cause, but the log shows authentication failure...

Code:

nov 08 21:15:46 user-B250M-DS3H wpa_supplicant[862]: wlxec086b105627: CTRL-EVENT-DISCONNECTED bssid=fc:52:8d:24:9c:61 reason=0
nov 08 21:15:46 user-B250M-DS3H wpa_supplicant[862]: wlxec086b105627: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="UNE_HFC_FDEA" auth_failures=1 duration=10 reason=CONN_FAILED
nov 08 21:15:46 user-B250M-DS3H wpa_supplicant[862]: wlxec086b105627: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
nov 08 21:15:46 user-B250M-DS3H NetworkManager[861]: <info>  [1541729746.3369] device (wlxec086b105627): supplicant interface state: associating -> disconnected

Perhaps try restarting your wireless router and then see if you can connect successfully. Which wifi authentication protocol are you using?

BrayaON · 11-09-2018, 08:10 AM

Quote:

Perhaps try restarting your wireless router and then see if you can connect successfully. Which wifi authentication protocol are you using?

I tried, nothing happen...

The wifi authentications procotol that I use is wpa2.

Thank you so much for help me. I appreciated, but I going to stop with this. And I know that this forum isn't for that, but I would like that recommend me what do i have to do? I going to formatted my pc and I don't know what distribution must install in order to fix this problem because I can't connect my pc with a Ethernet, then I must to use a external device for connection.

Again, thank you for help me.

ferrari · 11-09-2018, 01:56 PM

Well, at least you now know that it is an authentication problem. I'm always happy to help where I can. Sometimes issues like this take further analysis in order to help resolve them, but I accept not everybody has the time or is technically equipped to do this. Occasionally a bug report is required, so that developers can fix a bug. Anyway, good luck with finding a path that works for you.

BrayaON · 11-09-2018, 06:06 PM

Quote:

Occasionally a bug report is required, so that developers can fix a bug

You're right, I want to publish this issue bug and I don't know where i have to do it. If you know where, please, tell me and I'll do.

I thank you, always I ask to other this and nobody respond me. I appreciate so much your help

ferrari · 11-09-2018, 07:36 PM

From the information published here I understand that netplan configuration is located in /etc/netplan directory. You could find where your wifi config is stored (eg etc/netplan/config.yaml) remove it and try to configure your wifi connection again - just in case it is a config issue. Worth a shot IMHO.

For Ubuntu users, here's how to go about submitting a bug report....
https://help.ubuntu.com/community/ReportingBugs

FWIW, I've seen another approach to diagnosing cwifi onnection issues, by attempting to connect manually from a terminal using wpa_supplicant. (Not sure if netplan needs to be stopped first.)

To do this, configure /etc/wpa_supplicant/wpa_supplicant.conf with your wireless network SSID and passphrase....

Code:

network={
    ssid="yourSSID"
    psk="yourPassPhrase"
}

Then try associating with

Code:

sudo wpa_supplicant -d -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlxec086b105627

The output should help with any diagnosis/bug report, and there should also be logging at /var/log/wpa_supplicant.log to help with this as well.

FWIW, I also stumbled across this thread which describes how to return to the classic networking framework if preferred...
https://askubuntu.com/questions/1031...ork-interfaces

BrayaON · 11-12-2018, 08:35 PM

Oh man, imagine that I was try to write my bug in https://help.ubuntu.com/community/ReportingBugs but before do that, I downloaded Linuxmint 19 and I run it in a usb live, but, for my surprise, the problem continues there. Is the same problem, with the difference that there not appear wireless=unassociated instead appear this wireless=IEEE 802.11 and I investigated what it means and I found that is correct configurated. When I saw this problem, I supposed that isn't a bug for Ubuntu users, then I don't wrote nothing.
With this

Code:

network={
    ssid="yourSSID"
    psk="yourPassPhrase"
}

I tried, but nothing happenned. O maybe yes, but never stops. Shows and Shows a lot of lines but the problem continues.

Now I'm more frustrated with this issue. I don't know what I have to do. I don't know if is a problem with my computer or with your configuration. I have a Workstation and I don't know if is for that because with my laptop never like this happens. Or maybe is the TP-Link adapter (but, a lot friends in a group of Telegram tell me that this adapter is compatible with GNU/Linux )

ferrari · 11-12-2018, 09:54 PM

Quote:

I don't know what I have to do. I don't know if is a problem with my computer or with your configuration.

I hope you didn't use that configuration literally. The ssid and psk values need to match your network. You know that they represent your wifi network SSID and WPA passkey right?

The idea is that the output from wpa_supplicant needs to be captured, as it is this output that may help with determining where the problem lies. Definitive information is what is required to understand a problem or bug, and the kind of information that may help resolve a bug (if it exists).

BrayaON · 11-13-2018, 09:32 PM

Quote:

Originally Posted by ferrari

I hope you didn't use that configuration literally. The ssid and psk values need to match your network. You know that they represent your wifi network SSID and WPA passkey right?

xD yes, of course. I'm not that stupid I used the respective credentials of my network.
I tried again and saved the output in a file. [URL = "https://pastebin.com/sQcG1pd8"] https://pastebin.com/sQcG1pd8 [/ URL] on this link is all the output (I have to break it because it never stops)

On the other hand, I also confirmed that this issue is not only in my computer. I'll tried the same process in other workstation (my uncle's computer) and with the Ethernet, all work very well, but when I disconnect the Ethernet and plug the TP-link adapter also appears the networks but when I going to connect to one, shows the same message. I don't know if this can be useful, but now I'm sure that the problem isn't my computer

Also, I tried with the instructions that described in this link http://linux.icydog.net/wpa.php and the computer not work with this instructions. I'll let output here, maybe is useful. https://pastebin.com/GLg04gEd. (My command was wpa_supplicant -Dwext -iwlxec086b105627 -c /etc/wpa_supplicant/wpa.conf I used wext because my driver did not appeared in list when I typed wpa_supplicant --help)

ferrari · 11-13-2018, 11:24 PM

It was your comment

Quote:

I don't know if is a problem with my computer or with your configuration.

that led me to question you about the configuration used - it wasn't mine, it's specific to your network

Anyway, your wpa_supplicant output does show that the device appears to get associated....

Code:

Removed BSSID fc:52:8d:24:9c:61 from blacklist (clear)
wlxec086b105627: Selecting BSS from priority group 0
wlxec086b105627: 0: fc:52:8d:24:9c:61 ssid='UNE_HFC_FDEA' wpa_ie_len=26 rsn_ie_len=24 caps=0x1511 level=-57 freq=2412
wlxec086b105627:    selected based on RSN IE
wlxec086b105627:    selected BSS fc:52:8d:24:9c:61 ssid='UNE_HFC_FDEA'
wlxec086b105627: Considering connect request: reassociate: 0  selected: fc:52:8d:24:9c:61  bssid: 00:00:00:00:00:00  pending: 00:00:00:00:00:00  wpa_state: SCANNING  ssid=0x5605b1544380  current_ssid=(nil)
wlxec086b105627: Request association with fc:52:8d:24:9c:61
wlxec086b105627: Re-association to the same ESS
.
.
.
.
nl80211: Connect request send successfully
wlxec086b105627: Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: ifi_index=3 ifname= wext ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Drv Event 48 (NL80211_CMD_DISCONNECT) received for wlxec086b105627
nl80211: Disconnect event
wlxec086b105627: Event DEAUTH (12) received
wlxec086b105627: Deauthentication notification
wlxec086b105627:  * reason 0

...but then getting disassociated again. I think that you'll need to submit a bug report fir this. Beyond my pay grade.

BrayaON · 11-14-2018, 07:26 AM

Quote:

Originally Posted by ferrari

...but then getting disassociated again. I think that you'll need to submit a bug report fir this. Beyond my pay grade.

Yes, bro. Thank you for help me.

I going to report this bug here https://help.ubuntu.com/community/ReportingBugs. Do you think that they respond o, maybe, they resolve the problem?

ferrari · 11-14-2018, 04:08 PM

Well that's the general idea.