On Sat, Apr 10, 2021 at 11:23:53PM +0200, Bastian Blank wrote:
> On Sat, Apr 10, 2021 at 02:11:06PM -0700, Josh Triplett wrote:
> > For cloud instances and VMs, it's helpful to be able to use ip=dhcp as a
> > minimal network configuration. Enabling this option will do nothing
> > unless the kernel
Processing control commands:
> tag -1 wontfix
Bug #986741 [linux-image-cloud-amd64] Please enable CONFIG_IP_PNP_DHCP=y in
cloud image
Added tag(s) wontfix.
--
986741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 wontfix
Hi
On Sat, Apr 10, 2021 at 02:11:06PM -0700, Josh Triplett wrote:
> For cloud instances and VMs, it's helpful to be able to use ip=dhcp as a
> minimal network configuration. Enabling this option will do nothing
> unless the kernel command line includes ip=dhcp.
We don't
Package: linux-image-cloud-amd64
Severity: wishlist
X-Debbugs-Cc: j...@joshtriplett.org
For cloud instances and VMs, it's helpful to be able to use ip=dhcp as a
minimal network configuration. Enabling this option will do nothing
unless the kernel command line includes ip=dhcp.
-- System
I can confirm this behaviour. I also have wired and wireless bonded, and
it stopped working on 5.10.0-5. Everything looks fine: bond, gateway,
DNS, ... all have correct if addresses obtained from dhcp; resolvectl
looks fine; but I cannot even ping my gateway/router.
--
Francesc
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 09 Apr 2021 20:17:58 +0200
Source: linux
Architecture: source
Version: 5.10.28-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Changes:
linux
6 matches
Mail list logo
