-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am frequently in a situation where I have a machine sitting behind NAT which means it doesn't see the real network DHCP server and PXE parameters. Two examples: * Using VirtualBox with default NAT networking (bridging is tedious) * A machine that normally uses wireless but is being NAT'ed to real network for OS installation I have been looking for and failed to find some sort of booting solution that would try to do DHCP, let me manually enter/override network and PXE configuration then proceed to do a PXE boot. I would need to be able to boot this solution via PXE itself (for VirtualBox) or by CD. I couldn't see how to do interactive input with gpxe and pxe/syslinux seems to have most of the pieces in place but appears to need more code written. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIU08KmOOfHg372QQRAv9vAKCchwWe1WpqsvgsMO9bDDbJUaiLBQCgpR9a 5uvomIMbGChkP04+Vc9elBE=tNHa -----END PGP SIGNATURE-----
Roger Binns wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I am frequently in a situation where I have a machine sitting behind NAT > which means it doesn't see the real network DHCP server and PXE > parameters. Two examples: > > * Using VirtualBox with default NAT networking (bridging is tedious) > * A machine that normally uses wireless but is being NAT'ed to real > network for OS installation > > I have been looking for and failed to find some sort of booting solution > that would try to do DHCP, let me manually enter/override network and > PXE configuration then proceed to do a PXE boot. I would need to be > able to boot this solution via PXE itself (for VirtualBox) or by CD. > > I couldn't see how to do interactive input with gpxe and pxe/syslinux > seems to have most of the pieces in place but appears to need more code > written. >Hi there, You should be able to use gPXE as the ROM-level loader with static configuration to bootstrap PXELINUX. -hpa