mgetty problems
Gert Doering (gert@greenie.muc.de)
Tue, 18 Feb 1997 14:12:49 +0100
Hi,
for me this sounds like flow control problems. Make sure mgetty's setting
for DATA_FLOW and the *modems* setting agree. If the modem is set to
Xon/Xoff and the serial port is set to RTS/CTS, the behaviour you describe
would be quite typical.
I'm CC:'ing this to the mgetty mailing list, maybe someone else has some
more suggestions.
gert
Eric Harlow wrote:
>
> Hi,
>
> I recently pulled down the latest mgetty to use because of everyone
> telling me how much better it is over getty. I compiled it with the
> AutoPPP option because I have some Win95 dial-ups.
>
> I have the following problems.
>
> NT users are unable to connect. They get CRC errors - and cannot do
> anything. Right now I have them connect via a line with getty installed.
>
> Mac/C-128 users have problems. Mac users cannot connect via PPP.
> C-128 user connects with a shell - but has problems using lynx/pine
> because it looks like XON/XOFF chars are being received by the application
> (lynx, pine). I can't see what he's seeing, but it sounded ugly.
>
> Win-95 users connect great and can browse fine, but FTP transfers and
> newsgroups are dog slow. I've verified this myself. 100K file transfers
> take a half an hour if the line was answered with mgetty.
>
> I know mgetty shouldn't be the cause of the problem, but I've eliminated
> everything else as the cause. Something in the mgetty is killing the
> speed. It's not the speed of the line because I've watched the modem
> lights - it starts out just fine transferring - and then it stops... and
> waits... and waits ... and then there's a short burst... and then it
> wait... and waits...
>
> Any suggestions?
>
> -Eric
>
>
--
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