Boot from Alternative Interface...

[robinsmidsrod]

(2011-09-16 19:36)MultimediaMan Wrote:  Is there a way to PXE boot iPXE from one interface, then iSCSI boot from another?

At the iPXE Command Prompt, when I type dhcp net0, all works normally... but when I attempt to access the other network adapter, no dice.

So do I have to specify the network drivers at compile time?

Code:

00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 82)

I believe what you want to do should be possible, but you need native drivers for both cards available, AFAIK. And you do need to either specify which drivers you want or use an all-drivers image and recompile.

Does your SiS 900 match one of these PCI vendor/product IDs?

Code:

PCI_ROM(0x1039, 0x0900, "sis900",  "SIS900", 0),
PCI_ROM(0x1039, 0x7016, "sis7016", "SIS7016", 0),

If it does, then you should be able to get access to it if you boot ipxe with the sis900 driver in the package. If you're currently booting with undionly.kpxe or something similar I assume you won't get access to it, as the driver for your sis900 is not available.

I believe the all-drivers make target is called ipxe.pxe (someone correct me if I'm wrong here) if you intend to chainload it. If you're building a ROM image for your realtek adapter you need to add two, not just one, drivers into your image. The romburning tutorial doesn't mention how to do this, but hopefully someone else can chime in and explain how to do that.

The ifstat command should help you figure out if your network card is available or not.

Once you have both cards operational (and with valid IP details) sanhook/sanboot should be able to access your resources without problems.