I've seen (and caused/fixed) so many horrific things that I feel compelled to improve my expression skills... so that I can write them up more formally.
Most recently, I moved some of our Ubuntu systems away from network-scripts to systemd-networkd
I didn't realize the gravity of this change. Be warned, systemd-networkd will significantly change how forwarding works.
Due to things outside of my control, we have some systems playing router. They didn't like this change a whole lot, and I neglected to test this.
On network-scripts with the usual kit of sysctl and iptables rules, you're good to go.
networkd however requires more explicit configuration; particularly which interfaces may forward.
Not a big deal, unless you don't know... like I didn't
I find myself closer to the 'fan' side of systemd, but I'm under no illusions either - there are several detriments.
I find some of the heavier responses to it strange, either for or against. It's like developing a personality around a preference of sporks over forks/spoons.
Use what you like, help those who have trouble... but neither needs proselytizing
I've seen (and caused/fixed) so many horrific things that I feel compelled to improve my expression skills... so that I can write them up more formally.
Most recently, I moved some of our Ubuntu systems away from network-scripts to systemd-networkd
I didn't realize the gravity of this change. Be warned, systemd-networkd will significantly change how forwarding works.
Due to things outside of my control, we have some systems playing router. They didn't like this change a whole lot, and I neglected to test this.
On network-scripts with the usual kit of sysctl and iptables rules, you're good to go.
networkd however requires more explicit configuration; particularly which interfaces may forward.
Not a big deal, unless you don't know... like I didn't