[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up

[patpat]

>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 netdev *dev)
{
	dev->ip_addr = INADDR_ANY;
	dev->ip_gateway = INADDR_ANY;

        dprintf("-> dhcp discover ");

	return dhcp_send(dev, dhcp_discover_iov);
}

> please check whether this actually fixes the issue.
I encourage you to stop the guesswork and fix this upon what RFC2131 says
(which is pretty clear on this regard,  just see its page 36)
yiaddr must be 0 on packets sent by the client.

I encourage you not to tag this bug as "fix released"

Best,
Patrick

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1327412

Title:
  Delay during PXE Boot, IP-Config gives up

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  Attempting to PXE boot both the 12.04.3 and 14.04 Live images.   PXE
  boot works normally (PXE Menu, select desired image, image begins
  loading), then the boot process hangs while IP-Config attempts to get
  an IP address:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 3 secs - giving up

  These lines appear very quickly (5 seconds has NOT elapsed), after
  about a minute, we get this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 4 secs - giving up

  Some time later, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 6 secs - giving up

  Until finally, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 9 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: eth0 guessed broadcast address 172.25.11.31
  IP-Config: eth0 complete (dhcp from 172.25.10.20):
  (snip)

  While watching the DHCP server logs, Ubuntu is either not sending a
  DHCP Discover at times, or is not replying back with a DHCPRequest
  during these sessions, presumably ignoring an response from the DHCP
  server.  From the initial booting of the system via PXE, to when
  Ubuntu finally shows the desktop, almost 12 minutes will have elapsed.

  I am seeing this same behavior on both 12.04.3 and 14.04.  After
  finding a number of similar erros via Google and no real resolution, I
  have opened this bug.

  The system experiencing this issue has multiple ethernet interfaces
  (actual HW, not a VM), some Google found solutions suggest hard coding
  DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't
  acceptable as a system attempting to PXE boot may be using an
  alternate port for the network.

  I have found what looks to be a very similar bug filed for Debian,
  #584583, which also contains a patch for this issue (under Debian).

  I have no problems in PXE booting to various Windows, RedHat, Centos,
  or Fedora OSs.  Ubuntu is the only Live OS that I'm attempting to boot
  at present.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Jun  6 20:22:09 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions