<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">> That said, let me explain the real situation ...</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">> The IT guys already have one DHCP server running per subnet. (for network booting)</span><br style="font-family:arial,sans-serif;font-size:13px"><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">> I want to deploy my own PXE booting network, parallel to theirs to try out iPXE.</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">> </span><span style="font-family:arial,sans-serif;font-size:13px">(which would point the PXE clients to *my* installation server, rather than theirs.</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">> </span><span style="font-family:arial,sans-serif;font-size:13px">Having this feature allows me to test an alternate configuration even when the machine's</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">> </span><span style="font-family:arial,sans-serif;font-size:13px">MAC address is present in the IT network.</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">> </span><span style="font-family:arial,sans-serif;font-size:13px">Regards,</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">> </span><span style="font-family:arial,sans-serif;font-size:13px">Shantanu</span><br style="font-family:arial,sans-serif;font-size:13px"><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">You can sorta, kinda do this with proxyDHCP but it still requires the cooperation of your network team unless you're just doing this on one subnet that has a proxyDHCP server running. </span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><font face="arial, sans-serif">I'm with others and would not at all suggest you try to usurp the existing network boot process but you can try this out say in a self-contained VM network (VirtualBox, VMware, etc.). You could run a conventional DHCP server (ISC, dnsmasq, etc.) from one VM then try out a proxyDHCP server in another VM then try the network boot process from a third VM to get an idea of how this works.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">dnsmasq is the only proxyDHCP server I am aware of that works reliably. Here's a dnsmasq configuration I've created for an iPXE-centric tool I'm working on:</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><div>port=0</div><div>log-dhcp</div><div>dhcp-match=ipxe,175</div><div>dhcp-option=175,8:1:1</div><div>dhcp-boot=net:ipxe,<a href="http://yourbootserver.domain.com/boot/ipxeboot/${net0/mac}">http://yourbootserver.domain.com/boot/ipxeboot/${net0/mac}</a></div>
<div>dhcp-boot=tag:!Iipxe,ipxe.0</div><div>enable-tftp</div><div>tftp-root=/tftpboot</div><div>dhcp-range=192.168.0.0,proxy,255.255.0.0</div><div>dhcp-range=10.0.0.0,proxy,255.0.0.0</div><div>dhcp-range=172.16.0.0,proxy,255.255.0.0</div>
<div>pxe-service=net:#ipxe,x86PC,"Network Boot Environment",ipxe-native</div><div><br></div><div>In a real-world production environment you'd have to have a DHCP relay (i.e., ip helper) for every subnet pointing to this proxyDHCP server to pass network boot parameters. You can have multiple IP helpers per subnet so you could have one that actually hands the DHCP config and the other that just passes proxyDHCP network boot parameters; example:</div>
<div><br></div><div><div>interface Vlan50</div><div> ip address 10.1.50.2 255.255.255.0</div><div> ip helper-address 10.1.1.5 (your standard company DHCP server)</div><div> ip helper-address 10.1.20.15 (your proxyDHCP server running dnsmasq)</div>
<div> no ip proxy-arp</div><div> no ip route-cache cef</div><div> no ip route-cache</div><div> no ip mroute-cache</div><div> standby 50 ip 10.1.50.1</div><div> standby 50 priority 150</div><div> standby 50 preempt</div><div>
end</div></div><div><br></div><div>Again, to be perfectly clear, if you already have a network boot environment I don't envision your network/server guys will be OK with someone trying to usurp the network boot process. They *might* go for it if it's only for one subnet that maybe they give you as a sandbox. </div>
<div><br></div><div>You could also ask if you can put your iPXE bootstrap into whatever existing network boot system they have in place. If they've already got pxelinux it's quite trivial to add it; e.g., </div><div>
<br></div><div>LABEL ipxe</div><div> MENU LABEL iPXE boot</div><div> KERNEL ipxe.0 </div><div><br></div><div>They may or may not be OK with this but it could potentially just be a hidden option. </div><div><br></div><div>
And, of course, the lowest hanging fruit of the bunch is just boot off your own iPXE ISO where you can specify whatever boot options you'd like regardless of the existing DHCP environment. Naturally that negates all the fun of true network bootstrapping but that said you do still get the fun of using iPXE and all it can do.</div>
<div><br></div><div>Regards,</div><div>Jim Antoniou</div></font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 4:00 AM, <span dir="ltr"><<a href="mailto:ipxe-devel-request@lists.ipxe.org" target="_blank">ipxe-devel-request@lists.ipxe.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send ipxe-devel mailing list submissions to<br>
<a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:ipxe-devel-request@lists.ipxe.org">ipxe-devel-request@lists.ipxe.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:ipxe-devel-owner@lists.ipxe.org">ipxe-devel-owner@lists.ipxe.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of ipxe-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: iPXE with specific list of DHCP server(s) (Michael Brown)<br>
2. Re: iPXE with specific list of DHCP server(s) (Shantanu Gadgil)<br>
3. Re: iPXE with specific list of DHCP server(s) (James A. Peltier)<br>
4. Re: iPXE with specific list of DHCP server(s) (James A. Peltier)<br>
5. Re: iPXE with specific list of DHCP server(s) (Marin Hannache)<br>
6. Re: iPXE with specific list of DHCP server(s) (Gene Cumm)<br>
7. undionly boot port (Larry Brigman)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 14 Oct 2013 15:10:06 +0100<br>
From: Michael Brown <<a href="mailto:mbrown@fensystems.co.uk">mbrown@fensystems.co.uk</a>><br>
To: Shantanu Gadgil <<a href="mailto:shantanugadgil@yahoo.com">shantanugadgil@yahoo.com</a>><br>
Cc: <a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
Subject: Re: [ipxe-devel] iPXE with specific list of DHCP server(s)<br>
Message-ID: <<a href="mailto:525BFB3E.1050004@fensystems.co.uk">525BFB3E.1050004@fensystems.co.uk</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
On 14/10/13 08:13, Shantanu Gadgil wrote:<br>
> I was wondering if I can *specify* the the DHCP server(s) that I want iPXE to accept OFFERs from (using IP address) and ignore others.<br>
> The situation is that there could be more than one DHCP server.<br>
<br>
There is no support for doing this in iPXE. Such a requirement would<br>
normally indicate that the network is misconfigured; what is the<br>
motivation for wanting this functionality?<br>
<br>
Michael<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 14 Oct 2013 11:39:19 -0700 (PDT)<br>
From: Shantanu Gadgil <<a href="mailto:shantanugadgil@yahoo.com">shantanugadgil@yahoo.com</a>><br>
To: <a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
Subject: Re: [ipxe-devel] iPXE with specific list of DHCP server(s)<br>
Message-ID:<br>
<<a href="mailto:1381775959.64904.YahooMailBasic@web141001.mail.bf1.yahoo.com">1381775959.64904.YahooMailBasic@web141001.mail.bf1.yahoo.com</a>><br>
Content-Type: text/plain; charset=iso-8859-1<br>
<br>
<br>
--------------------------------------------<br>
On Mon, 10/14/13, Michael Brown <<a href="mailto:mbrown@fensystems.co.uk">mbrown@fensystems.co.uk</a>> wrote:<br>
<br>
On 14/10/13 08:13, Shantanu Gadgil<br>
wrote:<br>
> I was wondering if I can *specify* the the DHCP<br>
server(s) that I want iPXE to accept OFFERs from (using IP<br>
address) and ignore others.<br>
> The situation is that there could be more than one DHCP<br>
server.<br>
<br>
There is no support for doing this in iPXE.? Such a<br>
requirement would normally indicate that the network is<br>
misconfigured; what is the motivation for wanting this<br>
functionality?<br>
<br>
'Misconfiguration' ... I don't think so! :)<br>
/If the dhclient protocol/config/whatever has a 'reject' setting, why can't it have a<br>
an 'accept_only' setting?/<br>
<br>
That said, let me explain the real situation ...<br>
<br>
The IT guys already have one DHCP server running per subnet. (for network booting)<br>
<br>
I want to deploy my own PXE booting network, parallel to theirs to try out iPXE.<br>
(which would point the PXE clients to *my* installation server, rather than theirs.<br>
<br>
Having this feature allows me to test an alternate configuration even when the machine's<br>
MAC address is present in the IT network.<br>
<br>
Regards,<br>
Shantanu<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 14 Oct 2013 14:51:01 -0700 (PDT)<br>
From: "James A. Peltier" <<a href="mailto:jpeltier@sfu.ca">jpeltier@sfu.ca</a>><br>
To: Shantanu Gadgil <<a href="mailto:shantanugadgil@yahoo.com">shantanugadgil@yahoo.com</a>><br>
Cc: <a href="mailto:ipxe-devel@ipxe.org">ipxe-devel@ipxe.org</a><br>
Subject: Re: [ipxe-devel] iPXE with specific list of DHCP server(s)<br>
Message-ID:<br>
<<a href="mailto:104342734.434177757.1381787461211.JavaMail.root@jaguar10.sfu.ca">104342734.434177757.1381787461211.JavaMail.root@jaguar10.sfu.ca</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
----- Original Message -----<br>
|<br>
| --------------------------------------------<br>
| On Mon, 10/14/13, Michael Brown <<a href="mailto:mbrown@fensystems.co.uk">mbrown@fensystems.co.uk</a>> wrote:<br>
|<br>
| On 14/10/13 08:13, Shantanu Gadgil<br>
| wrote:<br>
| > I was wondering if I can *specify* the the DHCP<br>
| server(s) that I want iPXE to accept OFFERs from (using IP<br>
| address) and ignore others.<br>
| > The situation is that there could be more than one DHCP<br>
| server.<br>
|<br>
| There is no support for doing this in iPXE.? Such a<br>
| requirement would normally indicate that the network is<br>
| misconfigured; what is the motivation for wanting this<br>
| functionality?<br>
|<br>
| 'Misconfiguration' ... I don't think so! :)<br>
| /If the dhclient protocol/config/whatever has a 'reject' setting, why<br>
| can't it have a<br>
| an 'accept_only' setting?/<br>
|<br>
| That said, let me explain the real situation ...<br>
|<br>
| The IT guys already have one DHCP server running per subnet. (for<br>
| network booting)<br>
|<br>
| I want to deploy my own PXE booting network, parallel to theirs to<br>
| try out iPXE.<br>
| (which would point the PXE clients to *my* installation server,<br>
| rather than theirs.<br>
|<br>
| Having this feature allows me to test an alternate configuration even<br>
| when the machine's<br>
| MAC address is present in the IT network.<br>
|<br>
| Regards,<br>
| Shantanu<br>
<br>
Which is exactly a network misconfiguration. You're attempting to circumvent your IT Services infrastructure in favour of your own. If you want a test bed, set on up. You don't need a "real" network to test iPXE.<br>
<br>
--<br>
James A. Peltier<br>
Manager, IT Services - Research Computing Group<br>
Simon Fraser University - Burnaby Campus<br>
Phone : <a href="tel:778-782-6573" value="+17787826573">778-782-6573</a><br>
Fax : <a href="tel:778-782-3045" value="+17787823045">778-782-3045</a><br>
E-Mail : <a href="mailto:jpeltier@sfu.ca">jpeltier@sfu.ca</a><br>
Website : <a href="http://www.sfu.ca/itservices" target="_blank">http://www.sfu.ca/itservices</a><br>
<br>
?A successful person is one who can lay a solid foundation from the bricks others have thrown at them.? -David Brinkley via Luke Shaw<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 14 Oct 2013 14:58:50 -0700 (PDT)<br>
From: "James A. Peltier" <<a href="mailto:jpeltier@sfu.ca">jpeltier@sfu.ca</a>><br>
To: Shantanu Gadgil <<a href="mailto:shantanugadgil@yahoo.com">shantanugadgil@yahoo.com</a>><br>
Cc: <a href="mailto:ipxe-devel@ipxe.org">ipxe-devel@ipxe.org</a><br>
Subject: Re: [ipxe-devel] iPXE with specific list of DHCP server(s)<br>
Message-ID:<br>
<<a href="mailto:2058778954.434181918.1381787930625.JavaMail.root@jaguar10.sfu.ca">2058778954.434181918.1381787930625.JavaMail.root@jaguar10.sfu.ca</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
----- Original Message -----<br>
| ----- Original Message -----<br>
| |<br>
| | --------------------------------------------<br>
| | On Mon, 10/14/13, Michael Brown <<a href="mailto:mbrown@fensystems.co.uk">mbrown@fensystems.co.uk</a>> wrote:<br>
| |<br>
| | On 14/10/13 08:13, Shantanu Gadgil<br>
| | wrote:<br>
| | > I was wondering if I can *specify* the the DHCP<br>
| | server(s) that I want iPXE to accept OFFERs from (using IP<br>
| | address) and ignore others.<br>
| | > The situation is that there could be more than one DHCP<br>
| | server.<br>
| |<br>
| | There is no support for doing this in iPXE.? Such a<br>
| | requirement would normally indicate that the network is<br>
| | misconfigured; what is the motivation for wanting this<br>
| | functionality?<br>
| |<br>
| | 'Misconfiguration' ... I don't think so! :)<br>
| | /If the dhclient protocol/config/whatever has a 'reject' setting,<br>
| | why<br>
| | can't it have a<br>
| | an 'accept_only' setting?/<br>
| |<br>
| | That said, let me explain the real situation ...<br>
| |<br>
| | The IT guys already have one DHCP server running per subnet. (for<br>
| | network booting)<br>
| |<br>
| | I want to deploy my own PXE booting network, parallel to theirs to<br>
| | try out iPXE.<br>
| | (which would point the PXE clients to *my* installation server,<br>
| | rather than theirs.<br>
| |<br>
| | Having this feature allows me to test an alternate configuration<br>
| | even<br>
| | when the machine's<br>
| | MAC address is present in the IT network.<br>
| |<br>
| | Regards,<br>
| | Shantanu<br>
|<br>
| Which is exactly a network misconfiguration. You're attempting to<br>
| circumvent your IT Services infrastructure in favour of your own.<br>
| If you want a test bed, set on up. You don't need a "real" network<br>
| to test iPXE.<br>
|<br>
| --<br>
| James A. Peltier<br>
| Manager, IT Services - Research Computing Group<br>
| Simon Fraser University - Burnaby Campus<br>
| Phone : <a href="tel:778-782-6573" value="+17787826573">778-782-6573</a><br>
| Fax : <a href="tel:778-782-3045" value="+17787823045">778-782-3045</a><br>
| E-Mail : <a href="mailto:jpeltier@sfu.ca">jpeltier@sfu.ca</a><br>
| Website : <a href="http://www.sfu.ca/itservices" target="_blank">http://www.sfu.ca/itservices</a><br>
|<br>
| ?A successful person is one who can lay a solid foundation from the<br>
| bricks others have thrown at them.? -David Brinkley via Luke Shaw<br>
<br>
I should mention the following. If you have a DHCP server that is local to the network and it answers faster than the IT Services DHCP server your requests *MAY* be answered by it first. However, you should only use such a configuration with the deny unknown-clients DHCP option so that your server doesn't answer requests for any other hosts other than your test hosts.<br>
<br>
Keep in mind that this is a big if your server answers first. You may end up getting a request from yours then a request from theirs than a request from theirs then a request from yours, not having ANY clue other than the server IP that's answering the request to know if your "testing" is working.<br>
<br>
To me, fundamentally your testing methodology is broken.<br>
<br>
--<br>
James A. Peltier<br>
Manager, IT Services - Research Computing Group<br>
Simon Fraser University - Burnaby Campus<br>
Phone : <a href="tel:778-782-6573" value="+17787826573">778-782-6573</a><br>
Fax : <a href="tel:778-782-3045" value="+17787823045">778-782-3045</a><br>
E-Mail : <a href="mailto:jpeltier@sfu.ca">jpeltier@sfu.ca</a><br>
Website : <a href="http://www.sfu.ca/itservices" target="_blank">http://www.sfu.ca/itservices</a><br>
<br>
?A successful person is one who can lay a solid foundation from the bricks others have thrown at them.? -David Brinkley via Luke Shaw<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 15 Oct 2013 00:20:02 +0200<br>
From: Marin Hannache <<a href="mailto:mareo@mareo.fr">mareo@mareo.fr</a>><br>
To: "James A. Peltier" <<a href="mailto:jpeltier@sfu.ca">jpeltier@sfu.ca</a>><br>
Cc: <a href="mailto:ipxe-devel@ipxe.org">ipxe-devel@ipxe.org</a><br>
Subject: Re: [ipxe-devel] iPXE with specific list of DHCP server(s)<br>
Message-ID: <<a href="mailto:20131014222002.GA23635@prometheus.mareo.fr">20131014222002.GA23635@prometheus.mareo.fr</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi,<br>
<br>
On Mon, Oct 14, 2013 at 02:58:50PM -0700, James A. Peltier wrote:<br>
> Keep in mind that this is a big if your server answers first. You may end up<br>
> getting a request from yours then a request from theirs than a request from<br>
> theirs then a request from yours, not having ANY clue other than the server<br>
> IP that's answering the request to know if your "testing" is working.<br>
<br>
Make the rogue DHCP server send the "priority" setting should do the trick even<br>
if it does not answers first.<br>
<br>
This might be used as a workaround, but as James stated, you should do the<br>
testing part on a network you are in full control of. Howewer, if you choose to<br>
not follow this advice, make sure your server is configured as "not<br>
authoritative", failing to do so will make your DHCP server denying leases<br>
offered by the regular DHCP server.<br>
<br>
Regards,<br>
<br>
--<br>
Marin Hannache<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Mon, 14 Oct 2013 23:21:56 -0400<br>
From: Gene Cumm <<a href="mailto:gene.cumm@gmail.com">gene.cumm@gmail.com</a>><br>
To: Shantanu Gadgil <<a href="mailto:shantanugadgil@yahoo.com">shantanugadgil@yahoo.com</a>><br>
Cc: <a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
Subject: Re: [ipxe-devel] iPXE with specific list of DHCP server(s)<br>
Message-ID:<br>
<CAD0RxekvArERTXYHSEYH56S-1Cw6-iSZA=<a href="mailto:TOk1nqWP1iNU2RNw@mail.gmail.com">TOk1nqWP1iNU2RNw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Mon, Oct 14, 2013 at 2:39 PM, Shantanu Gadgil<br>
<<a href="mailto:shantanugadgil@yahoo.com">shantanugadgil@yahoo.com</a>> wrote:<br>
<br>
> The IT guys already have one DHCP server running per subnet. (for network booting)<br>
><br>
> I want to deploy my own PXE booting network, parallel to theirs to try out iPXE.<br>
> (which would point the PXE clients to *my* installation server, rather than theirs.<br>
<br>
This actually is a clear misconfiguration UNLESS they're doing IP<br>
config and you're only doing PXE boot data (sname, file). It's<br>
allowed per PXE.<br>
<br>
Few things to keep in mind:<br>
<br>
- Talk with your IT department on how to do this right. It will save<br>
a lot of aggravation on both sides.<br>
- Be willing to accept that you may need to physically separate your<br>
PXE test system so it can't talk on the normal network.<br>
- Good switches have DHCP guard which will put the port that hears the<br>
DHCP reply into a non-forwarding state (linked but nothing works)<br>
- Some switches also have a MAC guard where they'll put a port that<br>
sees multiple MAC addresses into a non-forwarding state.<br>
- The passthrough port on a VoIP phone with passthrough can often be<br>
disabled with a checkbox.<br>
- They may have already set the DHCP priority<br>
- Why not set your clients to reject the known IT servers WHILE your<br>
server only sends replies to known clients?<br>
- Some Acceptable Use Policies include stipulations to the effect of<br>
disrupting network operations (which this is) and disciplinary<br>
measures including termination<br>
- If your network guy is extremely strict and saw one of your office<br>
ports in DHCP guard block, he'd probably issue a warning via the<br>
proper organization administrative channel, turn on all available<br>
guards and consider putting all of your ports into a special group<br>
that gets completely blocked (minus VoIP phone) if any port triggers a<br>
guard block, effectively turning off the network in your office<br>
<br>
> Having this feature allows me to test an alternate configuration even when the machine's<br>
> MAC address is present in the IT network.<br>
<br>
Use a separated network (physical, by VLAN or just a bunch of isolated VMs).<br>
<br>
--<br>
-Gene<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Mon, 14 Oct 2013 22:59:07 -0700<br>
From: Larry Brigman <<a href="mailto:larry.brigman@gmail.com">larry.brigman@gmail.com</a>><br>
To: <a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
Subject: [ipxe-devel] undionly boot port<br>
Message-ID:<br>
<<a href="mailto:CAJEEjpZpOk8N7KScab54mv5TOXYnMmjFA6Ly%2Bb13Za7ewDeP_w@mail.gmail.com">CAJEEjpZpOk8N7KScab54mv5TOXYnMmjFA6Ly+b13Za7ewDeP_w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I'm trying to find the equivalent function that pxelinux provided<br>
or maybe it's not what I think it is.<br>
<br>
In the pxelinux configuration files<br>
I get a way to pass the ksdevice to a the kernel via<br>
ksdevice=bootif<br>
and this seems to be set with IPAPPEND 2<br>
<br>
Because the servers that I boot have as many as 18 interfaces,<br>
this process in pxelinux helps to remove some extra hand holding<br>
as the BIOS on these machines is configure to only pxeboot on<br>
a single interface.<br>
<br>
Watching ipxe load, I know that it knows which interface it loaded from.<br>
Is there anyway to make use of that data without going looping through all<br>
the interfaces.<br>
<br>
This would be easy if all the servers are the same but I have at least<br>
eight differently configured<br>
servers that we pxeboot on a regular basis. Lab install testing<br>
environment.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20131014/bf69ea0a/attachment-0001.html" target="_blank">http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20131014/bf69ea0a/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
ipxe-devel mailing list<br>
<a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
<br>
<br>
End of ipxe-devel Digest, Vol 41, Issue 10<br>
******************************************<br>
</blockquote></div><br></div>