Just installed debian 9, wifi refuses to connect.

[SpecialBomb]

I have installed debain 9.0.0, and as usual, the wifi is messing up.

When I installed debian 8, none of this was an issue besides getting the drivers installed.

I use an atheros usb dongle device, and I have put drivers on already and they are working.

The issue is that when I use networkmanager in kde, the dongle is able to see my WPA network, but is fails to connect when the message on the taskbar says "configuring interface" and hangs for 30 seconds before giving up.

One thing to note is that I manually set up dhcp while installing, and that a wired connection is impossible for me, so information will be hard to relay.

One thing that is different to me is that my device is called "wlx98ded00cb6e9", and I don't know why. This can be seen in the "restrict to device" field in networkmanager when editing the connection.

If you need information, I will need to take pictures with my phone.

[FreewheelinFrank]

Any messages in dmesg about missing firmware?

Code: Select all

# dmesg

What exactly is the dongle? (ie chipset.) From experience, you may need to get out a magnifying glass and Google the identification codes till you find one that tells you the actual chipset.

There is stuff in firmware-zd1211, firmware-linux-free and firmware-atheros that relates to Atheros wireless cards. Maybe some firmware that was in the kernel got bumped into one of these?

[SpecialBomb]

I am missing a driver for r8169, but that is not my wireless chipset. I will find the drivers and install them anyway to see what happens.

The chipset of my dongle is Atheros AR9002U, which I am very sure I have drivers loaded for.

In dmesg, I noticed it saying that the wlx98ded00cb6e9 device, the dongle, is having trouble authenticating. It tried a few times, it looks like. I would take a picture, but it turns out I get an error if I try to upload it,

[SpecialBomb]

Good news, I manually set up a connection using dhcdcd and ip, and learned how to do it every time I start up.

Bad news is that NetworkManager is still having issues, and it should be looked into further in order to prevent fresh installers like me from tripping up.

[SpecialBomb]

Okay, I replaced networkmanager with wicd to see if anything different would happen.

With wicd, nothing connects, similar to networkmanager.

Since I am able to, here is the output of dmesg when a connection using networkmanager or wicd is attempted:

Code: Select all

[  330.850115] wlx98ded00cb6e9: authenticate with e8:de:27:f6:40:56
[  331.026990] wlx98ded00cb6e9: send auth to e8:de:27:f6:40:56 (try 1/3)
[  331.029234] wlx98ded00cb6e9: authenticated
[  331.029731] wlx98ded00cb6e9: associate with e8:de:27:f6:40:56 (try 1/3)
[  331.036516] wlx98ded00cb6e9: RX AssocResp from e8:de:27:f6:40:56 (capab=0x431 status=0 aid=6)
[  331.045381] wlx98ded00cb6e9: associated
[  331.847445] wlx98ded00cb6e9: deauthenticating from e8:de:27:f6:40:56 by local choice (Reason: 3=DEAUTH_LEAVING)

Small note, I will be leaving for vacation tomorrow for three-ish days, so I will not be able to respond in time. Patience!

[Bulkley]

Network Manager and Wicd are both GUI front ends for wpa_supplicant. It is possible to set up wpa_supplicant directly using /etc/network/interfaces .

BTW, Network Manager and Wicd will interfere with each other. If you want to use one purge the other.

[orythem27]

I use an atheros usb dongle device
my device is called "wlx98ded00cb6e9

Looks like this issue: http://forums.debian.net/viewtopic.php?f=7&t=133597

Turn off automatic MAC spoofing in /etc/NetworkManager/NetworkManager.conf .

Related issues:
http://forums.debian.net/viewtopic.php?f=5&t=133495
http://forums.debian.net/viewtopic.php?f=7&t=133518

[SpecialBomb]

@Bulkley

That is what I may do, as I really don't need a NM anyway, it's not like I am taking my desktop anywhere.

@orythem27

Is it possible that Wicd does the same thing, as I am having issues with it as well? If that's the case, is there an equivalent fix?

[orythem27]

Is it possible that Wicd does the same thing, as I am having issues with it as well? If that's the case, is there an equivalent fix?

This is probably not an equivalent fix, but works for me before I knew about the NM mac spoofing issue.
See http://forums.debian.net/viewtopic.php? ... be#p647105