Not really, no. This was simple enough and I prefer to keep as close to netplan as possible as I suspect macvlan will eventually be supported. I could be swayed with the right argument, I suppose... O. On July 7, 2020, at 4:19 PM, Chriztoffer Hansen <ch@ntrv.dk> wrote: Dear Oliver, On Tue, 7 Jul 2020 at 22:04, Oliver O'Boyle <oliver.oboyle@gmail.com> wrote:
To close the loop:
I ended up going down the /etc/networkd-dispatcher route. I put:
[ -e /etc/network/if-up.d ] && /bin/run-parts /etc/network/if-up.d exit 0
into a script in that directory, then:
if ip link show vlan2049 | grep -sq 'state UP'; then ip link add vlan2049-4 link vlan2049 addrgenmode random type macvlan mode bridge ip link set dev vlan2049-4 address 00:00:5e:00:01:01 ip addr add 192.168.145.194/26 dev vlan2049-4 ip link set dev vlan2049-4 up
ip link add vlan2049-6 link vlan2049 addrgenmode random type macvlan mode bridge ip link set dev vlan2049-6 address 00:00:5e:00:02:01 ip addr add 2610:139:c001:3f:1801:f20a::5/64 dev vlan2049-6 ip link set dev vlan2049-6 up fi exit 0
into /etc/network/if-ip.d/
I figured this would allow someone not familiar with the workaround to perhaps more easily figure out what was happening.
It works well enough, but it's ugly AF... I'll probably make it a bit smarter now, but it works.
You never considered going down the system-networkd route? -- Cheers, CHRIZTOFFER _______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog