Ubuntu Server同时使用WiFi与以太网时WiFi失效的问题排查求助

各位好，我遇到一个困扰已久的问题，希望能得到大家的帮助：

我有一台运行Ubuntu Server 22.04.3的主机，WiFi适配器的IP是192.168.1.111，平时通过SSH连接完全正常。最近我通过/etc/netplan/50-cloud-init.yaml配置了一个以太网连接，静态IP设为192.168.2.22，用来连接同网段的相机（IP 192.168.2.64）。但只要插上以太网网线，WiFi就会断开，而且一直无法自动恢复。现在我只能通过以太网SSH登录主机，但这样就没法访问外网了，非常影响使用。

我已经尝试了以下排查步骤，但都没有解决问题：

• 检查BIOS中是否有WiFi/以太网相关的优先级设置，没找到相关选项
• 在网络管理器的IPv4选项卡中勾选了“仅将此连接用于其自身网络上的资源”，对应的连接配置文件里也设置了never-default=true（因为配置网关的话会提示和never-default不兼容，所以没配网关）
• 调整了WiFi连接的优先级，让它高于以太网

下面是我的相关配置和命令输出：

以太网连接配置文件内容 #

[connection]
id=Ethernet connection 1
uuid=8eac2307-8e13-4dca-ae46-d45552704db5
type=ethernet
interface-name=enp2s0

[ethernet]
mac-address=64:00:6A:16:A5:66

[ipv4]
address1=192.168.2.22/24
method=manual
never-default=true

[ipv6]
addr-gen-mode=stable-privacy
method=ignore

[proxy]

ifconfig 输出 #

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:99ff:fea7:7a72  prefixlen 64  scopeid 0x20<link>
        ether 02:42:99:a7:7a:72  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 43  bytes 6487 (6.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.22  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::6600:6aff:fe16:a566  prefixlen 64  scopeid 0x20<link>
        ether 64:00:6a:16:a5:66  txqueuelen 1000  (Ethernet)
        RX packets 709  bytes 68874 (68.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 567  bytes 67735 (67.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 228  bytes 20303 (20.3 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 228  bytes 20303 (20.3 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vetha1df66d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::9476:cbff:fe3f:7c70  prefixlen 64  scopeid 0x20<link>
        ether 96:76:cb:3f:7c:70  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 74  bytes 10522 (10.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.111  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::f70b:d185:5201:b9f2  prefixlen 64  scopeid 0x20<link>
        ether a4:c4:94:38:f2:de  txqueuelen 1000  (Ethernet)
        RX packets 240  bytes 22054 (22.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 86  bytes 11016 (11.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ip a s 输出 #

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: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 64:00:6a:16:a5:66 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.110/24 brd 192.168.1.255 scope global enp2s0
       valid_lft forever preferred_lft forever
    inet 192.168.2.22/24 brd 192.168.2.255 scope global enp2s0
       valid_lft forever preferred_lft forever
    inet6 fe80::6600:6aff:fe16:a566/64 scope link
       valid_lft forever preferred_lft forever
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a4:c4:94:38:f2:de brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.111/24 brd 192.168.1.255 scope global noprefixroute wlp3s0
       valid_lft forever preferred_lft forever
    inet6 fe80::f70b:d185:5201:b9f2/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:04:6a:8b:e6 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:4ff:fe6a:8be6/64 scope link
       valid_lft forever preferred_lft forever
6: veth45f0596@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether ba:4b:4b:c8:ae:df brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::b84b:4bff:fec8:aedf/64 scope link
       valid_lft forever preferred_lft forever

ip r s 输出 #

default via 192.168.1.1 dev wlp3s0 proto static metric 600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.111 metric 600
192.168.2.0/24 dev enp2s0 proto kernel scope link src 192.168.2.22

另外还有几个奇怪的点：

• 登录GUI时，以太网连接显示“从未使用”，但我明明是通过它SSH登录的
• 192.168.1.110是我之前给以太网网卡设的IP，已经删掉了但还在ip a输出里
• 之前以太网也有一条到网关的路由，我已经删除了，但问题依旧

请问各位，我还有哪些可以尝试的排查或解决方法吗？

备注：内容来源于stack exchange，提问作者Tam