[dieter.meinert_at_aip.de: RIS server refuses connections]

From: Dieter Meinert <dieter.meinert_at_aip.de>
Date: Fri, 05 Nov 1999 10:16:14 +0100 (MET)

-----BEGIN PGP SIGNED MESSAGE-----

Original message below.

I received some answers overnight and it turns out that I have to
enable rsh on the boothost (which for security reasons I disabled!).

I'll give it a try but summarize before I wreck my machine.


Thanks to Sean O'Connell <sean_at_stat.Duke.EDU>, Larry Griffith
<larry_at_cs.wsc.ma.edu> and Mike Iglesias
<iglesias_at_draco.acs.uci.edu>

Sean O'Connell wrote:

If I recall correctly, that is a bug involving the path to the
RIS installation area. you may want to make sure you have the
latest patchkit installed on it.

I think there are some tips in the mailing list archives.

As an aside, joind probably should be run both as a daemon
and out of inetd (although it doesn't look like the bootp
answer is your problem.

Make sure that you have your /etc/exports set up properly:

Here is an example from one of my /etc/bootptab entries (before
I switched to using much much much more sane ISC-DHCP)

/etc/bootptab:
.ris.dec:hn:vm=rfc1048:\
        :sm=255.255.255.0:\
        :bf=/ris/kit/vmunix1:\
        :rp="myserver:/ris/kit"\
        :ht=ethernet:

myclient:tc=.ris.dec:ha=xxxxxxxxxxxx:ip=aaa.bbb.ccc.ddd:


/etc/exports:
/ris/kit -root=0 -ro myclient
/ris/ris2.a/product_1 -root=0 -ro myclient
/var/adm/ris/ris2.alpha/kit -root=0 -ro myclient

where /ris/kit is a sym link to /var/adm/ris/ris2.alpha/kit
and so is /ris/ris2.a/product_1
==================================================================
Larry Griffith wrote:

        I've had your problem several times. Usually it is caused by
the failure of a rsh command that tries to access the ris account on
the server (this command is in the setld script). Once I solved it by
giving ris a password. A second time it turned out the C2 database
was corrupted in such a way that it only affected the ris account!

        Try this command from a running client:

        rsh -l ris <ris server hostname> ls

and see if you get a listing of the ris home directory. If not,
something is wrong with the ris account on the server.
==================================================================
Mike Iglesias wrote:

bootp uses UDP, not TCP, so you won't get any response to telnets on
those ports.

setld uses rsh to do some of the installation. If you have rshd turned off
or restricted via tcp_wrappers on your system, that will cause problems
with installations.

You might try rebooting the system to clear that up.

Hubs don't send out packets with their own hardware address (they usually
don't have one). What kind of hub is it?

==================================================================
=======original message===========================================
Dear fellow managers,

I'm for the first time trying to set up a Du RIS server.
It refuses connections from any host I try to boot via network,
and also from telnet to ports 67 and 68.

My Question: Am I missing something important on the boothost
concerning boot requests ? The other network daemons (ftpd,
sendmail, walld, amandad, telnetd) all run fine.




I followed instructions in the installation guide and "sharing s/w"
guide to set up the RIS area to a degree where I should be able
to find out about the filesystem structure for postload
scripting.

When I now try to boot another host I get an error message saying:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
cannot determine root directory on boothost
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

then the installation procedure continues with the X installation
screen, allowing to partition the root disk and select file
systems.
When I finally try to select the software packages I get
something like:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
setld: Error contacting server boothost: boothost.aip.de: Connection refused
setld: cannot initialize boothost:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

My client is inserted into /etc/bootptab on the RIS boothost with
both hw-address and IP-address and is included in our DNS.

joind and tftpd are started from inetd, although joind is already
running since startup.

I also cannot telnet to port 67/68 on boothost (connection
refused) but that didn't worry me before since it might simply be
missing the correct bootp request information.

setld -l boothost:
setld: Error contacting server boothost: boothost.aip.de: Connection refused
setld: cannot initialize boothost:

Also, I get regular 10minute boot requests from the hub the boothost is
connected to identifying as a broadcast IP with the HUBs h/w
address:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
============================================================
941720320.178039 Packet arrived on Thursday November 04 13:58:40

received on address iii.jjj.xxx.255
xid=0x00001cfb secs=62011 flags=000000 chaddr=08:00:2b:a6:7a:3b
unpacked payload:
ht=1:ha=08.00.2b.a6.7a.3b:ci=0.0.0.0:gi=iii.jjj.yyy.254:sa=0.0.0.0:yi=0.0.0.0:vm=rfc1048:

seeking BOOTP client (1,6,08:00:2b:a6:7a:3b) on subnet iii.jjj.0.0
BOOTP from HW 08:00:2b:a6:7a:3b : no static binding for BOOTP client and dynamic binding not enabled

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

which is the only message logged w/ the running joind, although
at the logged times nowhere a host has been rebooted on our LAN.

on startup joind logs (I did not change anything in the
/etc/join/ databases since the installation guide does not tell
me to):

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
JOIN server startup on Thursday November 04 13:30:09
JOIN Server Release 4.1.0b for Alpha with Digital UNIX
Copyright 1992-1998 Competitive Automation, Inc. All Rights Reserved.

server dns domain name = aip.de
server nis/nis+ domain name = digital
flexlm: Dynamic name updating disable.
The policy file 'server.pcy' is (potentially) incompatible with the existing datbase. that the database remains valid in the new policy (e.g. with jdbdump) thenremove '/etc/join/.oldserver.pcy'.
JOIN server shutdown on Thursday November 04 13:30:09

JOIN server startup on Thursday November 04 13:30:09
JOIN Server Release 4.1.0b for Alpha with Digital UNIX
Copyright 1992-1998 Competitive Automation, Inc. All Rights Reserved.

server dns domain name = aip.de
server nis/nis+ domain name = digital
flexlm: Dynamic name updating disable.
canonical server IP address = iii.jjj.xxx.abc
canonical server name = boothost
debug level = 2
ignored interfaces = none
default lease duration = 86400
finite bootp auto extension = 0 secs
ttl of provisional lease = 60 secs
timeout on ICMP echo = 500 msecs
minimum legal bootp packet = 300 bytes
name service = dns
name service updateable = false
naming policy = by ipaddress
accept client name = false
ignore name ownership = false
DNS expiration tracks DHCP lease = false
update NS on every transaction = false
free list length = 8
bootp support = true
bootp addr from pool = false
registered clients only = false
listen on ppp interfaces = false
Microsoft RAS support = false
ping bootp clients = true
reply when relay on same net = true
send options in offer = false
auto-reread modified bootptab = true
validate bootp client net# = true
auto synchronise disk database = false
token ring source routing = false
FLEXlm timer = 3600 secs
release ip when client moves = false
expand BOOTP packet ? = false
send bootfile in 'file' field = false
ignore hardware type = false
force broadcast reply = false
use MAC addr as client ID = false

syncing databases

Netmasks:
Net Mask
Listening on interfaces (name ip mask bdcast):
         tu0 iii.jjj.xxx.abc 255.255.255.0 iii.jjj.xxx.255
         tu1 iii.jjj.zzz.abc 255.255.255.0 iii.jjj.zzz.255

Total active leases = 0

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

N.B.: The boothost has two network interfaces to serve to different subnets !


Tschüß,
                                                Dieter
 
  _____________________________*__________________________________
 / * dieter.meinert_at_aip.de \
 \ Dieter Meinert (- ** http://www.aip.de/~dieter/ \
  \__________________A______*__*___________________________________/
           (public pgp key from http://www.aip.de/~dieter/)

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1

iQCVAwUBOCKgXvYksnFoaQ6JAQHUjwP+IwTFvFX2sMMWKEKFAWpVLfwnnny6srBB
t3spqTcTWbcyTDHLqGcP1cQUfky4Lg1C81bANw74cGTI1rPOzbsSZHaR9UyTsedU
izBf9pyOxB1+8AhfP4winRhzMrR1fKVVRglc31CHULNH56ViFL94iojS3zhFo4xQ
iwDj/ecCE4A=
=OtiP
-----END PGP SIGNATURE-----
Received on Fri Nov 05 1999 - 09:18:06 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:40 NZDT