为什么我的有线连接在 Ubuntu 18.04 上失败并出现 secondary-connection-failed ？

Question

当我的有线连接突然完全失败时，我正在更改我的 ufw 规则。即使禁用 ufw 后，每次我尝试连接有线连接时，它都会失败。

我能够启动到旧的 16.10 live USB，并且有线连接工作正常。

当我尝试连接后立即检查journalctl时，我得到以下信息：

Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1360] device (enp0s31f6): Activation: starting connection 'Wired connection 1' (01920e80-0c39-3968-ab5e-99dbba5f8e64) Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1363] audit: op="connection-activate" uuid="01920e80-0c39-3968-ab5e-99dbba5f8e64" name="Wired connection 1" pid=2481 uid=1000 result="su Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1368] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1373] manager: NetworkManager state is now CONNECTING Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1381] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1399] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1401] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds) Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1425] dhcp4 (enp0s31f6): dhclient started with pid 3406 Jul 06 09:22:54 mark-dev dhclient[3406]: DHCPREQUEST of 192.168.0.2 on enp0s31f6 to 255.255.255.255 port 67 (xid=0x70f92a1a) Jul 06 09:22:54 mark-dev dhclient[3406]: DHCPACK of 192.168.0.2 from 192.168.0.1 Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1707] dhcp4 (enp0s31f6): address 192.168.0.2 Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1707] dhcp4 (enp0s31f6): plen 24 (255.255.255.0) Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1708] dhcp4 (enp0s31f6): gateway 192.168.0.1 Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1708] dhcp4 (enp0s31f6): lease time 3600 Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1708] dhcp4 (enp0s31f6): hostname 'mark-dev' Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1708] dhcp4 (enp0s31f6): nameserver '192.168.0.1' Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1708] dhcp4 (enp0s31f6): domain name 'gateway' Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1708] dhcp4 (enp0s31f6): state changed unknown -> bound Jul 06 09:22:54 mark-dev avahi-daemon[1207]: Joining mDNS multicast group on interface enp0s31f6.IPv4 with address 192.168.0.2. Jul 06 09:22:54 mark-dev avahi-daemon[1207]: New relevant interface enp0s31f6.IPv4 for mDNS. Jul 06 09:22:54 mark-dev avahi-daemon[1207]: Registering new address record for 192.168.0.2 on enp0s31f6.IPv4. Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1720] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1726] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1727] policy: set 'Wired connection 1' (enp0s31f6) as default for IPv4 routing and DNS Jul 06 09:22:54 mark-dev NetworkManager[1266]: <warn> [1562368974.1742] policy: secondary connection 'eb2c7cac-ca3f-40c5-84b0-4ae23db66bdf' auto-activation failed: The connection doesn't exist. Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1745] device (enp0s31f6): state change: secondaries -> failed (reason 'secondary-connection-failed', sys-iface-state: 'managed') Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1746] manager: NetworkManager state is now CONNECTED_LOCAL Jul 06 09:22:54 mark-dev NetworkManager[1266]: <warn> [1562368974.1748] device (enp0s31f6): Activation: failed for connection 'Wired connection 1' Jul 06 09:22:54 mark-dev NetworkManager[1266]: <info> [1562368974.1751] device (enp0s31f6): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

关键似乎是 secondary-connection-failed 消息，但我不知道这意味着什么，也不知道它如何受到我用 ufw 更改的任何内容的影响。

我不知道什么可能导致此问题或如何解决它。

Answer 1

经过更多研究后，我发现第二次连接失败指的是我将网络管理器设置为在成功连接有线网络后自动连接的VPN。

我不确定它失败的确切原因，因为指定的 VPN 已正确设置。nm-connection-editor但是，我通过运行、输入有线连接设置并在选项卡Automatically connect to VPN when using this connection下取消选中来解决了该问题General。

这使得我的有线连接能够成功连接。然后我重新检查Automatically connect to VPN when using this connection并从下拉列表中选择一个 VPN。现在一切似乎都正常。