Hello, OK I've managed to fix my networking problem, here is how I did it... Giovanni Biscuolo writes: [...] > The networking service is failing with this message (manually copied > here, please forgive mistakes): now that I can connect via SSH, I can copy the actual messages: --8<---------------cut here---------------start------------->8--- Jun 14 11:28:32 localhost vmunix: [ 6.258520] shepherd[1]: Starting service networking... Jun 14 11:28:32 localhost vmunix: [ 6.472949] shepherd[1]: Service networking failed to start. Jun 14 11:28:32 localhost vmunix: [ 6.474842] shepherd[1]: Exception caught while starting networking: (no-such-device "swws-bridge") Jun 14 11:28:32 localhost vmunix: [ 6.492344] shepherd[1]: Starting service networking... Jun 14 11:28:32 localhost vmunix: [ 6.509652] shepherd[1]: Exception caught while starting networking: (%exception #<&netlink-response-error errno: 17>) Jun 14 11:28:32 localhost vmunix: [ 6.510034] shepherd[1]: Service networking failed to start. --8<---------------cut here---------------end--------------->8--- > The strange thing is that all the configured interfaces: eno1 I truncated the list, the actual list of interfaces was (and is): --8<---------------cut here---------------start------------->8--- g@ane ~$ ip addre ls 1: lo: 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 global lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether b4:2e:99:c5:cc:1c brd ff:ff:ff:ff:ff:ff inet 162.55.88.253/24 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::b62e:99ff:fec5:cc1c/64 scope link valid_lft forever preferred_lft forever 3: swws-bridge: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:9b:c6:63 brd ff:ff:ff:ff:ff:ff inet 192.168.133.1/24 brd 192.168.133.255 scope global swws-bridge valid_lft forever preferred_lft forever 4: vnet0: mtu 1500 qdisc noqueue master swws-bridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:ff:e2:fd brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:feff:e2fd/64 scope link valid_lft forever preferred_lft forever 5: vnet1: mtu 1500 qdisc noqueue master swws-bridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:41:53:1e brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe41:531e/64 scope link valid_lft forever preferred_lft forever 6: vnet2: mtu 1500 qdisc noqueue master swws-bridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:3d:17:90 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe3d:1790/64 scope link valid_lft forever preferred_lft forever 7: vnet3: mtu 1500 qdisc noqueue master swws-bridge state UNKNOWN group default qlen 1000 link/ether fe:54:00:64:81:8f brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe64:818f/64 scope link valid_lft forever preferred_lft forever --8<---------------cut here---------------end--------------->8--- > Please find below the relevant parts of the configuration of my host. > > As you can see I've installed a libvirt daemon service (it is working) > with an autostarted (by libvirt) bridge interface named "swws-bridge" [...] > --8<---------------cut here---------------start------------->8--- [...] sorry I missed to add some relevant definitions I have at the start of my config.scm file: (define ane-wan-device "eno1") (define ane-wan-ip4 "162.55.88.253") (define ane-wan-gateway "162.55.88.193") (define swws-bridge-name "swws-bridge") > (list > (service static-networking-service-type > (list (static-networking > (addresses (list (network-address > (device ane-wan-device) > (value (string-append ane-wan-ip4 "/24"))))) > (routes (list (network-route > (destination "default") > (gateway ane-wan-gateway)) the next one the problematic part of my static-networking configuration: > ;; ip route add 10.1.2.0/24 dev swws-bridge via 192.168.133.12 > (network-route > (destination "10.1.2.0/24") ;; lxcbr0 net > (device swws-bridge-name) > (gateway "192.168.133.12")))) > ;; on node002 I've commented out this network-route part and now the networking service is running fine at boot (and after a restart obviously) I think that the missing "swws-bridge" interface when the static-network is activates is blocking all further networking service startup, including restarts after "swws-bridge" has been created by the libvirtd service. After the "swws-bridge" interface has been created this is the routing table: --8<---------------cut here---------------start------------->8--- g@ane ~$ ip route ls default via 162.55.88.193 dev eno1 162.55.88.0/24 dev eno1 proto kernel scope link src 162.55.88.253 192.168.133.0/24 dev swws-bridge proto kernel scope link src 192.168.133.1 --8<---------------cut here---------------end--------------->8--- Obviously if I "manually" add the route I'm able to ping hosts on the 10.1.2.0/24 network: --8<---------------cut here---------------start------------->8--- g@ane ~$ sudo ip route add 10.1.2.0/24 dev swws-bridge via 192.168.133.12 g@ane ~$ ip route ls default via 162.55.88.193 dev eno1 10.1.2.0/24 via 192.168.133.12 dev swws-bridge 162.55.88.0/24 dev eno1 proto kernel scope link src 162.55.88.253 192.168.133.0/24 dev swws-bridge proto kernel scope link src 192.168.133.1 g@ane ~$ ping 10.1.2.1 PING 10.1.2.1 (10.1.2.1): 56 data bytes 64 bytes from 10.1.2.1: icmp_seq=0 ttl=64 time=0.341 ms 64 bytes from 10.1.2.1: icmp_seq=1 ttl=64 time=0.232 ms 64 bytes from 10.1.2.1: icmp_seq=2 ttl=64 time=0.544 ms ^C--- 10.1.2.1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.232/0.372/0.544/0.129 ms --8<---------------cut here---------------end--------------->8--- ...but I would like the route be automatically added at boot time and not have to remember to add it "manually" after a reboot. Please how can I specify that "swws-bridge" is a dependency for the networking service and make that service wait for that interface to come up? I know there is a (requirement ) field in static-networking but "swws-bridge" is not a Shepherd service: do I have to use "libvirtd" as my static-networking requirement? [...] Happy hacking! Gio' -- Giovanni Biscuolo Xelera IT Infrastructures