Re: missing gw in route -n
On 07/13/2018 01:21 PM, Mark Morgan Lloyd wrote:
> On 13/07/18 09:15, John Paul Adrian Glaubitz wrote:
>
>> Or, alternatively: Set up systemd-networkd and systemd-resolved and don't
>> waste endless amounts of time and energy to get this mess fixed which is
>> bash-script-based network initialization.
>
> ..which is something that those of us who are investing significant resources into
> complex routing and firewalling intend- for the moment at least- to stick with, to
> the extent of migrating to a different distro if necessary.
If you need a long discussion over multiple days to get this sorted out, it might
be a good indicator that the current solution isn't probably the best one.
> If- as you appear to be saying- Debian is knowingly shipping stuff in a broken
> state then my only response can be that we've got enough problems of our own
> without trying to fix yours.
Debian isn't shipping stuff that is broken. The default network configuration works
just fine, either with NetworkManager or systemd-networkd. Both of these solutions
also support complex routing and firewalling setups.
The problem here are hacky bash scripts which are racy, prone to various bugs
and they usually break once you make the slightest configuration change. The
whole concept is just outdated and the software often not really maintained
upstream anymore.
If you have an embedded board, server, container or virtual machine which runs
headless, I don't see any compelling argument to not use systemd-networkd. I have
switched my buildds to it and I never looked back. It just works(TM).
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: