On 9/28/20 11:21 AM, Andrew Lutomirski wrote:
I would have expected NetworkManager to handle this kind of setup
just fine. What went wrong?
getting offtopic, but ... a laundry list.
including broken routes, missed existing unit-file interface dependencies particularly
once bridges get involved, absolute disfunction with setups including shorewall &
wireguard, blah blah blah.
and, generally, a stubborn, been-there-done-that view that NM has *no place* on my servers
&/or workstations.
i'm sure _all_ of it was "bandaid-able" with enough monkeying around.
simply not worth the effort, cost, and uncertainty; i'd already moved OS/distros to
get away from a flaky network stack (among other issues, of course; not the least of which
was, ironically, old/dusty systemd version!) ... and intransigent 'policy'
decisions that came with it.
systemd-networkd with enterprise-grade/fits-my-needs DNS servers/resolvers works. very
nicely.
fingers-crossed that removing the unwanted/unwelcome cruft remains an easy option.
as always, YMMV.