You are not logged in.

#1 2018-02-18 15:36:56

Noah-Huppert
Member
Registered: 2016-07-19
Posts: 10
Website

Connmanctl does not autoconnect after resume

I am using Connman as my connection manager because it has autoconnect functionality built in.

This autoconnect functionality worked for a couple months. However about 4(?) months ago it stopped working. Now after I close my laptop lid and then re-open it Connam will not autoconnect.

Instead I have to manually type

connmanctl> connect wifi_123abcxyz_managed_psk

I suspect this has to do with power settings and the sleep functionality. However I have been unable to make any progress debugging and could use some help.

One can see in my connmanctl services output that I have several services with autoconnect configued.

I have looked over the journalctl output for connman.service and found a few errors which repeat. However I am not entirely sure if any of these errors are causing the issue I am experiencing.

I am on a Dell XPS 13, Arch 4.15.2-2-ARCH.

Please let me know if there is any additional debug information you would like me to retrieve.

Last edited by Noah-Huppert (2018-03-03 21:32:03)

Offline

#2 2018-03-01 14:54:05

Noah-Huppert
Member
Registered: 2016-07-19
Posts: 10
Website

Re: Connmanctl does not autoconnect after resume

After several months of this issue occuring it has randomly stopped. I assume that there was some sort of bug that was fixed in a recent update.

Offline

#3 2018-03-01 17:42:48

NoSuck
Member
Registered: 2015-03-04
Posts: 157
Website

Re: Connmanctl does not autoconnect after resume

I wonder if this had anything to do with a known “not-a-bug” with systemd, as I see your device name happens to be "wlan0" instead of following "wlp0s00u0u0" format, for example.

Offline

#4 2018-03-01 21:12:07

Noah-Huppert
Member
Registered: 2016-07-19
Posts: 10
Website

Re: Connmanctl does not autoconnect after resume

NoSuck wrote:

I wonder if this had anything to do with a known “not-a-bug” with systemd, as I see your device name happens to be "wlan0" instead of following "wlp0s00u0u0" format, for example.

This could be. I have a custom rule to make sure my wireless interface is named wlan. From this Arch Wiki page, my specific file.

It kept alternating between wlan and the wlpxxsx format. Which was causing issues with my Polybar configuration.

Last edited by Noah-Huppert (2018-03-01 21:15:27)

Offline

#5 2018-03-03 21:32:33

Noah-Huppert
Member
Registered: 2016-07-19
Posts: 10
Website

Re: Connmanctl does not autoconnect after resume

And it's back. 

Not solved.

Offline

#6 2018-03-04 18:13:05

NoSuck
Member
Registered: 2015-03-04
Posts: 157
Website

Re: Connmanctl does not autoconnect after resume

Try making it simpler:

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="MAC_ADDRESS", NAME="wlan0"

What does the connmanctl status command show for your wireless network, after failing to automatically connect?  Your output of "connmanctl services" shows a successful connection, so I am confused.

A Autoconnect
O Online
R Ready
a associated
c configured
d disconnected
* favorited

By the way, you can set PreferredTechnologies to prevent your system from connecting to Wi-Fi when it has a wired connection available.

Offline

#7 2018-03-05 14:07:58

Noah-Huppert
Member
Registered: 2016-07-19
Posts: 10
Website

Re: Connmanctl does not autoconnect after resume

NoSuck wrote:

Try making it simpler:

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="MAC_ADDRESS", NAME="wlan0"

What does the connmanctl status command show for your wireless network, after failing to automatically connect?  Your output of "connmanctl services" shows a successful connection, so I am confused.

A Autoconnect
O Online
R Ready
a associated
c configured
d disconnected
* favorited

By the way, you can set PreferredTechnologies to prevent your system from connecting to Wi-Fi when it has a wired connection available.

I believe I had an active network connection when I gathered the output of connmanctl services. B/c I was actively creating a GitHub gist with all the debug information. 

Here are some connmanctl command outputs after it failed to autoconnect:

$ connmanctl services
*AR Wired                ethernet_42f9fbdfb88a_cable
*AR Wired                ethernet_52092b243b06_cable
*A  drexelguest          wifi_3052cb823a67_64726578656c6775657374_managed_none
*A  eduroam              wifi_3052cb823a67_656475726f616d_managed_ieee8021x
    dragonfly3           wifi_3052cb823a67_647261676f6e666c7933_managed_ieee8021x
    dragonfly            wifi_3052cb823a67_647261676f6e666c79_managed_wep

$ connmanctl status
Error 'status': Unknown command

$ connmanctl state
  State = ready
  OfflineMode = False
  SessionMode = False

Last edited by Noah-Huppert (2018-03-05 15:18:29)

Offline

Board footer

Powered by FluxBB