Tellurian 


Tellurian Pty Ltd 
272 Prospect Road 
Prospect  SA  5082 
Australia 

ACN 069 073 267 


ph. +61 8 8408 9600 
fax. +61 8 8408 9614 




































Tellurian BootpdNT

A bootp service for
Windows NT and Windows 95

Author: Drew Ames, Tellurian Pty Ltd ACN 067 073 267
Copyright (c) Tellurian Pty Ltd, 1996-1999
trinkets@tellurian.com.au
23 November, 1997

Tellurian BootpdNT is a service for Windows* NT Workstation or Server, which complies to the Internet RFCs 951 and 1533 for the bootp protocol.   It also works stand alone in Windows 95.   With Tellurian BootpdNT, your Windows NT or Windows 95 computer can be the Internet Address server for your organisation's network.

This document describes the installation, care and feeding of your bootp service to ensure a long and satisfying relationship between you, your service and the network you are running.

* Windows, Windows NT and Windows 95 are trademarks of Microsoft.   iNTernet trinket is a trademark of Tellurian.

Installation for Windows NT

Place the BootpdNT.EXE file in the directory you wish it to permanently reside, change to this directory then run:

bootpdNT --install
This will place an entry in the registry for a service called bootpdNT which will execute bootpdNT.EXE from this directory.   If you move BootpdNT to a different directory you will have to update the registry; the easiest way is to re-install it.

By default Tellurian bootpdNT will be registered as a manually started service.   When started it expects to find a file called c:\tftpboot\bootptab for it's database of clients and IP addresses, and will create a log file called c:\logs\bootp\bootp.log.

Installation for Windows 95

There are no special installation instructions for Windows 95.   Simply place the BootpdNT.EXE file in the directory you wish it to reside.   When started it expects to find a file called c:\tftpboot\bootptab for it's database of clients and IP addresses, and will create a log file called c:\logs\bootp\bootp.log.

De-Installation for Windows NT

Tellurian BootpdNT can be de-installed in two steps:

1. Stop the service (if it is running).

2. From the DOS command line, run:

bootpdNT --remove

This will remove all Registry entries created.   The bootpdNT.EXE file can then be deleted with safety.

De-Installation for Windows 95

Tellurian BootpdNT can be de-installed in three steps:

1. Stop the program (if it is running).

2. Re-start it with the following DOS command line:

bootpdNT --win95 -r

3. Stop it again.

This will remove your site-specific default configuration values.   The bootpdNT.EXE file can then be deleted with safety.

Running under Windows NT

To start Tellurian BootpdNT under Windows NT, open the Services control panel, hilight the bootpdNT entry and click the Start button.   You can specify startup parameters to set the location of the log file, the bootptab file, the debug level and such.

Consult the Windows NT Workstation Help files on starting and stopping services for information on general operating procedures.   Issues specific to Tellurian bootpdNT follow...

In DOS command mode, Tellurian bootpdNT supports the following command arguments:

--install Place an entry in the Registry.
--remove Remove all Registry entries related to Tellurian bootpdNT.
--help Explain all possible command parameters.

Running under Windows 95

In DOS command mode, Tellurian bootpdNT supports the following command arguments:

--help Explain all possible command parameters.
--win95 [param ...] Start the program in a DOS box.

You must use the "--win95" argument to start the program under Windows 95.

Startup Parameters

When started as a service, Tellurian bootpdNT accepts parameters affecting it's operation and indicating the location of it's files.   Those parameters are entered at the bottom of the Services control panel.

When started as a Windows 95 program, the same parameters can be used, but they are typed on the command line, after the "--win95" argument.

-b <bootfile> <bootfile> represents the full pathname of the database file of clients and IP addresses.
-l <logfile> <logfile> represents the full pathname of the file to log bootp events.
-d <logginglevel> <logginglevel> is a number between 0 and 9 indicating the amount of detail desired in the log file.
0No logging is performed and a logfile is not created.
1Basic initialisation messages are generated.
2Level 1 logging PLUS Control Service events.
3Level 2 Packet dumps.
9Level 3 PLUS Full bootptab parsing information and request processing.
-p <server>:<client> Set the UDP port used to send and receive requests to <server> and <client>.
-s Save the current command parameters to the Registry for the next boot.
-r Reset the information in the Registry to the defaults mentioned under Installation.

