After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791692 - vpn: Could not find source connection when network booting
vpn: Could not find source connection when network booting
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: VPN (general)
1.10.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-12-17 02:04 UTC by don
Modified: 2020-11-12 14:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description don 2017-12-17 02:04:41 UTC
In network booting the linux kernel sets up eth0.  When I upgraded from nm
1.8.4 to 1.10 my VPN's broke with reason="Could not find source
connection."  Running 'nmcli connection' shows that eth0 is managed
under both 1.8.4 and 1.10, so I'm not sure why it can't find a connection for VPN's to use.
Comment 1 Beniamino Galvani 2018-01-19 09:07:17 UTC
(In reply to don from comment #0)
> In network booting the linux kernel sets up eth0.  When I upgraded from nm
> 1.8.4 to 1.10 my VPN's broke with reason="Could not find source
> connection."  Running 'nmcli connection' shows that eth0 is managed
> under both 1.8.4 and 1.10, so I'm not sure why it can't find a connection
> for VPN's to use.

Please paste the output of "nmcli; nmcli c; ip a; ip r".
Comment 2 Bruno Friedmann 2018-02-18 13:21:54 UTC
I've now a non working Networkmanager 1.10 and openvpn (using the plasma nm applet it segv NetworkManager).

Trying to use the nmcli I got those results

nmcli; nmcli c; ip a; ip r
eth0: connected to eth0
        "Intel Ethernet Connection (2) I219-LM"
        ethernet (e1000e), F8:CA:B8:21:09:E7, hw, mtu 1500
        inet4 10.26.8.2/24
        route4 0.0.0.0/0
        route4 10.26.8.0/24
        inet6 2a02:121e:34b5:2000:487b:1c1d:2c76:9746/64
        inet6 fe80::dcc5:ce13:7ffa:2b69/64
        route6 2a02:121e:34b5:2000::/64
        route6 fe80::/64
        route6 fe80::/64
        route6 ::/0
        route6 ff00::/8

cdc-wdm0: disconnected
        "cdc-wdm0"
        2 connections available
        gsm (cdc_mbim, qcserial), hw

wlan0: unavailable
        "Intel Wireless 8260"
        wifi (iwlwifi), A4:34:D9:10:E6:D6, hw, mtu 1500

vboxnet0: unmanaged
        "vboxnet0"
        ethernet (vboxnet), 0A:00:27:00:00:00, hw, mtu 1500

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 10.26.8.1 176.31.224.222
        domains: labaroche.ioda.net
        interface: eth0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(5) manual pages for complete usage details.
NAME                       UUID                                  TYPE      DEVICE 
eth0                       be0c51c7-a499-4533-a224-ef8e96621b59  ethernet  eth0   
AccorHotels-Guests         32f1436c-1d06-43c7-b567-6ed3715cbecd  wifi      --     
Salt                       63228242-6404-4c20-93e2-9e2c30b0b857  gsm       --
Vodafone                   af2ae9a8-f4c2-4716-8d2e-38704961bb50  gsm       --
_SNCF_WIFI_INOUI           acee23b1-f1de-4cf5-b54c-53039e239ae9  wifi      --
edf-eth0                   7daab8cc-c306-4e05-a03d-ae49fa0b3b4d  ethernet  --
edf-secure-pulse           2ec47000-9f0a-4dcc-9014-5568cb20262c  vpn       --
eth0                       b63d1321-0e49-4464-85f1-a4e56fb2fadd  ethernet  --
vpn-botta                  3e125064-5541-4e6f-8904-427fe62a96b7  vpn       --
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether f8:ca:b8:21:09:e7 brd ff:ff:ff:ff:ff:ff
    inet 10.26.8.2/24 brd 10.26.8.255 scope global dynamic noprefixroute eth0
       valid_lft 86185sec preferred_lft 86185sec
    inet6 2a02:121e:34b5:2000:487b:1c1d:2c76:9746/64 scope global dynamic noprefixroute
       valid_lft 86187sec preferred_lft 14187sec
    inet6 fe80::dcc5:ce13:7ffa:2b69/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a4:34:d9:10:e6:d6 brd ff:ff:ff:ff:ff:ff
5: wwp0s20f0u2i12: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether de:01:94:78:d8:21 brd ff:ff:ff:ff:ff:ff
6: vboxnet0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 192.168.56.1/24 brd 192.168.56.255 scope global vboxnet0
       valid_lft forever preferred_lft forever
    inet6 fe80::800:27ff:fe00:0/64 scope link
       valid_lft forever preferred_lft forever
default via 10.26.8.1 dev eth0 proto dhcp metric 100
10.26.8.0/24 dev eth0 proto kernel scope link src 10.26.8.2 metric 100
192.168.56.0/24 dev vboxnet0 proto kernel scope link src 192.168.56.1 linkdown


Feb 18 14:17:53 qt-kt.labaroche.ioda.net nm-dispatcher[11172]: req:3 'connectivity-change': start running ordered scripts...
Feb 18 14:18:43 qt-kt.labaroche.ioda.net NetworkManager[11167]: <info>  [1518959923.4801] manager: logging: level 'DEBUG' domains 'PLATFORM,RFKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,IP4,IP6,AUTOIP4,DNS,VPN,SHARING,SUPPLICANT,AGENTS,SETTINGS,SUSPEND,CORE,DEVICE,OLPC,INFINIBAND,FIREWALL,ADSL,BOND,VLAN,BRIDGE,TEAM,CONCHECK,DCB,DISPATCH,AUDIT,SYSTEMD,PROXY'
Feb 18 14:18:48 qt-kt.labaroche.ioda.net NetworkManager[11167]: <debug> [1518959928.4462] agent-manager: req[0x55d88dee0e40, :1.592/nmcli-connect/0]: requesting permissions
Feb 18 14:18:48 qt-kt.labaroche.ioda.net NetworkManager[11167]: <debug> [1518959928.4463] agent-manager: req[0x55d88dee0e40, :1.592/nmcli-connect/0]: agent registered
Feb 18 14:18:48 qt-kt.labaroche.ioda.net NetworkManager[11167]: <debug> [1518959928.4463] policy: re-enabling autoconnect for all connections (only clear no-secrets flag)
Feb 18 14:18:48 qt-kt.labaroche.ioda.net NetworkManager[11167]: <debug> [1518959928.4472] create NMAuditManager singleton (0x7f31cc001960)
Feb 18 14:18:48 qt-kt.labaroche.ioda.net NetworkManager[11167]: <info>  [1518959928.4473] audit: op="connection-activate" uuid="3e125064-5541-4e6f-8904-427fe62a96b7" name="vpn-botta" pid=11395 uid=0 result="fail" reason="Could not find source connection."
Feb 18 14:18:48 qt-kt.labaroche.ioda.net NetworkManager[11167]: <debug> [1518959928.4483] agent-manager: req[0x55d88dee0e40, :1.592/nmcli-connect/0]: agent unregistered or disappeared
Comment 3 Bruno Friedmann 2018-02-18 13:28:00 UTC
Related SEGV : https://bugzilla.opensuse.org/show_bug.cgi?id=1081430
Comment 4 André Klapper 2020-11-12 14:33:00 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).