Differences between version 38 and predecessor to the previous major change of WlugBladeServer.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 38 | Last edited on Sunday, October 18, 2009 1:08:27 am | by BruceKingsbury | Revert |
| Older page: | version 37 | Last edited on Saturday, October 17, 2009 11:44:44 pm | by AristotlePagaltzis | Revert |
@@ -68,9 +68,13 @@
* [Debian GNU/Linux Installation Guide: Preparing Files for TFTP Net Booting | http://www.debian.org/releases/stable/i386/ch04s05.html.en]
* [Setting Up A PXE Install Server For Multiple Linux Distributions On Debian Lenny | http://www.howtoforge.com/setting-up-a-pxe-install-server-for-multiple-linux-distributions-on-debian-lenny] (basically the same stuff, condensed)
-Only
the bottom row (<tt>eth0<
/tt>
) can be [PXE]-booted. Hopefully
the <tt>hoiho</tt> chassis has
been configured with this as the "private" network
. It's possibly also a good idea to lock down [PXE] boot to specific [MAC] addresses so no other blades can accidentally be [PXE] booted into the installer.
+On
the same blade running dhcpd
/tftpd I also configured NAT (and squid
) so that the debian installer
can fetch packages without
the blade being exposed to the public internet at all until after it's
been fully
configured and firewalled
.
+
+
It's possibly also a good idea to lock down [PXE] boot to specific [MAC] addresses so no other blades can accidentally be [PXE] booted into the installer.
+
+Only the bottom row network interfaces(<tt>eth0</tt>) can be [PXE]-booted. It seems the <tt>hoiho</tt> chassis has been configured with this as the "public" network so perhaps we should consider changing these around?
!! Files to edit
<tt>/var/lib/tftpboot/debian-installer/i386/boot-screens/menu.cfg</tt>::
