You are not logged in.
Hi folks,
every time I start my machine I need to manually connect to the network despite NM being configured to auto connect.
Please see here:
$ nmcli -f name,autoconnect connection
NAME AUTOCONNECT
Azure VPN yes
Wired (Dock) yes
tun0 no
And also, both VPN and wired network have:
All users may connect to this network
Any idea of how to fix this?
Thank you.
Last edited by lotor57917 (2022-11-29 10:19:35)
Offline
Does this apply here?
If not can we see the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
Thanks!
Para todos todo, para nosotros nada
Offline
Does this apply here?
If not can we see the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
Thanks!
The article seems to worry only about VPN not connecting, my problem is a bit different given the whole connection does not work. However I can try that and give feedback, maybe failing the VPN is also failing the whole connection.
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
Thank you for the help
Offline
That's almost certainly not the entirety of the command and filtering it for NetworkManager misses the point of why we want to see the output, post all of it
Offline
Post NetworkManager's log.
journalctl -b -u NetworkManager
Offline
@Head_on_a_Stick suggestion was spot on.
I tried to reboot after unticking "Automatically connect to this VPN" and that worked. Thanks. I will set up the dispatcher to connect as per wiki.
Offline