Re: gPXE and Altiris PXE server (ProxyDHCP)
Shao Miller <[email protected]> Sun, 20 Dec 2009 17:00:59 -0500
| Newsgroups | gmane.network.etherboot.user |
|---|---|
| Message-ID | <[email protected]> |
Viswanath Krishnamurthy wrote: > gPXE seems to be failing with Altiris (HP deployment pack) PXE server > (proxyDHCP mode) and regular Windows DHCP server on the same network. > > gPXE sends DHCP DISCOVER > Both Altiris (running on different server) and DHCP server responds > with DHCP Offer > gPXE accepts IP address from regular DHCP server and sends DHCP > REQUEST and receives DHCP ACK from DHCP server. > It now enters proxy mode and sends out DHCP request to port 67 > Altiris ignores it > > Onboard PXE NIC works fine (HP nic) > > Next I changed the proxy_port to 4011 (PXE_PORT) and it worked fine > (in dhcp.c file). It seems like Altiris is listening on port 4011 and > not 67 and causes the problem where gPXE times out and says "No root > path or file name specified". Would you be so kind as to try Joshua Oreman's fix at http://git.etherboot.org/?p=gpxe-staging.git;a=commitdiff;h=4121ed2542cc41e666a27aba122ceed48a3e70bb ? A report for this patch's compatibility with Altiris would be fantastic! > I know there have been recent fixes for dnsmasq which could have > caused this regression Pretty much, yes. Josh's patch cleared things up for another product. Also, please note that there is a gPXE mailing-list. Info at: http://etherboot.org/mailman/listinfo/gpxe Thanks! - Shao Miller ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev