Examine the Boot Options

The first time you boot from a Network Security Toolkit CDROM you should press the SPACE BAR to prevent it from automatically booting. You only have a few seconds (5 secs) to do this before it boots up using the default setting.

On the keyboard you can use the F1, F2, F3, F4 and F5 keys to move between the console boot screens. You will find a wealth of information as to how you can adjust the boot options for different situations. For a serial boot, the keystrokes are slightly different for access to the boot screens. On the terminal emulator keyboard use the Ctrl+F+1, Ctrl+F+2, Ctrl+F+3, Ctrl+F+4, Ctrl+F+5 keystroke sequences.

When the Network Security Toolkit ISO image was created for public distribution, we had to guess at what settings would be the most common. We tried to provide a ISO who's default options would work for the majority of situations. If you determine that our default choices don't work for your particular situation, you will need to specify your own boot options.

If the network you are booting the Network Security Toolkit on does not have a DHCP server, the default boot options won't work. You will see errors in this situation as the Network Security Toolkit won't be able to retrieve a IP address from a DHCP server.

In this situation, you should specify base, mbase, serial, utils, pcmcia, or usb at boot time. For example:

boot: mbase

It would be very difficult to show screen captures of the console boot screens other than to take digital pictures. Thus, we will present the boot screens from a serial boot session below in lieu of console screen captures.

If the system you are using does not have a keyboard, video card, or monitor (i.e. typically this is found with server systems and is referred to as a "headless configuration"), its still possible to adjust the default boot Kernel and NST settings. If you connect a null modem cable from the first serial port (COM:1 or ttyS0) on NST to a dumb terminal or second computer, one can control the NST boot time environment.

You will need to use the following serial settings:


For example, I use the minicom program for serial communications on my Linux box. I've set up a minicom configuration named server that I use when I want to adjust the Network Security Toolkit boot process for a headless or dual monitor (i.e. both serial and console) NST system. After connecting a null modem cable between the two computers, I started up minicom on my laptop and then powered up a headless NST server with the CDROM loaded. The following captions depict the NST serial boot, configuration, option, help, and specification screens (note: these screens have been captured using development versions of the Network Security Toolkit - your screens may be slightly different):


You still need to press the SPACE BAR to disable the auto boot (if you want to customize your boot options). Also, you'll need to use Control+F+1, Control+F+2, etc instead of the function keys to toggle between the help screens.

The following captions show the available NST serial boot screens:





Note

As a side note, booting via a serial console is an excellent way to capture error messages if you have a system that has trouble booting from the Network Security Toolkit CDROM (especially if you have a kernel panic situation).