Thread View: comp.sys.next.sysadmin
2 messages
2 total messages
Started by Michael McCulloch
Sat, 03 Oct 1992 19:23
SLIP Server Configuration
Author: Michael McCulloch
Date: Sat, 03 Oct 1992 19:23
Date: Sat, 03 Oct 1992 19:23
68 lines
3641 bytes
3641 bytes
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
Re: SLIP Server Configuration
Author: Louis A. Mamakos
Date: Sun, 04 Oct 1992 15:09
Date: Sun, 04 Oct 1992 15:09
63 lines
3278 bytes
3278 bytes
In article <1992Oct3.192357.3207@mnemosyne.cs.du.edu> lmccullo@nyx.cs.du.edu (Michael McCulloch) writes:
>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:
Let's examine the log closely...
>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)
Here's the telling error, of course:
>Oct 3 13:35:27 frodo diald-slip0[566]: Script Error: waiting for password
Looking at the fragment of the TCL script that generates this error:
expect timeout {error "waiting for password"} "*assword:*"
We see that it is expecting to see a Password: prompt from the other
side.
>I have an account on 'gandalf' that possesses the following settings:
>
>Enter user identifier (login or uid): slip0
>Entry is now:
> 1) login ...... slip0
I believe that this is your problem. The /bin/login program won't prompt for a
password unless there is one present on the account.
> 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.
There is a command /usr/dialupip/bin/duinstall which will do this for
you. Actually, it just makes links to the dudisc program.
>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????
I would either modify the login-unix.tcl script to not expect a password
prompt, or add a password to the account and have the login-unix.tcl script
supply it when asked.
louie
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads