Comment 6 for bug 2019048

Revision history for this message
ROG (xgates) wrote (last edit ):

I found the culprit!

/usr/lib/NetworkManager/conf.d/
20-connectivity-ubuntu.conf
uri=http://connectivity-check.ubuntu.com./

I commented this out;

#uri=http://connectivity-check.ubuntu.com./

Then I rebooted, and now, no matter which set of ufw rules I am using, OpenVPN or Wireguard, the nm applet always displays the Wired Connection as white when offline line from OpenVPN or Wireguard. Is this the correct behaviour we want to see, or should it always show as grayed out and a question mark, until making the VPN connection?

I've attached a screen shot, that now shows the Wired applet connection always white, when using ufw rules for OpenVPN and Wireguard, to route only connectivity over these, and not allow to go online, unless connected to them.

Also with uri=http://connectivity-check.ubuntu.com./ commented out #

Now nmcli networking connectivity shows full when using Wireguard instead of limited before.

nmcli networking connectivity
full

nmcli connection
NAME UUID TYPE DEVICE
Wired Connection 0c288f04-eb9d-309e-b15a-6fde9e55c487 ethernet enp5s0
lo 1168dc16-3322-46e7-a17d-9f22291109a4 loopback lo
Wireguard b1aa9b00-6fab-43cc-aa38-f21efd136ed5 wireguard wg0
OpenVPN b6080992-6e7b-4f43-894a-0feaa287bd9f vpn --

nmcli device
DEVICE TYPE STATE CONNECTION
enp5s0 ethernet connected Wired Connection
lo loopback connected (externally) lo
wg0 wireguard connected Wireguard