On Sat, Feb 11, 2023 at 3:53 PM Beat Bolli <[email protected]> wrote:
>
> On 11.02.23 14:36, Martin-Éric Racine wrote:
> > On Sat, Feb 11, 2023 at 3:25 PM Beat Bolli <[email protected]> wrote:
> >>
> >> On 11.02.23 14:03, Martin-Éric Racine wrote:
> >>> On Sat, Feb 11, 2023 at 2:42 PM Beat Bolli <[email protected]> wrote:
> >>>> On 11.02.23 12:01, Martin-Éric Racine wrote:
> >>>>> On Wed, 8 Feb 2023 08:35:02 +0200
> >>>>> =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <[email protected]>
> >>>>> wrote:
> >>>>>> On Mon, 06 Feb 2023 20:39:36 +0100 Beat Bolli <[email protected]> wrote:
> >>>>>>>          This morning, version 9.4.1-16 was installed by my daily
> >>>>>>>          unattended-upgrade run. As after all recent updates, the 
> >>>>>>> service
> >>>>>>>          was stopped, but not restarted after the update. This leads 
> >>>>>>> to
> >>>>>>>          loss of Internet connectivity after the DHCP lease expires.
> >>>>>>
> >>>>>> If you are only using dhcpcd-base, it implies that DHCP is restarted
> >>>>>> by ifupdown via /etc/network/interfaces. Is that the case here?
> >>>>>
> >>>>> Can you confirm?
> >>>>
> >>>> Honestly, I don't get the distinction between dhcpcd and &-base, but I
> >>>> now see in the package file list that the systemd integration is part of
> >>>> dhcpcd, not -base. So I have reported the bug for the wrong package.
> >>>>
> >>>> Regarding point 2 in the original report, I had to run "systemctl start
> >>>> dhcpcd.service" to restart the daemon.
> >>>
> >>> Can you paste me the content of /etc/network/interfaces and
> >>> /etc/network/interfaces.d/ just to be sure?
> >>
> >> Sure:
> >
> >> # The internal LAN interface
> >> allow-hotplug eth0
> >> iface eth0 inet static
> >>          address 192.168.11.1/26
> >>
> >> # The external WAN interface
> >> allow-hotplug eth1
> >> iface eth1 inet dhcp
> >>          # address 192.168.254.2/24
> >>          # gateway 192.168.254.1
> >>          up /usr/local/bin/freedns
> >
> > That explains it. The systemd unit conflicts with
> > /etc/network/interfaces since both are trying to start the same
> > interfaces.
> >
> > Can you check with 'dpkg -l | grep ifupdown' that you indeed have
> > ifupdown installed? If yes, you can purge 'dhcpcd' and only keep
> > 'dhcpcd-base' installed. It should do what you need.
>
> I have ifupdown installed. Now I've purged dhcpcd. I'll have to wait
> until the next update to verify.

sudo systemctl restart [email protected]

This should do what you need. If this works, the host should boot
correctly as well.

Martin-Éric

Reply via email to