From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: David Wilson <david@daviwil.com>
Cc: help-guix@gnu.org
Subject: Re: NetworkManager does not autoconnect wifi after boot or wake
Date: Wed, 9 Oct 2019 06:56:28 +0200 [thread overview]
Message-ID: <20191009045627.dmb23di2ujfpxkw5@pelzflorian.localdomain> (raw)
In-Reply-To: <adaa33da-26d5-4c8b-b6a4-918e6fe2e583@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Tue, Oct 08, 2019 at 03:48:38PM -0700, David Wilson wrote:
> Hi all,
>
> Does anyone know whether there's a configuration setting I can use somewhere that will cause NetworkManager to automatically (re)connect wifi upon boot or after waking from suspend? My current wifi connections all have autoconnect turned on, as does the wifi device itself. Is it perhaps a power management or network configuration setting that I'm looking for?
>
> Thanks!
>
> David
It works for me after suspend (I did not try reboot) after configuring
a new Wifi connection via nm-connection-editor. Once I entered the
password in nm-connection-editor, it automatically (re)connects.
If it helps, I attach the output of
nmcli connection show 299e800a-4737-4b78-b018-0012a35f942e
Perhaps /var/log/messages tells us something? Perhaps one needs to
configure something for NM to print more debug info??
Regards,
Florian
[-- Attachment #2: nmcli-c-show.log --]
[-- Type: text/plain, Size: 4561 bytes --]
connection.id: Funknetzwerkverbindung 1
connection.uuid: 299e800a-4737-4b78-b018-0012a35f942e
connection.stable-id: --
connection.type: 802-11-wireless
connection.interface-name: wlp0s6f1u4
connection.autoconnect: ja
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.auth-retries: -1
connection.timestamp: 1570597034
connection.read-only: nein
connection.permissions: --
connection.zone: --
connection.master: --
connection.slave-type: --
connection.autoconnect-slaves: -1 (default)
connection.secondaries: --
connection.gateway-ping-timeout: 0
connection.metered: unbekannt
connection.lldp: default
802-11-wireless.ssid: Lolo
802-11-wireless.mode: infrastructure
802-11-wireless.band: --
802-11-wireless.channel: 0
802-11-wireless.bssid: --
802-11-wireless.rate: 0
802-11-wireless.tx-power: 0
802-11-wireless.mac-address: 00:C0:CA:82:ED:1D
802-11-wireless.cloned-mac-address: --
802-11-wireless.generate-mac-address-mask:--
802-11-wireless.mac-address-blacklist: --
802-11-wireless.mac-address-randomization:default
802-11-wireless.mtu: auto
802-11-wireless.seen-bssids: 38:10:D5:63:36:33
802-11-wireless.hidden: nein
802-11-wireless.powersave: 0 (default)
802-11-wireless-security.key-mgmt: wpa-psk
802-11-wireless-security.wep-tx-keyidx: 0
802-11-wireless-security.auth-alg: --
802-11-wireless-security.proto: --
802-11-wireless-security.pairwise: --
802-11-wireless-security.group: --
802-11-wireless-security.pmf: 0 (default)
802-11-wireless-security.leap-username: --
802-11-wireless-security.wep-key0: <hidden>
802-11-wireless-security.wep-key1: <hidden>
802-11-wireless-security.wep-key2: <hidden>
802-11-wireless-security.wep-key3: <hidden>
802-11-wireless-security.wep-key-flags: 0 (keine)
802-11-wireless-security.wep-key-type: unknown
802-11-wireless-security.psk: <hidden>
802-11-wireless-security.psk-flags: 0 (keine)
802-11-wireless-security.leap-password: <hidden>
802-11-wireless-security.leap-password-flags:0 (keine)
802-11-wireless-security.wps-method: 0 (default)
ipv4.method: auto
ipv4.dns: --
ipv4.dns-search: --
ipv4.dns-options: ""
ipv4.dns-priority: 0
ipv4.addresses: --
ipv4.gateway: --
ipv4.routes: --
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.ignore-auto-routes: nein
ipv4.ignore-auto-dns: nein
ipv4.dhcp-client-id: --
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname: ja
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.never-default: nein
ipv4.may-fail: ja
ipv4.dad-timeout: -1 (default)
ipv6.method: auto
ipv6.dns: --
ipv6.dns-search: --
ipv6.dns-options: ""
ipv6.dns-priority: 0
ipv6.addresses: --
ipv6.gateway: --
ipv6.routes: --
ipv6.route-metric: -1
ipv6.route-table: 0 (unspec)
ipv6.ignore-auto-routes: nein
ipv6.ignore-auto-dns: nein
ipv6.never-default: nein
ipv6.may-fail: ja
ipv6.ip6-privacy: 0 (deaktiviert)
ipv6.addr-gen-mode: stable-privacy
ipv6.dhcp-send-hostname: ja
ipv6.dhcp-hostname: --
ipv6.token: --
proxy.method: none
proxy.browser-only: nein
proxy.pac-url: --
proxy.pac-script: --
prev parent reply other threads:[~2019-10-09 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 22:48 NetworkManager does not autoconnect wifi after boot or wake David Wilson
2019-10-09 4:56 ` pelzflorian (Florian Pelz) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191009045627.dmb23di2ujfpxkw5@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=david@daviwil.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).