[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bullseye: systemd-networkd-wait-online timeouts



Charles Curley:
> On Wed, 18 Aug 2021 21:36:30 +0200
> Jochen Spieker <ml@well-adjusted.de> wrote:
> 
>> Is there anything I can do about this without changing
>> /etc/network/interfaces? As far as I understand, I cannot switch to
>> systemd network configuration as long as the interfaces file exists.
> 
> Can you get anywhere by editing the template?

I do not have access to the template. It does not exist on my VM and I
assume it only exists in the hosting provider's infrastructure.

> Also, this interfaces file assigns address 127.0.0.1 to the interface
> venet0. Since that block (127.0.0.0/8, I believe) is reserved for the
> loopback device (interface lo), and is assigned automatically to lo,
> this setup is assigning 127.0.0.1 to both lo and venet:0. And that
> strikes me as a recipe for problems.

I totally agree and I have no idea why they are doing it this way. I
still would like to know why systemd does not recognize that the
interface configuration using ifupdown was successful and the the system
actually is online.

J.
-- 
Tony Blair is a hypnotised self-seeking scarecrow just like all the
rest.
[Agree]   [Disagree]
                 <http://archive.slowlydownward.com/NODATA/data_enter2.html>

Attachment: signature.asc
Description: PGP signature


Reply to: