login problem with mgetty

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

this sounds very much like the typical problem that the dial-out process
doesn't create a proper UUCP Lock files ("LCK..ttyS0"). So mgetty on the
dial-out side doesn't notice that it's a dial-out process, and will
trample on the line.

In any case, please ask further questions to the mgetty mailing list
(mgetty@muc.de), as I'm very busy right now, and can't find time to answer
all mgetty usage questions.

[Mgetty development / porting things are something different, which I want
to concentrate on!]

gert


Iouri A.Kropatchev wrote:
> Hello Mr Gert,
> 
> Sorry for direct e-mail but I have faced the following problem:
> 
> I am using Slackware Linux v2.0.30 and diald-0.16 from sunsite.unc.edu.
> I have organized dynamic PPP-link between two Linux boxes over serial line;
> both computers have external Hayes modems connected to serial ports ('ttyS0').
> Both computers are running 'mgetty'.
> 
> To automatical establishment PPP-link with diald,
> the last uses modified chat-script that come in diald-package.
> Each Linux has account name 'ppp' and '/usr/sbin/pppd' -call
> in the 'passwd'-file for 'ppp'-name;
> a password is not required.
> So to start pppd at another end of the line after initial connecting,
> the 'chat' simply sends name 'ppp',
> 
> Initially the link was very unstable; very often when diald called chat
> and the last sent the name, pppd was not invoked.
> Analizing log-files shown that in that case 'mgetty' at receiving end
> received not only the 'ppp'-word sent by 'chat'
> but also several additional characters;
> usually they were part of '/etc/issue'
> which was just before sent to 'chat' by 'mgetty'.
> 
> After eliminating sending by 'mgetty' all additional words except 'login:'
> situation became more stable regarding
> receiving correct name and invoking pppd.
> However it is still unreliable:
> time to time 'mgetty'-log contains record like
>  'time' yS0 match: user='login:ppp', key='' and etc.
> and such a case there is no a pppd started,
> because 'login' cannot find such user.
> At sending end, 'chat' logs messages like
> 	chat[]: login: -- got it
> 	chat[]: send (ppp)
> 	chat[]: timeout set to 45 seconds
> 	chat[]: expect (word:)
> 	chat[]: login:login:ppp		#- here variations are possible
> 	chat[]: Password: -- got it
> 	chat[]: send (xxxxx)  	#- xxxxx - passwd
> 
> 
> The question is: what is a source of such echo?
> I briefly looked through 'logname.c' and see that 'getlogname'
> uses usual read-write operators.
> So the ping-ponging text is accumulating somewhere in kernel,
> or I am wrong.
> I would appreciate any idea regarding the source of the bug.
> 
> Thanks in advance.
> Yuri
> 
> 
> 


-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-3545980     gert.doering@physik.tu-muenchen.de
.