All of lore.kernel.org
 help / color / mirror / Atom feed
* IPCP-Nak doesn't do anything
@ 2007-12-12 21:15 ipcpblues
  2007-12-12 21:29 ` Bill Unruh
  2007-12-12 21:36 ` James Carlson
  0 siblings, 2 replies; 3+ messages in thread
From: ipcpblues @ 2007-12-12 21:15 UTC (permalink / raw)
  To: linux-ppp


Hi,

I'm trying to get two PPP devices to work together to setup a PPP
connection.  I have control over one of them - meaning I can set whatever
options I please - but I can't control the other device, it's options are
hard-wired.

I think I've almost got them working because they pass the LCP request - ack
stage and enter the IPCP stage.  In the IPCP stage, my IPCP-Req is Ack'd, so
I'm halfway there.  Their IPCP-Req is received by me with IP-addr=0.0.0.0
and I respond with IPCP-Nak IP-addr\x192.168.20.50.  All this seems correct
to me, but then the device doesn't accept my Nak and either re-sends its
original IPCP-Req or goes back to the LCP-Req stage.  

Does any have ideas on why this could happen or something I can try?

My log is below, Thanks for reading :)

# pppd file options.pppBCM nodetach
pppd options in effect:
debug           # (from options.pppBCM)
nodetach                # (from command line)
dump            # (from options.pppBCM)
noauth          # (from options.pppBCM)
/dev/ttyUSB1            # (from options.pppBCM)
9600            # (from options.pppBCM)
lock            # (from options.pppBCM)
nocrtscts               # (from options.pppBCM)
asyncmap ffffffff               # (from options.pppBCM)
192.168.30.1:192.168.30.50              # (from options.pppBCM)
nobsdcomp               # (from options.pppBCM)
nodeflate               # (from options.pppBCM)
using channel 21
Using interface ppp0
Connect: ppp0 <--> /dev/ttyUSB1
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x25 <asyncmap 0x0> <magic 0xa5a44a5a>]
sent [LCP ConfAck id=0x25 <asyncmap 0x0> <magic 0xa5a44a5a>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfReq id=0x27 <addr 0.0.0.0>]
sent [IPCP ConfNak id=0x27 <addr 192.168.30.50>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfReq id=0x28 <addr 0.0.0.0>]
sent [IPCP ConfNak id=0x28 <addr 192.168.30.50>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfReq id=0x2a <addr 0.0.0.0>]
sent [IPCP ConfNak id=0x2a <addr 192.168.30.50>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [LCP ConfReq id=0x2c <asyncmap 0x0> <magic 0xa5a44a5a>]
sent [LCP ConfReq id=0x2 <magic 0xae75be4b> <pcomp> <accomp>]
sent [LCP ConfAck id=0x2c <asyncmap 0x0> <magic 0xa5a44a5a>]
rcvd [LCP ConfAck id=0x2 <magic 0xae75be4b> <pcomp> <accomp>]
sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfAck id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfReq id=0x2d <addr 0.0.0.0>]
sent [IPCP ConfNak id=0x2d <addr 192.168.30.50>]
sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfAck id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
rcvd [IPCP ConfAck id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>] 

-- 
View this message in context: http://www.nabble.com/IPCP-Nak-doesn%27t-do-anything-tp14303969p14303969.html
Sent from the linux-ppp mailing list archive at Nabble.com.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: IPCP-Nak doesn't do anything
  2007-12-12 21:15 IPCP-Nak doesn't do anything ipcpblues
@ 2007-12-12 21:29 ` Bill Unruh
  2007-12-12 21:36 ` James Carlson
  1 sibling, 0 replies; 3+ messages in thread
From: Bill Unruh @ 2007-12-12 21:29 UTC (permalink / raw)
  To: linux-ppp

On Wed, 12 Dec 2007, ipcpblues wrote:

>
> Hi,
>
> I'm trying to get two PPP devices to work together to setup a PPP
> connection.  I have control over one of them - meaning I can set whatever
> options I please - but I can't control the other device, it's options are
> hard-wired.
>
> I think I've almost got them working because they pass the LCP request - ack
> stage and enter the IPCP stage.  In the IPCP stage, my IPCP-Req is Ack'd, so
> I'm halfway there.  Their IPCP-Req is received by me with IP-addr=0.0.0.0
> and I respond with IPCP-Nak IP-addr\x192.168.20.50.  All this seems correct
> to me, but then the device doesn't accept my Nak and either re-sends its
> original IPCP-Req or goes back to the LCP-Req stage.
>
> Does any have ideas on why this could happen or something I can try?
>
> My log is below, Thanks for reading :)
>
> # pppd file options.pppBCM nodetach
> pppd options in effect:
> debug           # (from options.pppBCM)
> nodetach                # (from command line)

Why dump?

> dump            # (from options.pppBCM)
> noauth          # (from options.pppBCM)

You do not require athentication from the other side. That is the default.

> /dev/ttyUSB1            # (from options.pppBCM)
> 9600            # (from options.pppBCM)

That is really slow

