With the suggested change , *it is working as expected*. Thank you very much Matt.
As a side note, I’m not sure if there is a way to improve this. In my setup, I use *VPP+LCP* , which causes synchronization issues ( *race conditions* ) with the OS networking and, in my case, with *FRR*. My workaround was to configure the networking service to wait for VPP to start. I also added a few seconds of 'sleep' to VPP so that once it starts, it can fully execute the initialization script. Additionally, I configured FRR to depend on both the networking service and VPP being up and running. If I don't set up the networking service to start after VPP, nothing works, and I get the errors shown below. VPP.service > > [Unit] > Description=vector packet processing engine > After=network.target > [Service] > Type=simple > ExecStartPre=-/sbin/modprobe uio_pci_generic > ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf > ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm /dev/shm/vpe-api > Restart=always > ExecStartPost=/bin/sleep 10 > #LimitCORE=infinity > [Install] > WantedBy=multi-user.target > networking.service > > [Unit] > Description=Network initialization > Documentation=man:interfaces(5) man:ifup(8) man:ifdown(8) > DefaultDependencies=no > Before=shutdown.target > Conflicts=shutdown.target > After=vpp.service > Wants=vpp.service > [Service] > Type=oneshot > RemainAfterExit=yes > SyslogIdentifier=networking > TimeoutStopSec=30s > EnvironmentFile=/etc/default/networking > ExecStart=/usr/share/ifupdown2/sbin/start-networking start > ExecStop=/usr/share/ifupdown2/sbin/start-networking stop > ExecReload=/usr/share/ifupdown2/sbin/start-networking reload > [Install] > WantedBy=basic.target network.target shutdown.target > > > Mar 03 19:12:40 frr-gru-edge-vpp systemd[1]: Starting networking.service - > Network initialization... > Mar 03 19:12:40 frr-gru-edge-vpp networking[520]: networking: Configuring > network interfaces > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: warning: ens16: pre-up > cmd '/usr/sbin/ip link set dev ens16 address 44:4C:A8:20:88:9D;' failed: > returned 1 (Cannot find device "ens16" > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: ) > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: error: netlink: > ens16.1001: cannot create vlan ens16.1001 1001: ifname ens16 not present > in cache > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: warning: ens16.1001: > device not found - please check your configuration > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: error: netlink: > ens16.304: cannot create vlan ens16.304 304: ifname ens16 not present in > cache > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: warning: ens16.304: > device not found - please check your configuration > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: error: netlink: > ens16.1200: cannot create vlan ens16.1200 1200: ifname ens16 not present > in cache > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: warning: ens16.1200: > device not found - please check your configuration > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: error: netlink: > ens16.1002: cannot create vlan ens16.1002 1002: ifname ens16 not present > in cache > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: warning: ens16.1002: > device not found - please check your configuration > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: error: netlink: > ens16.1802: cannot create vlan ens16.1802 1802: ifname ens16 not present > in cache > Mar 03 19:12:40 frr-gru-edge-vpp networking[544]: warning: ens16.1802: > device not found - please check your configuration >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#26861): https://lists.fd.io/g/vpp-dev/message/26861 Mute This Topic: https://lists.fd.io/mt/118106827/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
