![]() Valid_lft 43198sec preferred_lft 43198sec ![]() Now, watch what happens if we restart the networking: # systemctl restart networking The important detail is that bond0 and enp0s8 has a made up MAC address ofĤ2:e2:89:5b:6d:de, you can also see enp0s8 has a permaddr 08:00:27:e2:37:5f field, signifying that it is currently having it's MACĪddress overwritten by the made up address on bond0. Inet6 fe80::a00:27ff:fe19:f33e/64 scope linkģ: enp0s8: mtu 1500 qdisc pfifo_fast master bond0 state UNKNOWN group default qlen 1000 Valid_lft 43128sec preferred_lft 43128sec Now, upon restarting the machine you will see something like this: # ip aġ: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 Ignore it below, is is not interesting for our purposes) andĮnp0s8 is an unused interface that will act as the bonding slave. where enp0s3 is the interface I am reaching the machine over (so just In my case it ended up looking like so: # This file describes the network interfaces available on your system To see it in action all you need to do is to install ifenslave and then modify /etc/network/interfaces to include bond settings as described in the Official Debian Configuration Example (of course with some tweaks to match your available interfaces etc). Why would a plain restart of the networking not result in aĬonsistent outcome when compared with the state after a machine reboot? Preparing a machine for testing ( systemctl restart networking) and noticed that the MAC address used by the At one point we tried restarting the networking service The other day a colleague and I were experimenting with bonding interfaces on a Debianīullseye machine. How can I achieve this, in Ubuntu 12.A tale of bonding interfaces, Linux kernel debugging, eBPF tools and netlink messages. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |