ifupdown at least follows the principle of least surprise
ifupdown at least follows the principle of least surprise
Posted Oct 25, 2024 2:56 UTC (Fri) by fest3er (guest, #60379)In reply to: ifupdown at least follows the principle of least surprise by maniax
Parent article: Debating ifupdown replacements for Debian trixie
In my experience, the interface doesn't need to bounce. It seems that every time NM periodically wakes up, it 'deletes' everything it did not configure. (WTF!?! I just added those addresses! Where the eff dif they go?!?) It's akin to municipal residents going to the city park, setting up a badminton net and playing a match, only to have the park manager walk by, see the net and supports and remove them in the middle of the match because he did not set them up. (Kind-of foolhardy since the badminton players might start using *him* as the birdie, just as I have to kill NM when I'm using multiple IP addrs on an IF—and then figure out how to handle WiFi myself.)
Posted Oct 25, 2024 4:32 UTC (Fri)
by intelfx (subscriber, #130118)
[Link]
I thought that’s exactly how it worked :-)
Posted Oct 25, 2024 5:41 UTC (Fri)
by zdzichu (subscriber, #17118)
[Link]
NM *may* have some setting to ignore guerilla IP addresses (other tools, like systemd-network, have such settings), but I leave finding it as an excercise for the reader.
Posted Oct 29, 2024 10:42 UTC (Tue)
by taladar (subscriber, #68407)
[Link]
ifupdown at least follows the principle of least surprise
ifupdown at least follows the principle of least surprise
ifupdown at least follows the principle of least surprise