Package: dhcpcd5
Version: 9.4.1-0.2
Followup-For: Bug #820069
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This bug happens because dhcpcd5 ships both an init.d script and systemd unit.
In order for dhcpcd5 to correctly work as an ifupdown backend via
/etc/network/interfaces, it should ship
Hi Adam,
On Fri, 8 Feb 2019 21:29:45 +1100 Scott Leggett wrote:
>
> You can avoid this issue by adding `allowinterfaces ...` or
> `denyinterfaces ...` as appropriate to the /etc/dhcpcd.conf file.
Have you tried updating the config file this way?
--
Regards,
Scott Leggett.
signature.asc
On Wed, 16 Jan 2019 20:20:04 -0800 Adam McKenna wrote:
> I was hit by this bug last night. After plugging a new Internet provider
> into my local network, my Debian router automatically added an IP address
> and default route to the new device. This resulted in my entire home's
> Internet
severity 820069 important
tags 820069 security
I was hit by this bug last night. After plugging a new Internet provider
into my local network, my Debian router automatically added an IP address
and default route to the new device. This resulted in my entire home's
Internet access being
dhcpcd does not parse /etc/network/interfaces.
I suspect dhcpcd was started by an init script, and the default config
is to configure all interfaces.
You can restrict this with /etc/dhcpcd.conf.
Roy
Package: dhcpcd5
Version: 6.0.5-2
Severity: normal
Hi,
this box has its network interface configured statically in
/etc/network/interfaces. dhcpcd5 is installed but should not be active
at this time. (I would have liked to use DHCP, but neither dhcpcd5 nor
isc-dhcp-client work properly on a
6 matches
Mail list logo
