9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: James A. Robinson Jim.Robinson@Stanford.Edu
Subject: Yeeha! =) (was Re: [9fans] Argh -- auth checklist?)
Date: Thu, 25 Feb 1999 19:15:56 -0800	[thread overview]
Message-ID: <19990226031556.LeLr8N0GDPwsJE8lxlzmH7OHYqRmO1MX34vapUNzWhY@z> (raw)

> I'm not no authority on this matter, hwoever, the underlines
> could be enough for netkey working correctly.  It works
> fine at least in my environment.

Well the below is what I had at first, and it did NOT work:

    #
    # systems on the local network
    #
    
    #
    # Domain Name Service
    #
    dom=
        ns=cilantro.stanford.edu
        ns=cassandra.stanford.edu
        ns=caribou.stanford.edu
    dom=cilantro.stanford.edu ip=171.64.7.99
    dom=cassandra.stanford.edu ip=171.64.7.77
    dom=caribou.stanford.edu ip=171.64.7.55
     
    #
    # Networks
    #
    ipnet=highwire-net ip=36.48.0.0 ipmask=255.255.255.0
        fs=bela.stanford.edu
        ipgw=36.48.0.1
        mailgw=highwire
        cpu=ruler
        auth=ruler
    
    #
    # CPU/Auth servers
    #
    ip=36.48.0.135 ether=0060977e685a sys=ruler
        dom=ruler.stanford.edu
        bootf=/386/9pccpudisk
        proto=il
    
    #
    # File servers
    #
    ip=36.48.0.137 ether=00a02425fb61 sys=bela
        dom=bela.stanford.edu
        proto=il
    
    ... terminal entries and stuff ...

    #
    #  il services
    #
    il=ticket       port=566


The following is what I have now, and it will work as long as the
sys=ruler entry has the auth=ruler line. Various additional lines
are copied from the other ndb/local stuff people told me they had
in their systems (and if it doesn't hurt... =)

    #
    # systems on the local network
    #
    
    #
    # Domain Name Service
    #
    dom=
        ns=cilantro.stanford.edu
        ns=cassandra.stanford.edu
        ns=caribou.stanford.edu
    dom=cilantro.stanford.edu ip=171.64.7.99
    dom=cassandra.stanford.edu ip=171.64.7.77
    dom=caribou.stanford.edu ip=171.64.7.55
     
    #
    # Networks
    #
    ipnet=highwire-net
        ip=36.48.0.0
        ipmask=255.255.255.0
        ipgw=36.48.0.1
        fs=bela
        auth=ruler
    
    #
    # CPU/Auth servers
    #
    sys=ruler
        dom=ruler.stanford.edu ip=36.48.0.135 ether=0060977e685a 
        bootf=/386/9pccpudisk
        proto=il
        proto=tcp
        proto=udp
        ipnet=highwire-net
        fs=bela
        auth=ruler
    
    #
    # File servers
    #
    sys=bela
        dom=bela.stanford.edu ip=36.48.0.137 ether=00a02425fb61
        proto=il
        ipnet=highwire-net
      
    ... terminal entries and stuff ...

    #
    #  il services
    #
    il=ticket       port=566




             reply	other threads:[~1999-02-26  3:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-26  3:15 James [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-02-27  1:33 James
1999-02-26 18:21 James
1999-02-26 18:13 forsyth
1999-02-26 17:41 Dorman, Eric
1999-02-26  4:21 okamoto
1999-02-26  3:10 okamoto
1999-02-26  2:29 James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990226031556.LeLr8N0GDPwsJE8lxlzmH7OHYqRmO1MX34vapUNzWhY@z \
    --to=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).