Subject: Re: hanging rlogin
To: None <firstname.lastname@example.org>
From: Leo Weppelman <email@example.com>
Date: 12/06/1995 14:47:00
Sorry I'm quite late in responding....
> > ' > > 3) pppd: rlogin (or 'rsh <host>') hung
> . . .
> > ' > I'm currently connected with rlogin. Seems to be allright. As you said
> > ' > that the same problem occured with MiNT, isn't there a problem at the
> > ' > remote site?
> > ' > Leo.
> > '
> > ' I can confirm this Problem. My PPP connection goes over 2 rlogin
> . . .
> > ' Is it due to my delayed PPP connection (via 2 other hosts)?
> > Oh I would think so. ALSO on my site the ppp-connection is established so:
> > I (chat) dial in a central modem-host of our department, which asked
> > the account and the account-host. After prompting for a special modem-
> > password (security is high on our RBG :-) it issues the command
> > rlogin -8 -l <account> <account-host>
> > After logging in at my account-host (on which I'm superuser :-) I send
> > /usr/local/etc/pppd proxyarp :<free-hostname> passive
> > (Then I got the Connect-msg and the two IP adresses)
> > Btw: this is not the official way to connect to our department (but the
> > only one from which I got a IP adress, which is official, i.e. can be
> > routed to the whole world!)
> > The official way is to dial and connect to a ppp-host.
> > I will try this tonight and test the rlogin behavior there.
> Aaah, I think we're on the right track !
> My current ppp-connection is (only) via our official ppp-host
> (i.e. dialin-host and ppp-host is the same) and
> I'm currently logged in with 'rlogin <myhost>' (only ONE rlogin)
> and it works fine (else I can't write this ;-) !
> Both methods (rlogin with password-input or direct rlogin with .rhost-right)
> works without problems.
> But as I preferd the other way to make my ppp connection (routing in the world
> possible, see above) what can we do to solve the bug ?
> Does it make sense to start one or both pppd in debug-mode and mail the
> output ?
I don't have the faintest idea what's causing this behaviour. I don't think
this is Atari specific. Maybe you should try current-users to see if anybody
has ideas/solutions about this.