Long filenames are supported in the bootfile and logfile parameters, but in Windows NT Services control panel it is important that you precede all backslashes (`\') and spaces (` ') with a backslash (`\').   eg. `c:\logs\bootp log.txt' must be typed as `c:\\logs\\bootp\ log.txt'.   In Windows 95 you must enclose filenames which contain spaces with double quotes.   eg. `c:\logs\bootp log.txt' must be typed as `c:\logs\bootp log.txt'.

If you need to change the default parameters or start the service automatically at boot time, start the service once manually specifying your preferred values in the Command Parameters window and include the -s option.   This will save these parameters in the Registry, and next time the service is started it will use the values in the Registry.

Any parameters specified in the Command Parameters or command line will override entries in the Registry.

Bootp's Database - bootptab

The common name for the configuration file for bootp servers is `bootptab'.   Tellurian BootpdNT can use any file name for it's database, but to avoid confusion we recommend that you use `bootptab'.   Tellurian BootpdNT supports the tags as used by CMU bootpd.   A CMU bootptab should work with only minor modifications.

Within bootptab, each entry starts with an entry name followed by a colon (`:'), a tag followed by an equals sign (`=') and a value.   The colon, tag and value are optionally repeated.

entryname:tag=value[:tag=value...]

Entries can be split over multiple lines by placing a colon at the end of the line.   Whitespace is allowed in values and between the colon and the tag but must not appear between tag and the equals sign.   Blank lines and carriage returns are ignored except for the purpose of terminating the current entry.   Comments within the file are represented by a `#' at the beginning of the line and extend to the end of the line.

All entries are case sensitive: you cannot use UPPER CASE tags where a lower case tag is expected.

Tag Value Type Description
bf String Bootfile name for requesting via tftp.
bs Integer Bootfile size for tftp transfer.
bs auto Calculate bootfile size for tftp transfer.
cs IP List List of IP addresses of Cookie servers.
df String Dumpfile name for dump server.
dn String Domain name.
ds IP List List of IP addresses of Domain Name Servers.
ef String Extensionfile name.
gw IP List List of IP addresses of Network gateways.
ha String Client hardware address expressed in hexadecimal (without a leading 0x).
hd String Base directory for the tftp transfer.
hn String The hostname for this client.   If no string is provided, the hostname is obtained by querying the DNS for the entry corresponding to this host's IP address.
im IP List List of IP addresses of Impress servers.
ip IP The internet address of the client.
lg IP List List of IP addresses of Log servers.
lp IP List List of IP addresses of lpr servers.
ns IP List List of IP addresses of IEN116 name servers.
rl IP List List of IP addresses of rlp servers.
rp String Pathname of the client's root disk.
sa IP The address to enter as the server for this client.
sm IP The subnet mask for this client.
sw IP List List of IP addresses of Swap servers.
tc String The entryname of a template of values to include with this entry.   Any template values will be superseded by values in this entry.
to Integer The time offset from GMT.
ts IP List List of IP addresses of Time servers.
Tn Value Generic tag for expansion.   The value can either be a string enclosed in double quotes, or a stream of hexadecimal digits.

A String is a list of characters.   All characters are valid except equals (`='), and colon (`:') is only allowed in strings when they separate a DOS drive letter from the rest of a filename.   An IP is a single dotted decimal Internet address.   An IP List is a list of dotted decimal Internet addresses separated by whitespace.   An Integer is a whole number consisting of the digits 0 through 9.

Each entry must have as a minimum, an entryname, a hardware address and an IP address.

Example bootptab

model1:gw=123.123.123.123:sm=255.255.255.0
model2:gw=223.223.223.223:sm=255.255.255.64

host1:tc=model1:ha=0040AC2D66BA:ip=123.123.123.1:bf=bootimage:bs=154
host2:tc=model2:ha=00402233ade1:ip=223.223.223.6:bf=bootimage:bs=auto
host3:tc=model2:ha=0040324EF165:ip=223.223.223.7:
	ds=223.223.223.6 223.223.223.9:T153="extrainfo":
	T202=4461766964207761732068657265
host4:ha=0023431236ef:ip=223.223.223.9

Limited Node Versions

Tellurian BootpdNT is made available under a variety of licences.   Some versions restrict the number of nodes which can be made available at any one time.   Please see the licence that was provided with the distribution for details of any limits applicable to you.

Copyright, Licence and Warranty

Tellurian BootpdNT is provided under one of the following licences.   Please refer to the version appropriate for you.

See Also

rfc1048.txt, rfc1084.txt, rfc1395.txt, rfc1497.txt, rfc1533.txt, rfc1534.txt, rfc2132.txt, rfc903.txt, rfc951.txt