🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.amiga.networking
Article #413

Need PLIP help...full prob described

#413
From: Johnson Brett E
Date: Sat, 05 Aug 1995 02:37
129 lines
5821 bytes
   I have 2 Amiga 3000's and want to network them together and use NFS.
Both computers are 25MHz and each have 10 megs of RAM.  My main
computer (Amiga#2) has a Quantum 105LPS, a Quantum 730LT, and a HD
floppy drive.  The other computer (Amiga#5) just has 1 LD floppy
(that's why I want NFS).  Both Amigas are running Workbench 3.1b.
   I have installed AmiTCP/IP 4.0 demo and gotten everything exaclty
how I want it using CSLIP (so NFS IS WORKING PROPERLY).  CSLIP is nice
and has its uses, but it's too slow (5k/sec).
   Since the AmiTCP/IP archive doesn't have the liana.device (or
support of it), I downloaded PLIP3812src.lha and PLIP3818.lha from
comm/net.  I have built a cable as specified by the doc file and
checked it.  plip.device is in DEVS:Networks.  I have modified the
"db/interfaces" file as follows:

db/interfaces: [extract]
plip0 DEV=DEVS:Networks/plip.device UNIT=0 P2P
plip1 DEV=DEVS:Networks/plip.device UNIT=1 P2P

Amiga#2 uses the plip0 entry; Amiga#5 uses plip1.

ENV:Sana2/plip.config is created by my StartNet script.  I'm currently
using the default values provided by the example.

My db/inetd.conf NFS entry reads:  (on both computers)
amiganetfs stream    tcp nowait root amitcp:serv/netfs-server
[It works fine with CSLIP, remember.  And yes, all of the needed files
are where AmiTCP/IP can find them.]

My db/services NFS entry read:  (on both computers)
amiganetfs      2049/tcp
[It works fine with CSLIP, remember.]


My StartNet script for Amiga2 is as follows:
NOTE:  Some mail programs may word-wrap this part.  My StartNet file has 
not been word wrapped in any way on my system. :)
===============================================================

.key IPADDRESS
.bra {
.ket }
.def IPADDRESS 192.168.25.25

; log in
AmiTCP:bin/login -f root
AmiTCP:bin/umask 022
AmiTCP:AmiTCP
WaitForPort AMITCP
; Configure loop-back device
AmiTCP:bin/ifconfig lo0 localhost
; Assure that ENV:Sana2 exists
if not exists ENV:Sana2
  makedir ENV:Sana2
endif
; Create plip0 configuration file
; the docs say that plip.device looks for this...
echo "TIMEOUT=330000 PRI=15 MTU=8192 BPS=25000 RETRIES=63 " >ENV:Sana2/plip.config
; ...but I'm paranoid and created second one just in case...couldn't hurt...
echo "TIMEOUT=330000 PRI=15 MTU=8192 BPS=25000 RETRIES=63 " >ENV:Sana2/plip0.config
; Configure plip0
AmiTCP:bin/ifconfig plip0 {IPADDRESS} 192.168.25.26
; Add IP address entry for this host
rx "address AMITCP; 'ADD HOST {IPADDRESS} amiga2.brettcave.net  amiga2'"
; Add route to this host
AmiTCP:bin/route add {IPADDRESS} localhost
AmiTCP:bin/route add default 192.168.25.25
setenv HOSTNAME `AmiTCP:bin/hostname`
Assign TCP: Exists > NIL:
IF Warn
  Mount TCP: from AmiTCP:devs/Inet-Mountlist
EndIf
; Start the internet `super server'
run AmiTCP:bin/inetd

===============================================================
Notes:
Amiga2 is set up as 192.168.25.25
Amiga5 is set up as 192.168.25.26
   The Amiga5 StartNet script is just like this one except that
occurrances of plip0 have been replaced with plip1 and the IP address
numbers have been swapped accordingly (except for default gateway route
entry).
   I don't get any errors when starting these scripts from their
respective computers.
   I have tried commenting out the echo commands to kill the
plip.config files as recommended by plip.doc in times of trouble. 
There was no change in performance.

   After TCP/IP has been started on both computers, I try to test the
connection with ping.  Each computer can ping itself, so that's good. 
When I try to ping the other computer, ping displays its first line of
data and just hangs.

Example ping session from Amiga2:
===============================================================
7.SYS:> ping 192.168.25.26
PING 192.168.25.26 (192.168.25.26): 56 data bytes
{^C entered right here}
--- 192.168.25.26 ping statistics ---
17 packets transmitted, 0 packets received, 100% packet loss
7.SYS:>
===============================================================

     It almost looks like it's not finding parallel.device...but
plip.doc doesn't mention parallel.device anywhere...  I've looked
through the binary .device files and haven't found any mention of "par"
either (of course it could be binary encoded).  BTW, I have tried using
both versions of plip.device that I downloaded.
     My floppy drives work just fine and I can print from both parallel
ports without errors.  This leads me to believe that my 8520's are of
sound mind.

     By now I guess you are asking "Why doesn't he just use ParNet or
ProNet?"  There is a good answer:  I'm not particularly enthusiastic
about how ParNet works.  I tried ProNet, but that kept crashing both of
my computers simultaneously...  That's when I said forget it to both
and modified my cable for PLIP.  I also want a SLIP connection to this
UNIX workstation sitting beside me and a CSLIP or PPP connection to my
Internet account (those are still nightmares in themselves).  AmiTCP/IP
is the way to go for me. :)

     I think I have given all the information I can.  Any
help/suggestions would REALLY, REALLY be appreciated. :) :) :)  [I have
been working on this for 4 days with no success...]

                                         Thanks in advance,
                                            Brett
                                            ip47@jove.acs.unt.edu
Technical Details
Message-ID: <ip47.807590230@jove>
Path: arc1-ca.pugleaf.net!news.unt.edu!jove!ip47

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!news.unt.edu!jove!ip47
From: ip47@jove.acs.unt.edu (Johnson Brett E)
Newsgroups: comp.sys.amiga.networking
Subject: Need PLIP help...full prob described
Date: 5 Aug 95 02:37:10 GMT
Organization: University of North Texas
Distribution: inet
Message-ID: <ip47.807590230@jove>
NNTP-Posting-Host: jove.acs.unt.edu
Keywords: PLIP