dial-out over mgetty

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

On Sat, 1 Aug 1998, Daniel D. Barber wrote:

> Hi,
> 
> 
> OK,  nevermind about the lock question.  It was answered in the pppd man
> page.  So now, I have my chat script set up so that it is using ttyS1.  
> 
> pppd connect 'chat -v "" ATZ OK ATDT12486651200 CONNECT "" ogin: log
> word: pass' \/dev/ttyS1 38400 lock -detach crtscts modem defaultroute
> noipdefault &
> 
> when I dial with it, everything seems to go fine until the time the
> remote ppp server is sending the ip addresses. 
> 
> Jul 31 18:00:18 Smileys chat[3529]: CONNECT -- got it 
> Jul 31 18:00:18 Smileys chat[3529]: send (^M) 
> Jul 31 18:00:18 Smileys chat[3529]: expect (ogin:) 
> Jul 31 18:00:18 Smileys chat[3529]:  28800/ARQ/V34/LAPM/V42BIS^M 
> Jul 31 18:00:20 Smileys chat[3529]: ^M 
> Jul 31 18:00:20 Smileys chat[3529]: ^M 
> Jul 31 18:00:20 Smileys chat[3529]: login: -- got it 
> Jul 31 18:00:20 Smileys chat[3529]: send (log^M) 
> Jul 31 18:00:21 Smileys chat[3529]: expect (word:) 
> Jul 31 18:00:21 Smileys chat[3529]:  ^M 
> Jul 31 18:00:23 Smileys chat[3529]: login: log^M 
> Jul 31 18:00:23 Smileys chat[3529]: Password: -- got it 
> Jul 31 18:00:23 Smileys chat[3529]: send (pass^M) 
> Jul 31 18:00:23 Smileys pppd[3527]: Serial connection established.
> Jul 31 18:00:24 Smileys pppd[3527]: Using interface ppp0
> Jul 31 18:00:24 Smileys pppd[3527]: Connect: ppp0 <--> /dev/ttyS1
> Jul 31 18:01:25 Smileys pppd[3527]: Modem hangup
> Jul 31 18:01:25 Smileys pppd[3527]: Connection terminated.
> Jul 31 18:01:25 Smileys pppd[3527]: Exit.

I used to get these all the time even before I ever used mgetty. I
complained and complained to the ISP that something was wrong on their end
with login/auth. They denied, and did what every ISP in America does; It's
that Linux you use.

Well, I say BAH on that and was able to figure out their host was so
overloaded (wow, an overloaded overselling ISP? Who would think it
possible) it was unable to log me in before their timeouts kicked in.
Anyways, consecutive dials might be successful. I switched ISP and have
never seen the problem again.

One word of advice tho. If your ISP can support PAP authentication, Linux
likes it much better. I bet you 37 cents your tech help doesn't even know
what PAP/CHAP is, but give them a call. The ISP-Hookup-HOWTO will detail
setting up PAP auth if you need docs.

> 
> 
> any ideas?
> 
> thanks,
> 
> Dan
> 
> 
> Daniel D. Barber wrote:
> > 
> > Thanks for your quick response.  A couple follow up questions:
> > 
> > Gert Doering wrote:
> > >
> > > Hi,
> > > Daniel D. Barber wrote:
> > > > CHAT:
> > > >
> > > > pppd connect 'chat -v "" ATDT12486651200 CONNECT "" ogin: log word:
> > > > pass' \/dev/cua1 38400 -detach crtscts modem defaultroute noipdefault &
> > >
> > > Add the "lock" statement to the command line, and do not use "cua1", but
> > > use ttyS1 instead.
> > >
> > 
> > Could you please show me an example of the lock statement?  do you mean
> > to add it to my dial-out chat script?  I couldn't find any reference to
> > it in "man chat".
> > 
> > When I use a regular inittab (not configured at all for dial in) I still
> > cannot use ttyS1 in my chat script to dial-out.  Could you point me to
> > the right resource for configuring my ttyS? device for dial out?
> > 
> > > (And yes, at least the cua1/ttyS1 issue *is* in the manual).
> > >
> > > gert
> > >
> > > --
> > > USENET is *not* the non-clickable part of WWW!
> > >                                                            //www.muc.de/~gert/
> > > Gert Doering - Munich, Germany                             gert@greenie.muc.de
> > > fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de
> > 
> > thanks for your patience.  And drink a Schneider Weisse for me!
> > 
> > Dan
>