This info comes from school where we have 11 network printers ( HP2100s, HP8000, HP2400) which all used boopt protocol to get their configuration from the server. Read the man pages on bootpd and bootptab. Not exactly a light read but with the attached info perhaps not so bad. Roger also advised me long ago that it must be allowed for in /etc/inetd.conf . I have just updated my linux to SuSE 7 prof. I will be installing this on my box to test it with an old HP external jet direct. To see if this works, then you can printout the HP Laserjet config page. On a 2100 just press the two buttons together and two sheets get printed out. Before it works there will be a lot of blank or default entries on the second sheet. When the printer bootps' from the network, then the entries get filled in. We use at school the ip range 180.245.138 which is Class C and uses a mask 255.255.0.0 No, we should not be using that range but it is history now and NAT works wonders. With the attached text files you will notice our ip range and mask and need to change these as necessary. A working printer is also a useful tool for testing the network, if it boots all is well, if it doesn't get out the cable tester. Hope this helps. Regards to all mike -- minkl@dircon.co.uk mike.clinch@ukuug.org School Focus responsibility This file goes in /tftpboot/hpex/, as remote1.cfg. You can rename it but you must change the referance to its name in the bootptab file. ---------------------------------------- # remote1.cfg configuration file # Reference is to be made to the /etc/bootptab file entry for the JetDirect # name: HMoff # name of printer, call it what you will # telnet: 1 # allows a telent operation to connect to it # contact: Mike , extn 5734 # just for info # allow: 180.245.138.195 # limits telnet from this ip number only # location: Big School # physical location if you need it # # set-community-name: * # can be used if needed # # banner: 0 # stops a banner page being printed This is the bootptab file from our netBSD server at school. the file lives in /etc and is read at boot time ie when bootpd starts. It is quite well documented but it took a while to find out from HP pep team that vm ,the Vendor Magic Cookie, is T144. Magic cookies are a dark art it seems! # BOOTPTAB FILE # $NetBSD: bootptab,v 1.5 1997/01/18 04:11:06 perry Exp $ # # /etc/bootptab: database for bootp server (/etc/bootpd) # Last update Mon 11/9/2000 11:03 # Blank lines and lines beginning with '#' are ignored. # # Legend: # # first field -- hostname # (may be full domain name and probably should be) # # bf Bootfile # bs Bootfile size in 512-octet blocks # cs Cookie server address list # df Merit dump file # dn Domain name # ds Domain name server address list # ef Extension file # gw Gateway address list # ha Host hardware address # hd Bootfile home directory # hn Send client's hostname to client # ht Host hardware type (see Assigned Numbers RFC) # im Impress server address list # ip Host IP address # lg Log server address list # lp LPR server address list # ns IEN-116 name server address list # nt NTP (time) Server (RFC 1129) # ra Reply address override # rl Resource location protocol server address list # rp Root path to mount as root # sa TFTP server address client should use # sm Host subnet mask # sw Swap server address # tc Table continuation (points to similar "template" host entry) # td TFTP root directory used by "secure" TFTP servers # to Time offset in seconds from UTC # ts Time server address list # vm Vendor magic cookie selector # yd YP (NIS) domain name # ys YP (NIS) server address # # Be careful about including backslashes where they're needed. Weird (bad) # things can happen when a backslash is omitted where one is intended. # # First, we define a global entry which specifies the stuff every host uses. # Dummy entries have an invalid hostname (one with a "." as first character). #.global.dummy:\ # :sm=255.255.255.0:\ # :hd=/home/nfsclient:bf=null:\ # :ds=128.32.149.141:\ # :ns=0x80020b4d 0x80020ffd:\ # :ts=0x80020b4d 0x80020ffd:\ # :to=18000: # Next, we can define different master entries for each subnet. . . #.subnet13.dummy:\ # :tc=.global.dummy:gw=128.2.13.1: # # # We should be able to use as many levels of indirection as desired. Use # your imagination. . . # # Individual entries (could also have different servers for some/all of these # hosts, but we don't really use this feature at CMU): #carnegie:tc=.subnet13.dummy:ht=ieee802:ha=7FF8100000AF:ip=128.2.11.1: #baldwin:tc=.subnet19.dummy:ht=ethernet:ha=0800200159C3:ip=128.2.11.10: #example nfs diskless client #timesink:hd=/home/nfsclient/timesink:\ # tc=.subnet149.dummy:ht=ethernet:ha=0800200168A7:ip=128.32.149.20: .global.dummy:\ :sm=255.255.0.0:\ :hd=/tftpboot:bf=riscos:\ :to=0:bs=auto:hn: # Now, we define a global entry which specifies the stuff every Remote # printer will use. .remotes.dummy: \ :sm=255.255.0.0: \ :hd=/tftpboot/hpex:\ :to=0:bs=auto:hn: # # Here we define the global entry NC will need to boot from the server # it is not yet complete #.netcomp.dummy # :sm=255.255.0.0:\ # hd=/tftpboot/nc:\ # to:=0:bs=auto:hn: # # Next, we can define different master entries for each subnet. . . .ether.dummy:\ :tc=global.dummy:sm=255.255.0.0: .d-link.dummy :sm=255.255.0.0:\ :hd=/tftpboot/dlink:\ :to=0:bs=auto:hn: # # We should be able to use as many levels of indirection as desired. Use # your imagination. . . # # Individual entries (could also have different servers for some/all of these # hosts, but we don't really use this feature at CMU): HMOff:tc=.remotes.dummy:bf=remote1.cfg:ht=ethernet:ha=0030c13bd5da:ip=180.245.1338.128:vm=rfc1048:T144="hpex/remote1.cfg": #