[ipxe-devel] undi interface info
Larry Brigman
larry.brigman at gmail.com
Thu Nov 7 00:49:01 UTC 2013
Replaced ipxe.pxe with undionly.kpxe and the same script and it works
without the
extra cycling through all the interfaces.
Thanks.
On Wed, Nov 6, 2013 at 4:01 PM, Larry Brigman <larry.brigman at gmail.com>wrote:
> Does that need to be undionly.pxe file or some form of keep pxe?
> I ask because I embedded the following script with ipxe.pxe
> ---------
> #!ipxe
> autoboot netX ||
> shell
> ----------------
> and get the following during the chaining process:
> -----------------------------
> CLIENT MAC ADDR: 00 30 48 BB AB 4C GUID: 534D4349 0002 BB48 3000
> BB4830004CAB
> CLIENT IP: 134.242.160.142 MASK: 255.255.252.0 DHCP IP:
> 134.242.160.248
> GATEWAY IP:
> 134.242.160.254
> PXE->EB: !PXE at 94CB:0070, entry point at
> 94CB:0106
> UNDI code segment 94CB:44B0, data segment 8E92:6390
> (570-613kB)
> UNDI device is PCI 06:00.0, type
> DIX+802.3
> 613kB free base memory after PXE
> unload
> iPXE initialising
> devices...ok
>
>
>
>
>
> iPXE 1.0.0+ (7405) -- Open Source Network Boot Firmware -- http://ipxe.org
>
> Features: HTTP iSCSI DNS TFTP AoE SRP bzImage ELF MBOOT PXE PXEXT
> Menu
> "netX": no such network
> device
> iPXE>
>
>
>
> On Wed, Nov 6, 2013 at 2:23 PM, Brian Rak <brak at gameservers.com> wrote:
>
>> Use the netX variables. These refer to whatever interface was it booted
>> off of.
>>
>>
>> On 11/6/2013 4:46 PM, Larry Brigman wrote:
>>
>> During chain loading of ipxe is there some way
>> to determine which interface ipxe was loaded from?
>>
>> Without this info, I will need to embed a script to walk through
>> the smbios/product and then still its a guess at which interface to use
>> because
>> of a different number of nic cards loaded.
>>
>> Instead, Is there a way to determine motherboard nic's?
>>
>>
>>
>>
>>
>> _______________________________________________
>> ipxe-devel mailing listipxe-devel at lists.ipxe.orghttps://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20131106/ac76dc54/attachment.htm>
More information about the ipxe-devel
mailing list