[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PAP & PPP, take 3



On Mon, 17 Nov 1997, Rick Hawkins wrote:

> I've bumped the debug level, as suggested. It gives me all kinds of
> messages, which make absolutely no sense to me :(  I've clipped them, in
> pieces (still haven't figured out how to increase plog's length).
> 
> > Nov 17 11:52:10 nest pppd[995]: rcvd [LCP ConfAck id=0x1 <mru 1500> <asyncmap 0
> > x0> <magic 0x7a22c6e8> <pcomp> <accomp>]
ConfAck = Configuration Acknoledged; The options mentioned have been
negotiated.

> > Nov 17 11:52:10 nest pppd[995]: sent [IPCP ConfReq id=0x1 <addr 192.0.2.1> <com
> > press VJ 0f 01>]
ConfReq = Configuration Request
Now your box wants to tell the ISP that it's IP-address is 192.0.2.1 (it
shouldn't do this. I assume you get a IP dynamicaly by your ISP)

> > Nov 17 11:52:32 nest last message repeated 7 times

It tries 7 times, your ISP doesn't answer.

> > Nov 17 11:52:35 nest pppd[995]: sent [LCP EchoReq id=0x0 7a 22 c6 e8]
> > Nov 17 11:52:35 nest pppd[995]: sent [IPCP ConfReq id=0x1 <addr 192.0.2.1> <com
> > press VJ 0f 01>]
Your box still want's to establish its view of the IP-address. I don't
know what echo is for.

Further decrypting is left as a exercise to the reader.

Sorry, I don't have your prior posting any more, so here are my guesses
about your setup:

You dial into your ISP, which assigns dynamic IPs to the customers dialing
in. Authentification via PAP.

If this is true, then you should try the following as /etc/ppp/options:

# /etc/ppp/options
#
asyncmap 0
crtscts
lock
modem
netmask 255.255.255.0
noipdefault
debug
proxyarp

# the following two shouldn't be necessary, but as I don't know what your
# other setup-scripts look like...
ipcp-accept-local
ipcp-accept-remote

# If this option is given, pppd will send an LCP echo-request frame to
# the peer every n seconds. Under Linux, the echo-request is sent when
# no packets have been received from the peer for n seconds. Normally
# the peer should respond to the echo-request by sending an echo-reply.
# This option can be used with the lcp-echo-failure option to detect
# that the peer is no longer connected.
lcp-echo-interval 30
                         
# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection.  Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 4

user my_username_at_the_isp

With /etc/ppp-secrets:

user my_username_at_the_isp	*	my_password_at_the_isp

If you want a easy to setup X frontend to pppd, mail me and I can upload
xisp-2.3-1.1.deb somewhere. 
If you want to take a look at it: http://users.hol.gr/~dbouras/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: