在Ubuntu 17.10上通过netplan进行网卡绑定

尝试使用netplan在Ubuntu 17.10的NIC团队：

network: version: 2 ethernets: switchports: match: macaddress: 00:15:5d:ec:d3:07 macaddress: 00:15:5d:ec:d3:08 wakeonlan: true bridges: bond0: interfaces: [switchports] addresses: [172.30.1.10/18] gateway4: 172.30.0.1

应用后不能ping网关或从其他networking节点ping Ubuntu服务器。我的预感是我错过了简单的东西，但阅读文档和其他示例我不知所措：/

这里的ip addr show ：

 [...] 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:15:5d:ec:d3:07 brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 00:15:5d:ec:d3:08 brd ff:ff:ff:ff:ff:ff 4: bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether ae:1e:0c:06:21:8c brd ff:ff:ff:ff:ff:ff inet 172.30.1.10/18 brd 172.30.63.255 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::ac1e:cff:fe06:218c/64 scope link valid_lft_forever preferred_lft forever [...]

更新1：如同马克·瓦格纳指出的那样，将bridges变成bonds: 。

Ping网关现在正在工作，但DNSparsing不是。

 ping google.com ping: google.com: Temporary failure in name resolution

尝试使用netplan手动设置名称服务器，但仍然没有运气：

 network: version: 2 .... gateway4: 172.30.0.1 nameservers: addresses: [172.30.0.1, 8.8.8.8]

这里是cat /proc/net/bonding/bond0 ：

 Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (ms): 0 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth1 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:15:5d:ec:d3:08 Slave queue ID: 0

更新2：重启计算机的固定DNS

要求的三个修复：

改变了bridges bonds 。
新增名称服务器
为了真正的NIC组合弹性，将两个NIC分成bond0单独的接口

最后的networking计划：

 network: version: 2 ethernets: eth0: match: macaddress: 00:15:5d:ec:d3:07 wakeonlan: true eth1: match: macaddress: 00:15:5d:ec:d3:08 wakeonlan: true bonds: bond0: interfaces: [eth0, eth1] addresses: [172.30.1.10/18] gateway4: 172.30.0.1 nameservers: addresses: [172.30.0.1]