Pppd is getting the peer's messages and replying to them. The peer doesn't
reply to any of pppd's messages. I'd check the device file - /dev/ttyS1 -
configuration, particularly the UART type configured as compared to the
type of the UART that the modem actually uses. For example, a modem device
file configured for a 16550 UART won't work with a 16650A UART.
On Sat, 26 Jun 1999, Jeff Hebert wrote:
|Synopsis: I have been blissfully using PPP for quite some time under Red Hat
|5.1 with my current ISP. After upgrading to RH 6.0, PPP now fails to
|connect and I think the problem is in the LCP negotiation phase. (correct
|me if I'm wrong)
|
|At this point in the debugging phase I am using minicom to log into to my
|ISP manually and then I quit minicom without hanging up the modem and fire
|up pppd with:
|
|[root@localhost /root]# pppd -d -detach /dev/ttyS1 38400 &
|
|The debug info below was copied from the terminal to a text file:
|
|[root@localhost /root]# Using interface ppp0
|Connect: ppp0 <--> /dev/ttyS1
|sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x53cb3c0> <pcomp> <accomp>]
|rcvd [LCP ConfReq id=0x3 <mru 1500> <asyncmap 0x0> <magic 0x712a5766>
|<pcomp> <accomp>]
|sent [LCP ConfAck id=0x3 <mru 1500> <asyncmap 0x0> <magic 0x712a5766>
|<pcomp> <accomp>]
|rcvd [LCP ConfReq id=0x4 <mru 1500> <asyncmap 0x0> <magic 0x712a5766>
|<pcomp> <accomp>]
|sent [LCP ConfAck id=0x4 <mru 1500> <asyncmap 0x0> <magic 0x712a5766>
|<pcomp> <accomp>]
And more, all much the same.
...
|reason I get a "modem hangup" before the connection is made (timeout
The peer didn't get a response and hungup.
...
|problem???). Are there some LCP configuration options I should be setting
|in the options file? I never needed any under RH 5.1 - ppp connected
The LCP negotiations never opened, options can only make a difference when
PPP link negotiations actually take place. That didn't happen here.
---
Clifford Kite Not a guru. (tm)
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
