🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.sysadmin
Article #2396

Re: Setting up a home LAN with NEXSTEP/Unix

#2396
From: Gary Palmer
Date: Mon, 09 May 1994 17:26
40 lines
3462 bytes
In article <2qipqu$m29@portal.gmu.edu>,
Christian Smith <csmith@blackplague.gmu.edu> wrote:
>Ok, here is what you should do.  Since the NeXT is using Slip to get to the
>outside world, it has TWO network interfaces, call them slip0 and en0.  Each
>of these should have its own ip address.  The slip0 interface will get its
>ip from the slip server you connect to.  The en0 interface will get its ip
>address from /etc/hostconfig.  Now, you have two choices

Erm, I dunno much about NeXT, but FreeBSD (and other Unixes) can
run quite happily with the SLIP i/f address set to the ethernet card
address, since routing is done by the SLIP's destination address,
not by it's local address (AFAIK). I can say this (with a bit of
uncertainty) as the machine I am sending this from has a SLIP i/f to
Netcom (designation 'sl0'), and a Ethernet i/f toa 10bT LAN (designated
'ed1'). Both have been ifconfiged to have the same local IP address, and a
default route has been set to the gateway machine at the other end of the SLIP
link, with the ifconfig for the ed1 card setting the route
to the LAn correctly. Unless NeXT does things differently, only
one IP address should be needed by the NeXT. Certainly,
2 (or more) IP addresses are needed for machines with multiple IP i/f's
of a more traditional nature (ethernet, FDDI, etc), but I think most SLIP
implimentations would fall over if the 'en0' and the 'sl0' were given
separate IP addresses.

*However* I could be wrong, but this setup works fine for us.

>Choice one is easy, choice two involves setting routed on the next, and getting
>you slip prrovider to set you up with a subdomaine, which they might or might
>not be willing to do.  I can't help you out to much with this one.

Again, AFAIK, routed isn't needed unless there are multiple possible
routes to the smae destination. All that is needed for SLIP is a default
route entry, made just after the SLIP interface is brought up.

Hope this help, and doesn't confuse anyone!

BTW: Can anyone give more details of the Nutshell routing book,
     e.g. ISBN, etc? Thanks

Gary
Technical Details
Message-ID: <2qlrpl$c9b@baird.xap.com>
Path: arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!hookup!swrinde!sdd.hp.com!ihnp4.ucsd.edu!library.ucla.edu!csulb.edu!csus.edu!netcom.com!netcomsv!xap.com!xap.com!not-for-mail
References: <2qic19$479@crl.crl.com> <2qipqu$m29@portal.gmu.edu>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f9325,193439804b075481
X-Google-Attributes: gidf9325,public
X-Google-Thread: 10183f,193439804b075481
X-Google-Attributes: gid10183f,public
X-Google-Thread: 10ddbc,193439804b075481
X-Google-Attributes: gid10ddbc,public
X-Google-Thread: 1035b6,193439804b075481
X-Google-Attributes: gid1035b6,public
X-Google-Thread: 103cba,193439804b075481
X-Google-Attributes: gid103cba,public
X-Google-Thread: 1156c9,193439804b075481
X-Google-Attributes: gid1156c9,public
X-Google-ArrivalTime: 1994-05-09 10:58:54 PST
Path: arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!hookup!swrinde!sdd.hp.com!ihnp4.ucsd.edu!library.ucla.edu!csulb.edu!csus.edu!netcom.com!netcomsv!xap.com!xap.com!not-for-mail
From: Gary Palmer <pesky@scoob.xap.com>
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.misc,comp.sys.mac.comm,comp.sys.mac.system,comp.protocols.tcp-ip,ca.unix
Subject: Re: Setting up a home LAN with NEXSTEP/Unix
Date: 9 May 1994 10:26:59 -0700
Organization: XAP Company, Inc.
Lines: 40
Sender: pesky@xap.com
Distribution: ca
Message-ID: <2qlrpl$c9b@baird.xap.com>
References: <2qic19$479@crl.crl.com> <2qipqu$m29@portal.gmu.edu>
NNTP-Posting-Host: baird.xap.com
X-ORIGINAL-NEWSGROUPS: comp.sys.next.sysadmin,comp.sys.next.misc,comp.sys.mac.comm,comp.sys.mac.system,comp.protocols.tcp-ip,ca.unix