Ubuntu 20.04上带有netplan的保税nics不通过通信量

Question

我花了一个下午的时间试图在Ubuntu20.04服务器上绑定一些nics。键似乎是基于ip a和/proc/net/成键的，但是我只能点击键本身的ip，其他的东西都会返回无法到达的新工作。

netplan配置是

    network:
      ethernets:
        enp1s0:
          dhcp4: false
          dhcp6: false
          optional: true
        enp2s0:
          dhcp4: false
          dhcp6: false
          optional: true
      bonds:
        bond0:
          interfaces: [enp1s0, enp2s0]
          addresses: [192.168.44.173/24]
          gateway4: 192.168.44.1
          nameservers:
                    addresses: [8.8.8.8]
          parameters:
                  mode: active-backup
                  #mode: balance-alb
                  mii-monitor-interval: 1    
                  primary: enp1s0
    version: 2

当我应用这个配置时，我得到

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: enp1s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether 3a:16:23:70:af:55 brd ff:ff:ff:ff:ff:ff
3: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc mq master bond0 state DOWN group default qlen 1000
    link/ether 3a:16:23:70:af:55 brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3a:16:23:70:af:55 brd ff:ff:ff:ff:ff:ff
    inet 192.168.44.173/24 brd 192.168.44.255 scope global bond0
       valid_lft forever preferred_lft forever
    inet6 fe80::3816:23ff:fe70:af55/64 scope link 
       valid_lft forever preferred_lft forever
5: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none 
    inet6 fe80::20df:bfda:fa00:48e9/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever

它看起来是可以的，路由为

default via 192.168.44.1 dev bond0 proto static 
192.168.44.0/24 dev bond0 proto kernel scope link src 192.168.44.173 

和/proc/net/胶合/债券0作为

Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: enp1s0 (primary_reselect always)
Currently Active Slave: enp1s0
MII Status: up
MII Polling Interval (ms): 1
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0

Slave Interface: enp2s0
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: 00:18:7d:d7:e9:aa
Slave queue ID: 0

Slave Interface: enp1s0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:18:7d:d7:e9:a9
Slave queue ID: 0

我放弃了这一点，并试图回到与dhcp的单一接口，但现在nic出现了，但拒绝获得任何类型的地址(即使在重新启动时，它现在等待一个地址超过一分钟，然后继续没有地址)。

有人能指点我的方向吗？当然不会这么难的。

好的。

Answer 1

我认为问题一定是一个坏的arp表在其中一个开关或类似的东西。

在机器关机24小时后，我又回到了这里，它刚刚开始工作(包括动态地址和绑定的nics)。

感谢那些往里面看的人。

对于任何看上去的人来说，上面的配置实际上是起作用的。