[Bug 1937110] Re: dhcp option 121 & 249

2022-05-20 Thread Matt Heller
I'll also add that installers for past LTS Ubuntu releases do work in our environment. I opened up the Focal initrd.gz we use for PXE based installs (I think it was from the mini.iso which I guess is now classified as a "Legacy Image", http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-

[Bug 1937110] Re: dhcp option 121 & 249

2022-05-20 Thread Matt Heller
The Ubuntu Jammy installer initrd is missing the /etc/dhcp/dhclient- exit-hooks.d/rfc3442-classless-routes hook for dhclient. The /sbin/dhclient-script included in the initrd assumes the hook is present and if the "rfc3442_classless_static_routes" DHCP is sent by the DHCP server it ignores the the

[Bug 1840477] Re: Probed linux entries not bootable if original initrd line has more than one file

2019-08-16 Thread Matt Heller
I didn't spot an existing bug report when I first filed this but I later found: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1635781 ...which is pretty closely related. I am using UEFI and Manjaro Linux rather than Legacy BIOS mode and Arch Linux but the cause of the problem seems to

[Bug 1840477] Re: Probed linux entries not bootable if original initrd line has more than one file

2019-08-16 Thread Matt Heller
My apologies, I just realized I did have to change one more line to make the generated grub menu work for me, the diff of 30_os-prober should really be: diff /etc/grub.d/30_os-prober.original /etc/grub.d/30_os-prober 246c246 < LINITRD="`echo ${LINUX} | cut -d ':' -f 5`" --- >

[Bug 1840477] [NEW] Probed linux entries not bootable if original initrd line has more than one file

2019-08-16 Thread Matt Heller
Public bug reported: I have Manjaro Linux 18.0.4 installed and then recently installed Ubuntu 19.04 on another partition. After the Ubuntu install the Ubuntu created GRUB boot menu includes entries for booting Manjaro but they aren't functional. It is repeatable after install too, If I run

[Bug 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes

2017-07-07 Thread Matt Heller
** Bug watch added: Debian Bug tracker #867625 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867625 ** Also affects: isc-dhcp (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867625 Importance: Unknown Status: Unknown -- You received this bug notification because

[Bug 1615342] Re: variable of $new_rfc3442_classless_static_routes has spelling error in /sbin/dhclient-script

2017-07-07 Thread Matt Heller
FYI this bug is fixed in newer versions, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748272 So perhaps this bug can be closed? --Matt ** Bug watch added: Debian Bug tracker #748272 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748272 -- You received this bug notification

[Bug 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes

2017-07-07 Thread Matt Heller
Is there something I can do to help make some progress fixing this bug? This issue is not applicable to the upstream software source however I did notice that it is relevant to Debian's isc-dhcp-client package which I believe is in a sense "upstream" for the Ubuntu package. In light of that should

[Bug 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes

2017-03-14 Thread Matt Heller
In my environment we have some dual-homed Ubuntu hosts that have one network interface with a WAN IP and one on a private network. For proper network connectivity we need to use the configurable metric value to prioritize the default route provided by the WAN connected interface over the default