🚀 go-pugleaf

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