I had this exact message from pppd, and found that the message was a misnomer. What was happening in my case was that I had a default route already in my route table (inadvertently), and had to remove that before pppd could take over the default route.

your mileage may vary...



Date: Tue, 21 Dec 1999 22:43:14 -0500 (EST)
From: Tom Savage <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: RE: Can't get ppp to work
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit


looks like your chap-secrets or pap-secrets file is miising information in it
to log in to your ISP.


The format of the PAP file is::


<your username>        ppp0    <your password>


On 22-Dec-99 Gordon Charrick wrote:
> Okay, I've done everything I can think of to get ppp working. The modem
> is not a winmodem. I can talk to it and get it to dial with minicom.
> I've triple checked the configuration settings and everything seems
> fine, but the fu**er just refuses to do anything with an "ifup ppp0". It
> doesn't seem to even be talking to the serial port. Does anyone have an
> idea what is going on? These are the lines from the messages file.
>
>
> Dec 21 20:47:36 butch ifup-ppp: pppd started for ppp0 on /dev/ttyS1 at
> 57600
> Dec 21 20:47:36 butch pppd[1750]: The remote system (ppp0) is required
> to authenticate itself but I
> Dec 21 20:47:36 butch pppd[1750]: couldn't find any suitable secret
> (password) for it to use to do so.
> Dec 21 20:47:36 butch ifup-ppp: pppd started for ppp0 on /dev/ttyS1 at
> 57600
> Dec 21 20:47:36 butch modprobe: can't locate module char-major-108
>
>

Rod Flancher
[EMAIL PROTECTED]


"The more I see, the more I see there is to see"  - John Sebastion

Reply via email to