We had a similar issue. We realized that (in our case) the problem was
the Spanning Tree time to converge.
Explication: when PXE boots get an IP from DHCP server, and then when Linux
starts, the interface go down and up, and Linux try to get IP from DHCP server
again, but fails after 35 seconds
** Changed in: klibc (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notificat
** Changed in: klibc (Debian)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications abou
trusty-proposed, klibc-utils 2.0.3-0ubuntu1.14.04.3 still suffers from
this (or equally manifesting) issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Con
The bug seems to be squashed in Xenial, Yakkety (and Zesty as well).
Trusty seems to be the last one that needs verification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay durin
Hello, cyphermox!
Do you think you could send your patches upstream as well?
The same bug affects Debian (http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=756633) and, probably, the source packages. It's
sad seeing this fixed in Ubuntu only.
Thanks!
--
You received this bug notification becau
I stand corrected;
there's a typo on my patch the correct line should look like:
+ bootp.flags = htons(0x8000);
as mentioned by jvosburgh
Unfortunately this mistake was not previously detected because
all the net gear I've used on tests and Wireshark completely
ignored it.
Best,
Patrick
--
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bug
Opened bug 1624014 to patch the wrong-bit regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug g
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 z
This bug was fixed in the package klibc - 2.0.4-8ubuntu1.16.04.1
---
klibc (2.0.4-8ubuntu1.16.04.1) xenial; urgency=medium
* debian/patches/broadcast_dhcp_send.patch: yiaddr should always be set to 0
(INADDR_ANY) when sending those messages we're sending as a DHCP client,
so
you know what
fixing 2 + 2 = 5
with 2 + 2 = 4
does not really need to be "confirmed" in every single Ubuntu flavor.
if I were you I would not remove anything because that would only add confusion.
Best,
Patrick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The wily update was not verified in three months, and wily is almost
EOL. So I removed the -proposed package.
** Changed in: klibc (Ubuntu Wily)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>This has broken DHCP in our environment.
>I suspect it has something to do with dhcp relaying.
If your DHCP relay is broken after this change that means your DHCP
relay needs the client's IP on the yiaddr field and that means you have
a broken DHCP relay.
--
You received this bug notification b
Were you able to confirm this? It seems very odd, since regular DHCP
operations are usually performed with userspace clients, not ipconfig
(usually used in early userspace/startup environments).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This has broken DHCP in our environment. I suspect it has something to
do with dhcp relaying. I am trying to get good data to confirm it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Is it possible for anyone to test them in Wily/Xenial? It would be great
to have those packages moved from Proposed to the current release for
those versions.
Thanks! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
> * debian/patches/broadcast_dhcp_send.patch: set the broadcast
> bit and yiaddr to 0 (INADDR_ANY) when sending DHCPDISCOVER/
> DHCPREQUEST, as per RFC 2131; section 4.1.
This is OK
>This helps when there is more than one interface
>trying to do DHCP at the same time.
This is complete nonsense
This bug was fixed in the package klibc - 2.0.3-0ubuntu1.14.04.1
---
klibc (2.0.3-0ubuntu1.14.04.1) trusty; urgency=medium
* debian/patches/broadcast_dhcp_send.patch: set the broadcast bit and yiaddr
to 0 (INADDR_ANY) when sending DHCPDISCOVER/DHCPREQUEST, as per RFC 2131;
s
** Tags removed: rls-u-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs.lau
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://
The fix works for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs.launc
Forgot to say, I verified in 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs
here you have also an old bug (2 years) affecting PXE scenarios when
using CIFS. It was never fixed even when the solution is right there.
seen in:
ubuntu-14.04-desktop-amd64.iso
ubuntu-14.04-desktop-i386.iso
ubuntu-16.04-desktop-amd64.iso
ubuntu-16.04-desktop-i386.iso
https://bugs.launchpad.
Hello Jim, or anyone else affected,
Accepted klibc into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/klibc/2.0.3-0ubuntu1.14.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
I have sent the patch to Debian long ago,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633
I found Daniel Baumann there who systematically refused to do anything
on this matter answering very funny things.
I have also sent the patch to the klibc list but it was completely
ignored.
Best,
Thanks, Mathieu! I didn't get a chance to test this yet, but it's great
to see it may be now fixed for good. :-)
Could you assist us once more?
We've been trying to send the fix for this bug upstream, so that all
GNU/Linux distros can get the fixed versions. However, the original
mailing list for
--- a/usr/kinit/ipconfig/dhcp_proto.c
+++ b/usr/kinit/ipconfig/dhcp_proto.c
@@ -201,8 +201,14 @@ static int dhcp_send(struct netdev *dev,
bootp.hlen = dev->hwlen;
bootp.xid = dev->bootp.xid;
bootp.ciaddr= INADDR_ANY;
- bootp.yiaddr= dev->ip_addr;
+
This bug was fixed in the package klibc - 2.0.4-8ubuntu2
---
klibc (2.0.4-8ubuntu2) yakkety; urgency=medium
* debian/patches/broadcast_dhcp_send.patch: yiaddr should always be set to 0
(INADDR_ANY) when sending those messages we're sending as a DHCP client,
so DHCPDISCOVER a
@Mathieu Trudel-Lapierre
> please check whether this actually fixes the issue.
> this is no guesswork.
Yes it is; I'm saying here for almost 2 years what it has to be done to fix
this problem and you recommend to see if a partial fix solves the problem or
not. well...
>Bits can be missed.
Sure
** Description changed:
+ [Impact]
+ PXE booting users with live images or other minimal setups using klibc-utils.
+
+ [Test case]
+ Attempt to PXE boot using Ubuntu live images; see below for details.
+
+ [Regression potential]
+ This forces the yiaddr (client requested/current IP) to be set to
** Also affects: klibc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: klibc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: klibc (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: klibc (Ubuntu)
Status: Fix
@patpat; this is no guesswork. Bits can be missed. While you're right as
to the correct value for yiaddr, I believe that you misunderstand how
klibc on the whole works, and how Ubuntu processes work. The status
change was automatic from the package upload.
Was I was getting at before is that the D
I'm still seeing this bug as well.
Both Ubuntu 16.04 LTS and 15.10 netboot kernels produce this behaviour.
When IP-Config starts configuring the NICs, I see the DHCPDISCOVER
arriving on the DHCP server, DHCPOFFER is going out, but no ACK is being
received and the client continues telling me "IP-
Hello, Mathieu!
Thank you for looking into this.
Unfortunately, the bug is still present. I tested the same setups with
the latest Xenial release (which natively includes your fix) and the
behavior is the same: the DHCP server receives the request, OFFERs an IP
address and ipconfig (from klibc-ut
>yiaddr is set elsewhere in the code already (in dhcp_send_discover()
If that is the case it is also wrong;
I wonder what IP are they using in a DHCP DISCOVERY??
that makes absolute not sense for a booting client trying to get an IP.
anyway it seems you are wrong:
int dhcp_send_discover(struct
yiaddr is set elsewhere in the code already (in dhcp_send_discover() or
whatever); please check whether this actually fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
De
Patch sent upstream
But I think that list is not really active
http://www.zytor.com/pipermail/klibc/2016-March/003923.html
Best,
Patrick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Tit
I just recompiled ipconfig "once" and I got it working
I can confirm that /klibc-2.0.4/usr/kinit/ipconfig/dhcp_proto.c
did not fix this bug yet
static int dhcp_send(struct netdev *dev, struct iovec *vec)
{
struct bootp_hdr bootp;
char dhcp_hostname[SYS_NMLN+2];
uint8_t p
That's great - thank you (again) for testing this. :-) I'd help with the
testing (compiling my own version), but I'm in a slow, expensive
connection at the moment and can't grab the needed kernel packages.
If the latest version (from the most upstream this can get) also has
this issue, what do you
As a workaround, you may also use "IPAPPEND 2" in the pxe config.
** Changed in: klibc (Ubuntu)
Status: Confirmed => In Progress
** Changed in: klibc (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a membe
It seems the fix is only partial ;
>From RFC2131 (Dynamic Host Configuration Protocol) for a client we have:
FieldDHCPDISCOVER DHCPREQUEST DHCPDECLINE,
DHCPINFORM DHCPRELEASE
-
This bug was fixed in the package klibc - 2.0.4-8ubuntu1
---
klibc (2.0.4-8ubuntu1) xenial; urgency=medium
* debian/patches/broadcast_dhcp_send.patch: set the broadcast bit when
sending DHCPDISCOVER/DHCPREQUEST, as per RFC 2131; section 4.1. This
helps when there is more tha
;-)
I kinda dread ask it here, but... it seems you've recompiled ipconfig quite a
few times to get it working.
Have you tried recompiling the latest version from kernel.org? As in:
https://www.kernel.org/pub/linux/libs/klibc/2.0/
It would be interesting to know if it's a bug in the current sour
This is an old bug never fixed by Ubuntu, never fixed by Debian either...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633
You have to recompile ipconfig with the patch I wrote above and everything
works OK.
Hopefully some day Ubuntu and/or Debian will fix this ;-)
--
You received this
I'm hitting the same bug. It's a show-stopper when it comes down to
using PXE for network booting. I'm using Wily Werewolf and trying to
boot off PXE, but no dice. The DHCP server receives the request, OFFERs
an IP address and ipconfig (from klibc-utils) simply doesn't acknowledge
it.
I first ran
PXE booting w/o the ipconfig issue
; ubuntu-15.10-desktop-amd64.iso
; ubuntu-15.10-desktop-i386.iso
; ubuntukylin-15.10-desktop-amd64.iso
; ubuntukylin-15.10-desktop-i386.iso
requires INITRD_N11.1.GZ
source:
http://www.vercot.com/~serva/an/NonWindowsPXE3.html
--
You received this bug notif
patpat's fixed initramfs (INITRD_N11.2.GZ) doesn't work in ubuntu 15.10,
system crash when trying launch ipconfig.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot,
no news from Ubuntu, your link seems broken...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
h
We find similar issue. Does have any update from ubuntu?
https://bugs.launchpad.net/quantatw/+bug/1376588
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Confi
This is the patch that "fix" this issue...
I have been using this patch for almost a year and works perfectly
static int dhcp_send(struct netdev *dev, struct iovec *vec)
{
...
- bootp.yiaddr = dev->ip_addr;
+bootp.yiaddr = INADDR_ANY;
+bootp.flags = htons(0x800);
...
}
I think I'm seeing this bug as well. However, the patch from the debian
bug report does not fix the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot
** Tags removed: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs.launchpad.net/
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
** Changed in: klibc (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this
** Also affects: klibc (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633
Importance: Unknown
Status: Unknown
** Tags added: rls-u-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Additional info
1)
When PXE installing on a VMware Workstation using the VMware DHCP server plus
Serva as proxyDHCP the bug is not present.
When PXE installing on a real PC with a Netgear ISP router as DHCP plus Serva
as proxyDHCP the bug is present.
In the first case the VMware DHCP module igno
I think I have found/solved this bug;
The problem is located at ipconfig (klibc-utils) not implementing the DHCP
standard as it should at the file
/klibc-2.0.3/usr/kinit/ipconfig/dhcp_proto.c
old:
static int dhcp_send(struct netdev *dev, struct iovec *vec)
{
...
bootp.yiaddr= dev->i
** Package changed: initramfs-tools (Ubuntu) => klibc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about t
Very weird bug;
I have PXE booted over VMWare VM w/o problem but when PXE booting on real
hardware I got the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Tit
This same bug appears to be affecting the PXE boot up process of MAAS
nodes. It seems to only be an issue on machines with more than one NIC.
It looks like the DHCP requests never make it to the MAAS cluster
controller.
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Package changed: ubuntu-release-upgrader (Ubuntu) => initramfs-tools
(Ubuntu)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
63 matches
Mail list logo
