Si-Wei,
What environment and methodology are you testing with? I do not see the
same results you are reporting. I am using the instructions you
previously provided, and with an 18.04.5 Ubuntu image, I see the
expected network interface naming (ens3, ens3nsby), and do not see
Si-Wei,
In the test environment I'm using, the only change needed was to
initramfs-tools. I suspect the udevd change you're thinking of was an
alternate implementation that we did not proceed with due to the
regression it introduced (that network interface names would change).
--
You received
Regarding #2 from comment #19:
As the defined range for the ipv6.mtu is from IPV6_MIN_MTU to the
device's MTU, and the existing API returns an error if the ipv6.mtu is
out of range, I think it's reasonable for a configuration with the
ipv6.mtu > device MTU to fail.
--
You received this bug
Patch proposal to modify ipconfig to use one packet socket per interface
** Patch added: "klibc-fix-1.patch"
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1652348/+attachment/4806861/+files/klibc-fix-1.patch
--
You received this bug notification because you are a member of Ubuntu
** Changed in: klibc (Ubuntu)
Status: Confirmed => In Progress
** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.10-rc1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
without major rework to utilize one packet
socket per interface.
** Tags removed: kernel-key
** Package changed: linux (Ubuntu) => klibc (Ubuntu)
** Changed in: klibc (Ubuntu)
Status: Triaged => Confirmed
** Changed in: klibc (Ubuntu)
Assignee: (unassigned) => Jay Vosburgh (
The patch added to nominally fix this issue is incorrect; it is setting
the wrong bit in the BOOTP flags field for broadcast:
+ bootp.flags = htons(0x800);
The correct value should be 0x8000. This is causing issues with
switches that reject the packet as having bits set in a "must be
Public bug reported:
The /usr/share/initramfs-tools/hook-functions contains what appears to be a
variable name update (from root to dev_node) error.
It appears that one instance of root was not updated correctly; this causes
mkinitramfs to fail with the error:
mkinitramfs: for device /dev/vda1
ifupdown 0.7.48.1ubuntu9 resolves the original problem for me on a fresh
vivid install with the daily build for today.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
Public bug reported:
The change to ifup@.service done as part of LP 1425376 appears to break the
ordering of units marked as After=network-online.target. In my specific
case, a new service script with After=network-online.target is erroneously
run concurrently with dhclient. As the new
10 matches
Mail list logo
