Re: bad modem?
From debian-user-request@lists.debian.org Sun Jan 30 21:11:49 2000
Envelope-to: rbt@rivet
Delivery-date: Sun, 30 Jan 2000 21:11:49 -0500
Delivered-To: surfree.com%rmgnt@surfree.com
X-Received: 31 Jan 2000 00:46:14 GMT
Resent-Date: 31 Jan 2000 00:45:55 -0000
Resent-Cc: recipient list not shown: ;
X-Envelope-Sender: nakor@texas.net
X-Sender: nakor@pop.texas.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.0.33 (Beta)
Date: Sun, 30 Jan 2000 18:45:45 -0600
To: debian-user@lists.debian.org
From: "Chris R. Martin" <nakor@texas.net>
Subject: bad modem?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Resent-From: debian-user@lists.debian.org
X-Mailing-List: <debian-user@lists.debian.org> archive/latest/80903
X-Loop: debian-user@lists.debian.org
Precedence: list
Resent-Sender: debian-user-request@lists.debian.org
X-UIDL: 8586
I recently got a modem for my Linux server, and it seem to have some
problems. When I first connect it seems to work okay, but after a varying
amount of time (5-15 min) I see the following log messages:
Jan 30 18:21:21 server pppd[255]: sent [LCP EchoReq id=0x1 magic=0x8e98729b]
Jan 30 18:21:23 server pppd[255]: rcvd [LCP EchoRep id=0x1 magic=0x1742385f]
That's not your modem doing that, its the ppp program.
Perhaps you have the 'persist' option in your /etc/ppp/peers/provider
file (it may be named something else) set. The code you included is
a 'ping' to keep the connection going. Read the script /usr/bin/pon
and see what the name of the option file (in the 'call' command on
the command line following /usr/sbin/pppd) is. Look in
/etc/ppp/peers/<filename>.
Reply to: