HELP: pppd won't talk to modem, and won't link up with ISP

HELP: pppd won't talk to modem, and won't link up with ISP

Post by Bill Peterse » Thu, 05 Dec 1996 04:00:00



I am running RedHat 4.0, which I just loaded from an archive CD.
So I am running Linux 2.0.18 and pppd 2.2.0f.

When I run the ppp-on script, I see DTR come on on the modem,
but no lights ever blink on the modem, and according to the
syslog entries, it never even responds to AT.

Q: Is there a problem with chat?

When I fire up minicom, it can talk to the modem just fine.
In fact, I tried to use it to dial into my ISP and then fire up
pppd, and pppd never connects.

I have ppp built into the kernel, not as a module.

/etc/ppp/options looks like this:
38400
modem
crtscts
defaultroute
noipdefault
lock
asyncmap 20A0000
escape FF

I execute pppd like this:

/usr/sbin/pppd /dev/ttyS0 debug lock kdebug 1

Here is what pppd logs:

Dec  4 13:19:33 viper pppd[619]: pppd 2.2.0 started by root, uid 0
Dec  4 13:19:33 viper pppd[619]: Using interface ppp0
Dec  4 13:19:33 viper pppd[619]: Connect: ppp0 <--> /dev/ttyS0
Dec  4 13:19:33 viper pppd[619]: sent [LCP ConfReq id=0x1 <mru 1500>
<asyncmap 0x20a0000> <magic 0x887dea4d> <pcomp> <accomp>]
Dec  4 13:19:57 viper last message repeated 8 times
Dec  4 13:19:57 viper pppd[619]: rcvd [LCP ConfAck id=0x1 <mru 1500>
<asyncmap 0x20a0000> <magic 0x887dea4d> <pcomp> <accomp>]
Dec  4 13:20:00 viper pppd[619]: sent [LCP ConfReq id=0x1 <mru 1500>
<asyncmap 0x20a0000> <magic 0x887dea4d> <pcomp> <accomp>]
Dec  4 13:20:00 viper pppd[619]: rcvd [LCP ConfAck id=0x1 <mru 1500>
<asyncmap 0x20a0000> <magic 0x887dea4d> <pcomp> <accomp>]
Dec  4 13:20:03 viper pppd[619]: sent [LCP ConfReq id=0x1 <mru 1500>
<asyncmap 0x20a0000> <magic 0x887dea4d> <pcomp> <accomp>]
Dec  4 13:20:30 viper last message repeated 9 times
Dec  4 13:20:33 viper pppd[619]: LCP: timeout sending Config-Requests
Dec  4 13:20:33 viper pppd[619]: Connection terminated.
Dec  4 13:20:33 viper pppd[619]: Exit.

I have tried this with an internal supra pnp 28.8 modem,
 and a USRobitics Sportster 28.8.  All of which seem to work with
Win95 to dial in to a RAS server just fine.

Any ideas on what I am doing wrong?

Cheers,
Bill Petersen

 
 
 

HELP: pppd won't talk to modem, and won't link up with ISP

Post by Kalevi Hautanie » Fri, 06 Dec 1996 04:00:00


: I am running RedHat 4.0, which I just loaded from an archive CD.
: So I am running Linux 2.0.18 and pppd 2.2.0f.

: When I run the ppp-on script, I see DTR come on on the modem,
: but no lights ever blink on the modem, and according to the
: syslog entries, it never even responds to AT.

: Q: Is there a problem with chat?

: When I fire up minicom, it can talk to the modem just fine.
: In fact, I tried to use it to dial into my ISP and then fire up
: pppd, and pppd never connects.

Next time you fire up the Minicom, write down the string Minicom sends to
the modem for initialization. Then add it to the chat -script the pppd
uses for connect, like this for example:

'/usr/sbin/chat -v -t 60 "" ATS7=45S0=0L1M1V1X3&c1E1Q0 OK atdt......'
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^    
After that you can access your modem with pppd.

--
                        Kalevi J Hautaniemi
----------------------------------------------------------------------------
Marjatankatu 12       |tel: +358-3-364-7446           |fax: +358-3-364-2476

FINLAND               |http://www.sci.fi/~khmi/       |On air:  OH3FG, KO4BC
----------------------------------------------------------------------------

 
 
 

HELP: pppd won't talk to modem, and won't link up with ISP

Post by Everard Bro » Sun, 29 Dec 1996 04:00:00


Hi all

I know it's Christmas, but...

I've just rebuilt my kernel 1.2.13 (old I know) for PPP, I've been
told to keep SLIP in for using PPP.

During the kernel initialisation.... (from syslog):

(snip)
Swansea University Computer Society NET3.019
Swansea University Computer Society TCP/IP for NET3.019
IP Protocols: IGMP, ICMP, UDP, TCP
PPP: version 0.2.7 (4 channels) NEW_TTY_DRIVERS OPTIMIZE_FLAGS
TCP compression code copyright 1989 Regents of the University of
California
PPP line discipline registered.
SLIP: version 0.8.3-NET3.019-NEWTTY (4 channels) (6 bit encapsulation
enabled)
CSLIP: code copyright 1989 Regents of the University of California
Checking 386/387 coupling... Ok, fpu using exception 16 error
reporting.
  .
(snip)
  .
ppp: ppp0 not connected to a TTY! can't go open!
(snip)

what's missing here? has SLIP occupied all of my TTYs? or what?

Thanks in advance for any help - and seasons greetings to one and all.

Everard

 
 
 

HELP: pppd won't talk to modem, and won't link up with ISP

Post by Everard Bro » Mon, 30 Dec 1996 04:00:00


Hi all

I know it's Christmas, but...

I've just rebuilt my kernel 1.2.13 (old I know) for PPP, I've been
told to keep SLIP in for using PPP.

During the kernel initialisation.... (from syslog):

(snip)
Swansea University Computer Society NET3.019
Swansea University Computer Society TCP/IP for NET3.019
IP Protocols: IGMP, ICMP, UDP, TCP
PPP: version 0.2.7 (4 channels) NEW_TTY_DRIVERS OPTIMIZE_FLAGS
TCP compression code copyright 1989 Regents of the University of
California
PPP line discipline registered.
SLIP: version 0.8.3-NET3.019-NEWTTY (4 channels) (6 bit encapsulation
enabled)
CSLIP: code copyright 1989 Regents of the University of California
Checking 386/387 coupling... Ok, fpu using exception 16 error
reporting.
  .
(snip)
  .
ppp: ppp0 not connected to a TTY! can't go open!
(snip)

what's missing here? has SLIP occupied all of my TTYs? or what?

Thanks in advance for any help - and seasons greetings to one and all.

Everard

 
 
 

HELP: pppd won't talk to modem, and won't link up with ISP

Post by Everard Bro » Fri, 10 Jan 1997 04:00:00


Hi all

I've just rebuilt my kernel 1.2.13 (old I know) for PPP, I've been
told to keep SLIP in for using PPP.

During the kernel initialisation.... (from syslog):
(snip)
Swansea University Computer Society NET3.019
Swansea University Computer Society TCP/IP for NET3.019
IP Protocols: IGMP, ICMP, UDP, TCP
PPP: version 0.2.7 (4 channels) NEW_TTY_DRIVERS OPTIMIZE_FLAGS
TCP compression code copyright 1989 Regents of the University of
California
PPP line discipline registered.
SLIP: version 0.8.3-NET3.019-NEWTTY (4 channels) (6 bit encapsulation
enabled)
CSLIP: code copyright 1989 Regents of the University of California
Checking 386/387 coupling... Ok, fpu using exception 16 error
reporting.
  .
(snip)
  .
ppp: ppp0 not connected to a TTY! can't go open!
 .
(snip)

what's missing here? has SLIP occupied all of my TTYs? or what?

Thanks in advance for any help.

Everard

 
 
 

1. Newbie, Need help, linux doesn't/won't talk to modem

I am using linux 1.2.3 and I have it set to /dev/cua1 for linux, comm2 on
Win95, but it never talks to the modem, I have tried minicom, & chat to
dial the modem, neither of which work. I know that they don't dail the
modem because the phone by the computer, same line, doesn't even have it
dialing. Please help, and thanks in advanced.

Vance Glasscock

2. crossover

3. New US Robotics modem won't dial; browser won't find web pages

4. Automounting of CDROM...

5. Help: Mandrake 9.2- my eth1 won't talk to my ADSL modem

6. strange nvidia driver behaviour

7. Please help: Linux won't talk to Modem

8. Apache for HP-UX

9. CD won't work, system won't reboot...please help

10. help needed: AWE32 PNP won't work - kernel won't compile - gurus read this!

11. PPPD talks but won't listen

12. PPPD won't load for KPPP; the FAQ hasn't helped.

13. Slackware 1.1.2 talk(1) won't talk to Suns (explain talkd)