You can see the kernel command line adjustments here: # cat /boot/nf Network device naming #īy default, most images come with systemd’s predictable network naming disabled. Once it starts pinging and you’re able to log in, start following the guide below. To get started, head on over to the Rackspace Cloud control panel and build a compute-1 OnMetal server and choose Fedora 22 as your operating system. They’re also quite fast and always fun for experiments. Rackspace’s OnMetal Servers are a good place to test since they have bonded networks configured by default. However, the documentation on systemd-networkd with bonding is a bit lacking (but I have a pull request pending for that). How can I achieve this, in Ubuntu 12.I’ve written about systemd-networkd in the past and how easy it can be to set up new network devices and tunnels. Is using different MAC address in a single bonded interface a common requirement? Their "real" MAC addresses are (from cat /proc/net/bonding/bond0): The network admin has told me that the Juniper layer 2 switches (into which the server is plugged) need each of the bonded NICs to have their own unique MAC address, in order to prevent problems with multicast. TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
TX packets:1991772 errors:0 dropped:0 overruns:0 carrier:0 RX packets:2880650 errors:0 dropped:0 overruns:0 frame:0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
TX packets:1991774 errors:0 dropped:0 overruns:0 carrier:0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 I have a bonded interface: bond0 Link encap:Ethernet HWaddr d4:ae:52:ce:32:4e
0 kommentar(er)
