systemd network interface configuration (was "Re: systemd woes continue")

2019-09-18 Thread Bob Tracy
On Wed, Sep 18, 2019 at 11:46:06AM +0200, John Paul Adrian Glaubitz wrote:
> Your permanent bashing of systemd makes answering your mails stressful
> for me.

Adrian -- please accept my apology for my rantings...  They contribute
nothing to the conversation, and as you note, irritate the very people
in the best position to render needed assistance.  

Going back to a previous message you sent, you suggested looking at a
few systemd network-related services:

(1) systemd-networkd: this is currently showing "disabled" on my system
(vendor preset: enabled).

(2) resolver-related systemd services such as "resolvconf" and 
"systemd-resolved":
"resolvconf" is "enabled", but "systemd-resolved" is "disabled"
(vendor preset: enabled).

None of the services mentioned above have any configuration files other
than the defaults.

So, I guess the main question on the table is, what's the best path
forward to ensure network interfaces are brought up and configured
automatically at boot time?  Related to that question: is the use of
"/etc/network/interfaces" deprecated?  That's where my network
configuration details currently exist, and that used to be sufficient,
even after the migration from the old-style init program/scripts to
"systemd".  A sanitized copy of my current "interfaces" file is
attached.

Thanks in advance for the assist.

--Bob
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address (masked)
netmask 255.255.255.240
network (masked)
broadcast (masked)
gateway (masked)
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers (masked)
dns-search (my registered domain)

# /64 prefix assigned by Hurricane Electric 
iface eth0 inet6 static
address (masked)
netmask 64
scope global

# Wireless settings for D-Link DWA-131 (r8712u driver from staging -- sigh)
# The initial interface name is wlan0, but that gets remapped to the name
# below by systemd+udev.
allow-hotplug wlx1c7ee513fb7b
iface wlx1c7ee513fb7b inet dhcp
wireless-mode Managed
wpa-driver wext
wpa-ssid (masked)
wpa-psk (masked)

# USB RTL8153 Gigabit Ethernet Adapter
allow-hotplug enx00e04c6881f7
iface enx00e04c6881f7 inet static
address (masked)
netmask 255.255.255.0
network (masked)
broadcast (masked)
gateway (masked)

# Hurricane Electric tunnel: ID# (masked) est. 01 May 2016
auto he-ipv6
iface he-ipv6 inet6 v4tunnel
address (masked)
netmask 64
endpoint (masked)
local (masked, but IPv4 address of eth0)
ttl 255
gateway (masked)


Re: systemd woes continue

2019-09-18 Thread Michael Cree
On Wed, Sep 18, 2019 at 11:46:06AM +0200, John Paul Adrian Glaubitz wrote:
> is just annoying. Please let's have a more constructive discussion, after
> all, the previous issues on alpha were not caused by systemd either but
> a bug in glibc for alpha.

I would not be so quick to blame glibc. (If you can point me to the
actual bug in glibc I will reconsider my opinion).

Systemd sidesteps glibc and makes direct geteuid, etc., syscalls.
Because Alpha did not have these syscalls systemd had a nasty hack
only compiled on Alpha which I was worried would break one day.
Systemd is one of the reasons why I supported getting the geteuid
compatible syscalls into the Alpha kernel.

Systemd may have come right because it was re-compiled against
recent linux headers and picked up the new Linux syscalls on Alpha,
and, if so, it will only work with a 5.1 or newer kernel.

I have been meaning to test this theory and re-look at the relevant
systemd code and consider whether it needs further patching (maybe
the Alpha specific hack can now be removed) but haven't got around to
it.

Cheers,
Michael.



Re: systemd woes continue

2019-09-18 Thread John Paul Adrian Glaubitz

Hi Bob!

On 9/18/19 1:48 AM, Bob Tracy wrote:

It appears that all the configuration info in "/etc/network/interfaces"
for my "eth0" interface was completely ignored other than the IPv4
address.  No IPv6 address, no "dns-*" config items, etc.  Thanks,
systemd!  Not :-(.  I blame "systemd", because, when it was still
dropping me into emergency mode, "eth0" came up correctly.


Your permanent bashing of systemd makes answering your mails stressful
for me. I have contributed to systemd quite some bit and I have a good
relationship with several of the developers, so the pointless bashing
is just annoying. Please let's have a more constructive discussion, after
all, the previous issues on alpha were not caused by systemd either but
a bug in glibc for alpha.

As for the network configuration issue you are having, this might be a
result of udev renaming your network interfaces names [1]. You can
try disabling that.

Adrian


[1] 
https://wiki.archlinux.org/index.php/Network_configuration#Revert_to_traditional_interface_names


--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913