[ale] Remove systemd network handling

[Alex Carver]

I do have a router/firewall that is running without systemd and uses
only /etc/network/interfaces for the multiple NICs.  Thankfully that's
been ok so far but I'm going to check again in case something slipped in
like it did with this other machine.

The network service is likely fine and helpful with a laptop that moves
around a lot.  A static machine doesn't need that.  I'm hoping this is
the fix because there's nothing else that indicates a hardware issue.
My data loggers just show various commands timing out and then, when it
tries to reconnect automatically, I get an error "no route to host"
which usually indicates the interface dropped entirely.  The script
retries several times a few seconds apart so the second try usually
responds.  I only know about it because one of the collection threads
will die because it times out too many times before the reconnect
happens and I'm left looking at a database with missing data.

On 2021-09-20 13:51, Horkan Smith wrote:
> Sounds like you've gotten it turned off, cool!
> 
> Just in case someone else needs it, I'll note that I *don't* have a copy
> of my /etc/network/interfaces file in /etc/systemd/network, instead in
> my case I put several *.network files, which look something like:
> 
> [horkan at danube network]$ cat 50-eth1.network [Match]
> Name=eth1
> 
> [Network]
> DHCP=no
> LinkLocalAddressing=no
> 
> [Address]
> Address=192.168.10.1/24
> 
> [horkan at danube network]$ cat 50-eth0.network [Match]
> Name=eth0
> 
> [Network]
> DHCP=yes
> DNSSEC=no
> 
> 
> and even
> 
> [horkan at danube network]$ cat en.network [Match]
> Name=en*
> 
> [Network]
> DHCP=yes
> DNSSEC=no
> 
> (I'm using this machine as a dsnmasq server & NAT router, thus the
> multiple ethernets.)
> 
> Sorry, I should've documented *what* I put that dir a little better in
> my first message.....
> 
> I'd have to dig around a little to see if this would work on raspbian,
> or if this arch-based distro would use an 'interfaces' file in the
> /etc/systemd/network directory....  I worked out the .network file
> approach from "man systemd.network", FWIW.
> 
> The Arch distro doesn't even have an /etc/network directory; I think
> that's a Debian thing they're continuing to support for backward
> compatibility.
> 
> later!
>   horkan
> 
> 
> On Mon, Sep 20, 2021 at 08:03:38AM -0700, Alex Carver wrote:
>> The original network configuration was in /etc/network/interfaces and
>> perfectly stable.  One update a few months ago snuck in an automatic
>> background apt update cron job (through systemd ironically) and a copy
>> of my interfaces file was automatically inserted into the
>> /etc/systemd/network firectory.  For whatever reason systemd was
>> bouncing the connection since that update.
>>
>> On 2021-09-20 05:14, Horkan Smith wrote:
>>> This may be a silly question, but have you tried putting your static
>>> definition in /etc/dhcpcd.conf (as my fairly recent Raspberry OS install
>>> suggests), or in /etc/systemd/network/ (as an older raspberry arch
>>> install I have wanted) ??? Neither would remove systemd (sorry!), but
>>> both appear stable for me so far.
>>>
>>> later!
>>> ???? horkan
>>>
>>>
>>> On Sun, Sep 19, 2021 at 03:55:44PM -0700, Alex Carver via Ale wrote:
>>>> Ok, I'm having some trouble figuring out how to completely remove
>>>> systemd from handling network connections.?? For some reason it decides
>>>> to bounce the connection on a couple machines every few days with no
>>>> information in the logs as to why.?? It causes havoc with a bunch of
>>>> data
>>>> collection scripts that are connected to instruments. I completely lose
>>>> connection to any of the instruments and can't recover without fully
>>>> restarting the scripts. I don't need the connection managed for me,
>>>> it's
>>>> perfectly fine statically configured.
>>>>
>>>> The device is already statically defined in /etc/network/interfaces,
>>>> I'm
>>>> not using DHCP on this particular machine, and there's no need to be
>>>> looking for hotplug events because the instruments and computer are all
>>>> bolted together in the same chassis.
>>>>
>>>> I still seem to have a networking.service listed but I've not found a
>>>> way to stop everything. Nearly everything I find in searching is how to
>>>> enable it which isn't what I want.
>>>>
>>>>
>>>> As an aside, are there any good explanations for how to remove user
>>>> management and login control from systemd as well??? I don't need seats
>>>> or any of the fancy features on this machine, that's just overhead for
>>>> no good value so I'd rather to back to plain logins.
>>>> _______________________________________________
>>>> Ale mailing list
>>>> Ale at ale.org
>>>> https://mail.ale.org/mailman/listinfo/ale
>>>> See JOBS, ANNOUNCE and SCHOOLS lists at
>>>> http://mail.ale.org/mailman/listinfo
>>>
>