%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% STATIC OK! $ ll /etc/systemd/network/ ... enp3s0.network $ cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Network] Address=192.168.2.2/24 Gateway=192.168.2.1 DNS=192.168.2.1 # journalctl -b -u systemd-networkd -- Logs begin at ... ... systemd-networkd[630]: enp3s0: carrier on ... systemd-networkd[630]: enp3s0: link configured $ ifconfig enp3s0 enp3s0: flags=... inet 192.168.2.2 netmask 255.255.255.0 broadcast 192.168.2.255 inet6 ... ether ... ... %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% BRIDGED !? $ ll /etc/systemd/network/ ... bridge0.netdev ... enp3s0.network $ cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Network] Address=192.168.2.2/24 Gateway=192.168.2.1 DNS=192.168.2.1 Bridge=bridge0 $ cat /etc/systemd/network/bridge0.netdev [NetDev] Name=bridge0 Kind=bridge # journalctl -b -u systemd-networkd.service -- Logs begin at ... $ ifconfig enp3s0 enp3s0: flags=... ether ... ... $ brctl show bridge name bridge id STP enabled interfaces bridge0 8000.000000000000 no %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% # grep -P '(?=.*bridge)(?=.*udevd)' /var/log/messages Mar 2 11:58:23 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 12:17:48 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 15:30:22 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 15:43:30 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 16:20:23 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 16:59:46 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 17:07:11 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 17:21:28 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 17:25:10 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 17:31:31 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 17:45:50 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 22:01:00 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 22:04:25 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 22:07:43 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 22:13:41 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 22:16:01 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 22:18:01 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 22:22:34 localhost systemd-udevd: Could not apply link config to bridge0 Mar 2 22:26:21 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 12:41:36 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 14:00:57 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 14:05:28 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 14:11:01 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 14:13:55 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 19:13:29 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 22:50:51 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 23:13:24 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 23:49:55 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 23:55:36 localhost systemd-udevd: Could not apply link config to bridge0 Mar 3 23:55:36 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 00:01:02 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 01:30:19 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 02:01:35 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 10:53:55 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 10:57:12 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 11:00:52 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 11:03:38 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 11:24:47 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 11:36:35 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 11:52:22 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 11:57:44 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 12:01:37 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 13:08:03 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 13:54:37 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 14:52:27 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 14:52:27 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 16:28:29 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 16:43:03 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 17:30:47 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 17:34:10 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 17:43:09 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 17:50:01 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 17:55:57 localhost systemd-udevd: Could not apply link config to bridge0 Mar 4 18:00:50 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 00:49:40 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 00:59:40 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 11:27:32 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 11:45:15 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 11:45:15 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 15:49:29 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 17:13:08 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 17:53:36 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 17:59:11 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 19:16:28 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 20:28:28 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 20:58:29 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 21:02:54 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 21:05:41 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 21:08:18 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 21:11:22 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 21:17:12 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 21:35:08 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 21:42:58 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 22:01:19 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 22:17:19 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 22:38:00 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 23:05:38 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 23:09:27 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 23:12:53 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 23:12:53 localhost systemd-udevd: Could not apply link config to bridge0 Mar 5 23:19:26 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 04:40:09 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 11:23:34 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 11:38:19 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 11:50:25 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 11:54:29 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 12:17:14 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 13:43:06 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 15:44:07 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 15:57:49 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 16:06:39 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 17:20:28 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 17:36:57 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 17:54:10 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 18:39:17 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 18:44:08 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 18:54:37 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 18:57:25 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 19:12:52 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 19:20:04 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 19:26:05 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 19:35:23 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 20:44:18 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 21:00:23 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 21:05:25 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 21:10:14 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 21:26:58 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 21:31:40 localhost systemd-udevd: Could not apply link config to bridge0 Mar 6 22:05:22 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 01:55:05 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 02:19:11 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 02:25:39 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 04:02:35 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 04:09:57 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 04:40:06 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 04:49:05 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 04:56:29 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 04:59:41 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 15:05:23 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 15:51:19 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 16:01:00 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 16:04:54 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 18:01:44 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 18:03:35 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 18:45:52 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 19:07:14 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 19:07:14 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 19:14:50 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 22:05:06 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 22:34:44 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 22:54:53 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 22:58:34 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 23:02:28 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 23:06:33 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 23:14:42 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 23:33:48 localhost systemd-udevd: Could not apply link config to bridge0 Mar 7 23:40:05 localhost systemd-udevd: Could not apply link config to bridge0 Mar 8 00:01:59 localhost systemd-udevd: Could not apply link config to bridge0 Mar 8 00:08:09 localhost systemd-udevd: Could not apply link config to bridge0 Mar 8 00:14:08 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 01:34:36 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 02:10:45 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 02:13:47 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 01:34:36 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 02:10:45 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 02:13:47 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 02:27:55 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 02:31:56 localhost systemd-udevd[394]: Could not apply link config to bridge0 Mar 9 02:33:39 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 02:39:45 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 03:23:49 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 03:27:34 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 03:33:56 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 03:48:37 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 04:03:52 localhost systemd-udevd[381]: Could not apply link config to bridge0 Mar 9 04:11:44 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 04:15:56 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 05:02:04 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 05:05:15 localhost systemd-udevd[396]: Could not apply link config to bridge0 Mar 9 05:11:14 localhost systemd-udevd: Could not apply link config to bridge0 Mar 9 05:14:26 localhost systemd-udevd: Could not apply link config to bridge0 # SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd timestamp of '/etc/systemd/network' changed bridge0: creating netdev enp1s9: link (with ifindex 2) added enp3s0: found matching network '/etc/systemd/network/enp3s0.network' enp3s0: requesting link status enp3s0: enslaving by 'bridge0' enp3s0: link (with ifindex 3) added bridge0: link (with ifindex 4) added lo: link (with ifindex 1) added Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 error=n/a enp3s0: got link state enp3s0: link status updated: 00000000 -> 0x00001002 Got message type=method_return sender=org.freedesktop.DBus destination=:1.30 object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.30 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 error=n/a ... $ ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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: enp1s9: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether ... brd ff:ff:ff:ff:ff:ff 3: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether ... brd ff:ff:ff:ff:ff:ff 4: bridge0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default link/ether 62:35:26:91:ec:db brd ff:ff:ff:ff:ff:ff ... ^CReceived SIGINT. Assertion 's->event->state != SD_EVENT_FINISHED' failed at ../src/libsystemd/sd-event/sd-event.c:1240, function sd_event_source_set_enabled(). Ignoring. Assertion 's->event->state != SD_EVENT_FINISHED' failed at ../src/libsystemd/sd-event/sd-event.c:1240, function sd_event_source_set_enabled(). Ignoring. Assertion 's->event->state != SD_EVENT_FINISHED' failed at ../src/libsystemd/sd-event/sd-event.c:1240, function sd_event_source_set_enabled(). Ignoring.
# rpm -q systemd systemd-209-1.fc21.x86_64 http://kojipkgs.fedoraproject.org//work/tasks/9777/6549777/systemd-209-1.fc21.src.rpm # dmesg -t | grep -i systemd random: systemd urandom read with 37 bits of entropy available systemd[1]: systemd 209 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP) systemd[1]: Running in initial RAM disk. systemd[1]: Set hostname to <localhost.localdomain>. systemd-fstab-g (81) used greatest stack depth: 5432 bytes left systemd[1]: Expecting device dev-disk-by\x2duuid-....device... systemd[1]: Expecting device dev-disk-by\x2duuid-....device... systemd[1]: Expecting device dev-disk-by\x2duuid-....device... systemd[1]: Starting Timers. systemd[1]: Reached target Timers. systemd[1]: Starting Dispatch Password Requests to Console Directory Watch. systemd[1]: Started Dispatch Password Requests to Console Directory Watch. systemd[1]: Starting Paths. systemd[1]: Reached target Paths. systemd[1]: Starting -.slice. systemd[1]: Created slice -.slice. systemd[1]: Starting udev Kernel Socket. systemd[1]: Listening on udev Kernel Socket. systemd[1]: Starting Journal Socket. systemd[1]: Listening on Journal Socket. systemd[1]: Starting System Slice. systemd[1]: Created slice System Slice. systemd[1]: Starting system-systemd\x2dfsck.slice. systemd[1]: Created slice system-systemd\x2dfsck.slice. systemd[1]: Starting dracut cmdline hook... systemd[1]: Starting Create list of required static device nodes for the current kernel... systemd[1]: Starting Load Kernel Modules... systemd[1]: Starting Journal Service... systemd[1]: Started Journal Service. systemd-journald[106]: Vacuuming done, freed 0 bytes systemd-modules (102) used greatest stack depth: 4776 bytes left systemd-udevd[201]: starting version 209 systemd-fstab-g (274) used greatest stack depth: 4072 bytes left systemd-udevd (217) used greatest stack depth: 3672 bytes left systemd-journald[106]: Received SIGTERM from PID 1 (systemd). systemd-readahead[339]: Bumped block_nr parameter of 8:0 to 20480. This is a temporary hack and should be removed one day. systemd-journald[343]: Vacuuming done, freed 0 bytes systemd-udevd[365]: starting version 209 systemd-udevd[371]: renamed network interface eth0 to enp1s6 systemd-udevd[379]: renamed network interface eth1 to enp1s9 systemd-udevd[381]: renamed network interface eth2 to enp3s0 systemd-journald[343]: Received request to flush runtime journal from PID 1 systemd-udevd (368) used greatest stack depth: 3368 bytes left systemd-udevd[366]: Could not apply link config to bridge0 systemd-sysctl[585]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/99-sysctl.conf'. # systemctl status systemd-networkd.service systemd-networkd.service - Network Service Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; static) Active: active (running) since Sun 2014-03-09 22:27:58 CET; 47s ago Docs: man:systemd-networkd.service(8) Main PID: 580 (systemd-network) Status: "Processing requests..." CGroup: /system.slice/systemd-networkd.service └─580 /usr/lib/systemd/systemd-networkd # journalctl -b -u systemd-networkd.service -- Logs begin at Wed 2013-08-21 23:26:56 CEST, end at Sun 2014-03-09 22:28:31 CET. -- # ifconfig 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 0 (Local Loopback) RX packets 2 bytes 140 (140.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 140 (140.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collision # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default link/ether 76:fe:b7:e1:34:1a brd ff:ff:ff:ff:ff:ff 3: enp1s6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:11:22:33:44:55 brd ff:ff:ff:ff:ff:ff 4: enp1s9: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:11:33:55:77:99 brd ff:ff:ff:ff:ff:ff 5: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:22:44:66:88:aa brd ff:ff:ff:ff:ff:ff 6: bridge0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default link/ether 6e:27:92:12:b2:5f brd ff:ff:ff:ff:ff:ff # brctl show bridge name bridge id STP enabled interfaces bridge0 8000.000000000000 no # ll /etc/systemd/network/ total 8 -rw-r--r-- 1 root root 34 Mar 9 03:20 bridge0.netdev -rw-r--r-- 1 root root 105 Mar 9 22:23 enp1s6.network # cat /etc/systemd/network/enp1s6.network [Match] Name=enp1s6 [Network] Address=192.168.2.2/24 Gateway=192.168.2.1 DNS=192.168.2.1 Bridge=bridge0 # cat /etc/systemd/network/bridge0.netdev [NetDev] Name=bridge0 Kind=bridge # ll /usr/lib/systemd/network/ total 4 -rw-r--r--. 1 root root 73 Mar 9 22:06 99-default.link # cat /usr/lib/systemd/network/99-default.link [Link] NamePolicy=database onboard slot path MACAddressPolicy=persistent
Created attachment 873647 [details] systemd-networkd 211 bridge fluctuate
What next release!?
Created attachment 875193 [details] systemd-networkd netdev-bridge git-f8294e4
Created attachment 875621 [details] systemd-networkd - bridge OK
Created attachment 877526 [details] systemd-networkd bridge dhcp OK
Created attachment 878306 [details] systemd-networkd bridge dhcp - git commit 5ba6e09
OK, this is the last commit that works properly related to DHCP bridging, commit 3dd215e056ee9ff23175eca66686ff9b7a566dbf Author: Tom Gundersen <teg> Date: Sun Mar 23 21:45:46 2014 +0100 sd-rtnl: add sd_rtnl_message_enter_container() Extend rta_offset_tb into a stack of offset tables, one for each parent of the current container, and make sd_rtnl_message_{enter,exit}_container() pop/push to this stack. Also make sd_rtnl_message_rewind() parse the top-level container, and use this when reading a message from the socket. This changes the API by dropping the now redundant sd_rtnl_message_read() method.
Hm, do you mean that that's the first broken commit? It's a big change, so I can easily believe that I broke something there, but after that I don't see any obvious candidates...
commit 3dd215e056ee9ff23175eca66686ff9b7a566dbf is OK. All the above, starting with commit d39edfc72f9296078a18014627bf0a2543b60627 Author: Tom Gundersen <teg> Date: Mon Mar 24 00:07:46 2014 +0100 networkd: netdev - verify that newlink messages has the expected kind is broken, related to DHCP bridging.
Created attachment 879257 [details] networkd git commit d39edfc reversed - bridge dhcp OK
Created attachment 879259 [details] networkd log - git commit d39edfc reversed - bridge dhcp OK
Created attachment 879706 [details] networkd log - git commit 9f5bbfe - bridge dhcp
Created attachment 879714 [details] networkd log - git commit 9f5bbfe with d39edfc reversed - bridge dhcp OK
Created attachment 880039 [details] networkd log - git aef0768 - bridge dhcp
Created attachment 880456 [details] networkd log - git 2ad75 - bridge dhcp
Created attachment 881142 [details] systemd-networkd - git 2086120 - bonding & bridge dhcp
This article is quite optimistic, "Round-robin bonding (mode 0) with virtualization breaks networking for guests. Why? How can I work around it?" https://access.redhat.com/site/articles/16039 With the "bridged bonding" the only usable bonding mode[1] for the libvirt domain(guest) is the 'active-backup 1'. /etc/modprobe.d/bonding.conf: options bonding mode=1 # bonding mode of operation: # 0 for balance-rr # 1 for active-backup # 2 for balance-xor # 3 for broadcast # 4 for 802.3ad # 5 for balance-tlb # 6 for balance-alb (charp) /sys/class/net/bond0/bonding/mode & /sys/devices/virtual/net/bond0/bonding/mode: active-backup 1 # brctl show bridge name bridge id STP enabled interfaces bridge0 8000.001234567830 no bond0 # bondctl detail bond0 Bonding Master: bond0 Oper State: up Slaves: enp3s0 enp1s9 Active Slave: enp3s0 Mode: active-backup 1 Monitor: No monitoring enabled [1] http://www.linux-kvm.org/page/HOWTO_BONDING#Modes And that's it. Tom, good luck with the project!
Created attachment 887928 [details] systemd-networkd git commit 66aaf85 bridge DHCP
Created attachment 888512 [details] systemd-networkd gitcommit 7d95c77 bridge DHCP
Hi poma, Thanks a lot for all your testing (sorry that I haven't gotten back to you before, but I read all your posts :) ). From comment #20 it seems that bridging is working for you as expected? If there are other issues may I ask you to open separate reports? Cheers, Tom
Created attachment 888713 [details] systemd-networkd gitcommit 26e376b bond & bridge DHCP There is a 15 second DHCP lag in this bond-bridge scheme.
(In reply to Tom Gundersen from comment #21) > Hi poma, > > Thanks a lot for all your testing (sorry that I haven't gotten back to you > before, but I read all your posts :) ). > > From comment #20 it seems that bridging is working for you as expected? If > there are other issues may I ask you to open separate reports? > > Cheers, > > Tom Hey Tom, yeah simple bridging is working OK. Do you mean, per each new issue goes a new report, regardless if it is an issue of the same category?
(In reply to poma from comment #22) > Created attachment 888713 [details] > systemd-networkd gitcommit 26e376b bond & bridge DHCP > > > There is a 15 second DHCP lag in this bond-bridge scheme. This variable lag emerges is due to the use of debug kernel i.e. 3.15.0-0.rc2.git1.1.fc21.x86_64. However, it is not within nodebug kernel i.e. 3.15.0-0.rc2.git0.1.fc21.x86_64. Anyway this never happened before, i.e. before the last group of networkd commits. 3.15.0-0.rc2.git1.1.fc21.x86_64(debug kernel): ... :45 : DHCP CLIENT (0xe3d194ac): DISCOVER :45 : DHCP CLIENT (0xe3d194ac): OFFER :45 : DHCP CLIENT (0xe3d194ac): REQUEST (requesting) :45 : DHCP CLIENT (0xe3d194ac): ACK :45 : DHCP CLIENT (0xe3d194ac): lease expires in 9min 58.982809s :45 : DHCP CLIENT (0xe3d194ac): T2 expires in 8min 42.678604s :45 : DHCP CLIENT (0xe3d194ac): T1 expires in 5min 351.006ms ... 9 seconds lag ... :54 : bridge0: DHCPv4 address 192.168.2.35/24 via 192.168.2.1 :54 : bridge0: setting addresses :55 : bridge0: addresses set :55 : bridge0: setting routes :55 : bridge0: routes set :55 : bridge0: link configured
Created attachment 889475 [details] systemd git bf50056 bond & bridge DHCP