🚀 go-pugleaf

I have the Louis Mamakos version of SLIP for the NeXT and I having trouble
configuring a NeXT to act as a server.

I have the following setup:
	A NeXT at home called 'frodo'
	A NeXT at work called 'gandalf'

I want 'gandalf' to act as my SLIP server. The dial-out procedure for 'frodo'
attempts dial-out and the modem then connects with 'gandalf' at work. However,
the syslog file gives the following error:

Oct  3 13:34:35 frodo tcldiald[130]: Authorized packet [140.165.32.210 -> 140.165.32.59], proto TCP (6)
Oct  3 13:34:35 frodo tcldiald[130]: Started pid 566 to bring up interface slip0
Oct  3 13:34:36 frodo diald-slip0[566]: tracing TCL commands
Oct  3 13:34:36 frodo diald-slip0[566]: makecall: Attempting connection to "gandalf.tbe.com" via "slip0"
Oct  3 13:34:36 frodo diald-slip0[566]: (Begin unix.tcl for interface slip0 site gandalf.tbe.com)
Oct  3 13:34:36 frodo diald-slip0[566]: (mtu 1006 atimeo 300 wtimeo 300 ipkts 0 opkts 0)
Oct  3 13:34:36 frodo diald-slip0[566]: (Start of ZyXEL dialing script, dialing xxx-xxxx)
Oct  3 13:34:37 frodo diald-slip0[566]: (Modem firmware version U1496E  V M4.13)
Oct  3 13:34:37 frodo diald-slip0[566]: (set parameters)
Oct  3 13:34:37 frodo diald-slip0[566]: (Dialing xxx-xxxx)
Oct  3 13:35:04 frodo diald-slip0[566]: (Connected ^M)
Oct  3 13:35:04 frodo diald-slip0[566]: (Begin Unix login)
Oct  3 13:35:27 frodo diald-slip0[566]: Script Error: waiting for password
Oct  3 13:35:27 frodo diald-slip0[566]: Error Code: NONE
Oct  3 13:35:27 frodo diald-slip0[566]: Error Info:
Oct  3 13:35:27 frodo diald-slip0[566]: Script Error: waiting for password
Oct  3 13:35:27 frodo diald-slip0[566]: End Error Info.
Oct  3 13:35:27 frodo diald-slip0[566]: failcall: Did SIOCFAILCALL on "slip0"
Oct  3 13:35:27 frodo diald-slip0[566]: failcall: Script "/usr/dialupip/config/slip-srv.script" for "gandalf.tbe.com" failed
Oct  3 13:35:27 frodo tcldiald[130]: Child pid 566 for slip0/gandalf.tbe.com exited.

(tel. numbers x'ed out)

I am using the provided login-unix.tcl script as provided in the package.
The problem probably lies in the server 'slip' account configuration, since
Louis does not discuss setting up the server side in any kind of detail.
I have an account on 'gandalf' that possesses the following settings:

Enter user identifier (login or uid): slip0
Entry is now:
   1)  login ...... slip0
   2)  password ... (none)
   3)  name ....... 
   4)  userid ..... 100
   5)  groupid .... 4 (uucp)
   6)  login dir .. /
   7)  login sh ... /usr/dialupip/bin/dudisc_slip0
   
Is this what I should have on the server side? I also made a copy of
/usr/dialupip/bin/dudisc and renamed it /usr/dialupip/bin/dudisc_slip0.

The server (gandalf) also has the following config.slip file entry for SLIP0
which I believe is correct:

SLIP0LOCAL=140.165.32.59
# remote set the same since the dial-in machine id changes
SLIP0REMOTE=140.165.32.59
SLIP0NETMASK=255.255.255.0
SLIP0CONFIG=SLIP
SLIP0DEFAULT=NO

What's the deal with the password -- or is my account spec for slip0 screwed?
Or do I have to have a .netrc on the client side????

Michael McCulloch
Huntsville, AL
mmcculloch@nebula.tbe.com