bug-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #35193] Grub2 doesn't use info in boot server packets


From: Tyson Whitehead
Subject: [bug #35193] Grub2 doesn't use info in boot server packets
Date: Thu, 29 Dec 2011 23:15:47 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.107 Safari/535.1

URL:
  <http://savannah.gnu.org/bugs/?35193>

                 Summary: Grub2 doesn't use info in boot server packets
                 Project: GNU GRUB
            Submitted by: twhitehead
            Submitted on: Thu 29 Dec 2011 11:15:45 PM GMT
                Category: Network
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: other
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

Currently grub2 only processes the DHCP ACK package.

When PXE booting this can result in missed PXE options (as the boot server can
supplement them) and grub not getting the IP address for the TFTP server that
served the core image (as this information may not even be in the DHCP
package).

I've put together a patch that adds parsing the boot server packet as well to
make sure all the required information gets extracted.  It gives precedence to
DHCP PXE options (as required by the PXE spec) and boot server IP
addresses/file names.

An example of a situation that doesn't work before this patch is running
dnsmasq on a local 192.168.1.x network in proxy mode along side a regular DHCP
server that doesn't provide booting services.  The dnsmasq parameters are

enable-tftp
tftp-root=/srv/tftp
pxe-service=x86PC, "GRUB", boot/grub/i386-pc/core
dhcp-range=192.168.1.0,proxy,255.255.255.0

Another example would be a remote TFTP server setup, such as

pxe-service=x86PC, "GRUB", boot/grub/i386-pc/core, 192.168.1.1

Cheers!  -Tyson

PS:  This should address the wrong server issue (DHCP vs boot) in 33348 but
doesn't do anything to add http support.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Thu 29 Dec 2011 11:15:45 PM GMT  Name:
0001-Include-PXE-info-from-boot-server-too-instead-of-jus.patch  Size: 3kB  
By: twhitehead

<http://savannah.gnu.org/bugs/download.php?file_id=24711>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?35193>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]