> lock            # (from options.pppBCM)
> nocrtscts               # (from options.pppBCM)

Dangerous. does your modem really have no hardware flow control?


> asyncmap ffffffff               # (from options.pppBCM)
> 192.168.30.1:192.168.30.50              # (from options.pppBCM)

These are the IP addresses you want your self and them to have.

> nobsdcomp               # (from options.pppBCM)
> nodeflate               # (from options.pppBCM)
> using channel 21
> Using interface ppp0
> Connect: ppp0 <--> /dev/ttyUSB1
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]

The above all mean that you are talking to yourself. You are sending out
and receiving the same thing (that is what the magic numbr is all about)
there is not communication with the remote side.


> rcvd [LCP ConfReq id=0x25 <asyncmap 0x0> <magic 0xa5a44a5a>]
> sent [LCP ConfAck id=0x25 <asyncmap 0x0> <magic 0xa5a44a5a>]
They send you something.
and you respond.

> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]

They agree to your address.

> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfReq id=0x27 <addr 0.0.0.0>]
> sent [IPCP ConfNak id=0x27 <addr 192.168.30.50>]
> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfReq id=0x28 <addr 0.0.0.0>]
> sent [IPCP ConfNak id=0x28 <addr 192.168.30.50>]

It looks to me like the other side is hardly every receiving your
communication. What is the thing that you are trying to connect to?


> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfReq id=0x2a <addr 0.0.0.0>]
> sent [IPCP ConfNak id=0x2a <addr 192.168.30.50>]
> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [LCP ConfReq id=0x2c <asyncmap 0x0> <magic 0xa5a44a5a>]
> sent [LCP ConfReq id=0x2 <magic 0xae75be4b> <pcomp> <accomp>]
> sent [LCP ConfAck id=0x2c <asyncmap 0x0> <magic 0xa5a44a5a>]
> rcvd [LCP ConfAck id=0x2 <magic 0xae75be4b> <pcomp> <accomp>]
> sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
> sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfReq id=0x2d <addr 0.0.0.0>]
> sent [IPCP ConfNak id=0x2d <addr 192.168.30.50>]
> sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
> sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x2 <compress VJ 0f 01> <addr 192.168.30.1>]

I think that he is not hearing you most of the time.

More information about what it is you are trying to do, and what is on the
other side of the link would be useful. (Cell phone, windows machine,
embedded computer,...

>
>

-- 
William G. Unruh   |  Canadian Institute for|     Tel: +1(604)822-3273
Physics&Astronomy  |     Advanced Research  |     Fax: +1(604)822-5324
UBC, Vancouver,BC  |   Program in Cosmology |     unruh@physics.ubc.ca
Canada V6T 1Z1     |      and Gravity       |  www.theory.physics.ubc.ca/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: IPCP-Nak doesn't do anything
  2007-12-12 21:15 IPCP-Nak doesn't do anything ipcpblues
  2007-12-12 21:29 ` Bill Unruh
@ 2007-12-12 21:36 ` James Carlson
  1 sibling, 0 replies; 3+ messages in thread
From: James Carlson @ 2007-12-12 21:36 UTC (permalink / raw)
  To: linux-ppp

ipcpblues writes:
> I think I've almost got them working because they pass the LCP request - ack
> stage and enter the IPCP stage.  In the IPCP stage, my IPCP-Req is Ack'd, so
> I'm halfway there.  Their IPCP-Req is received by me with IP-addr=0.0.0.0
> and I respond with IPCP-Nak IP-addr\x192.168.20.50.  All this seems correct
> to me, but then the device doesn't accept my Nak and either re-sends its
> original IPCP-Req or goes back to the LCP-Req stage.  

The peer is free to ignore your suggested IP address for any reason it
wants.  You cannot make it accept an address that it doesn't want.

Assuming you can't get debug logs out of the peer (in order to find
out why it doesn't like that address), I think the only thing you
could do would be to refuse to negotiate the addresses by adding
"ipcp-no-address ipcp-no-addresses".

> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> sent [LCP ConfReq id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]
> rcvd [LCP ConfAck id=0x1 <magic 0xec2490cf> <pcomp> <accomp>]

This part is pretty suspicious and likely points to communications
errors on the path ...

> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]

... as does this.  Are you sure that the underlying link works and is
relatively error-free?  Excessive frame loss could _easily_ be the
cause of the kind of problem you're seeing.  It can lead to
non-convergence.

> rcvd [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 192.168.30.1>]
> rcvd [LCP ConfReq id=0x2c <asyncmap 0x0> <magic 0xa5a44a5a>]
> sent [LCP ConfReq id=0x2 <magic 0xae75be4b> <pcomp> <accomp>]

Right here the peer gives up and starts over.  That likely indicates
that it thinks IPCP isn't converging properly, which seems fairly
likely given the very odd traffic on this link.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-12-12 21:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-12 21:15 IPCP-Nak doesn't do anything ipcpblues
2007-12-12 21:29 ` Bill Unruh
2007-12-12 21:36 ` James Carlson

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.