Discussion:
ippp0 and ipv6 trouble (ipv6cp)
(too old to reply)
Zafer Aydogan
2007-09-25 19:43:40 UTC
Permalink
hello list,

I'm having trouble to establish an isdn connection.
Everything seem to work but somehow ippp0 tries to establish a ppp
connection via ipv6. This attempt (ipv6cp) is rejected by the peer.
After that, the ipcp pap authentication succeeds and I get an IP
(ipv4) but before the connection is established the connection is
closed. During dialing my console prints: "ipv6cp illegal up in state
req-sent" all the time.

Here is the debug log from ifconfig.

Sep 25 21:32:17 pembe /netbsd: ippp0: lcp open(initial)
Sep 25 21:32:17 pembe /netbsd: ippp0: phase establish
Sep 25 21:32:17 pembe isdnd[126]: CHD 00146 world rate 0 sec/unit (conf)
Sep 25 21:32:17 pembe isdnd[126]: CHD 00146 world dialing out from xxx to yyy
Sep 25 21:32:17 pembe isdnd[126]: CHD 00146 world outgoing call
proceeding (ctl 0, ch 0)
Sep 25 21:32:18 pembe /netbsd: ippp0: Up event
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp up(starting)
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp output <conf-req id=0x92
len=10 05-06-ab-cb-b5-35>
Sep 25 21:32:18 pembe isdnd[126]: CHD 00146 world outgoing call active
(ctl 0, ch 0, ippp0)
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp input(req-sent): <conf-req
id=0x22 len=27 03-04-c0-23-05-06-28-eb-b8-56-11-04-05-f4
-13-09-01-64-69-61-6c-69-6e>
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp parse opts: auth-proto magic
0x11 [rej] 0x13 [rej] send conf-rej
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp output <conf-rej id=0x22
len=17 11-04-05-f4-13-09-01-64-69-61-6c-69-6e>
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp input(req-sent): <conf-ack
id=0x92 len=10 05-06-ab-cb-b5-35>
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp input(ack-rcvd): <conf-req
id=0x23 len=14 03-04-c0-23-05-06-28-eb-b8-56>
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp parse opts: auth-proto magic
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp parse opt values:
auth-proto magic 0x28ebb856 send conf-ack
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp output <conf-ack id=0x23
len=14 03-04-c0-23-05-06-28-eb-b8-56>
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp tlu
Sep 25 21:32:18 pembe /netbsd: ippp0: phase authenticate
Sep 25 21:32:18 pembe /netbsd: ippp0: pap output <req id=0x92 len=23
09-66-6c-61-74-32-73-75-72-66-08-69-6e-74-65-72-6e-65-74
Sep 25 21:32:18 pembe /netbsd: ippp0: ipv6cp up(initial)
Sep 25 21:32:18 pembe /netbsd: ippp0: pap success
Sep 25 21:32:18 pembe /netbsd: ippp0: phase network
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp open(initial)
Sep 25 21:32:18 pembe /netbsd: ippp0: ipv6cp open(closed)
Sep 25 21:32:18 pembe /netbsd: ippp0: ipv6cp output <conf-req id=0x23
len=14 01-0a-02-30-05-ff-fe-45-33-6a>
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp up(starting)
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp output <conf-req id=0x23
len=10 03-06-00-00-00-00>
Sep 25 21:32:18 pembe /netbsd: ippp0: ipv6cp up(req-sent)
Sep 25 21:32:18 pembe /netbsd: ippp0: ipv6cp illegal up in state req-sent
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp input(req-sent): <conf-req
id=0x1 len=10 03-06-53-f2-20-fc>
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp parse opts: address
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp parse opt values: address
0.0.0.1 [ack] send conf-ack
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp output <conf-ack id=0x1
len=10 03-06-53-f2-20-fc>
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp input(opened): <proto-rej
id=0x1 len=20 80-57-01-23-00-0e-01-0a-02-30-05-ff-fe-45-3
3-6a>
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp: RXJ+ (proto-rej) for proto
0x8057 (ipv6cp/req-sent)
Sep 25 21:32:18 pembe /netbsd: ippp0: ipv6cp close(req-sent)
Sep 25 21:32:18 pembe /netbsd: ippp0: ipv6cp output <term-req id=0x24 len=4>
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp input(ack-sent): <conf-nak
id=0x23 len=10 03-06-53-f2-3c-26>
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp nak opts: address [wantaddr
83.242.60.38] [agree]
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp output <conf-req id=0x24
len=10 03-06-53-f2-3c-26>
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp input(opened): <proto-rej
id=0x2 len=10 80-57-05-24-00-04>
Sep 25 21:32:18 pembe /netbsd: ippp0: lcp: RXJ+ (proto-rej) for proto
0x8057 (ipv6cp/closing)
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp input(ack-sent): <conf-ack
id=0x24 len=10 03-06-53-f2-3c-26>
Sep 25 21:32:18 pembe /netbsd: ippp0: ipcp tlu
Sep 25 21:32:19 pembe /netbsd: ippp0: lcp down(opened)
Sep 25 21:32:19 pembe /netbsd: ippp0: phase terminate
Sep 25 21:32:19 pembe /netbsd: ippp0: ipcp down(opened)
Sep 25 21:32:19 pembe /netbsd: ippp0: ipcp close(starting)
Sep 25 21:32:19 pembe /netbsd: ippp0: ipv6cp down(closing)
Sep 25 21:32:19 pembe /netbsd: ippp0: ipv6cp close(initial)
Sep 25 21:32:19 pembe /netbsd: ippp0: Down event (carrier loss)
Sep 25 21:32:19 pembe /netbsd: ippp0: lcp close(starting)
Sep 25 21:32:19 pembe /netbsd: ippp0: phase dead

Any help is appreciated.

Zafer.

ps: this is current 4.99.31 from today morning.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Ignatios Souvatzis
2007-10-02 11:52:55 UTC
Permalink
Post by Zafer Aydogan
hello list,
I'm having trouble to establish an isdn connection.
Everything seem to work but somehow ippp0 tries to establish a ppp
connection via ipv6. This attempt (ipv6cp) is rejected by the peer.
After that, the ipcp pap authentication succeeds and I get an IP
(ipv4) but before the connection is established the connection is
closed. During dialing my console prints: "ipv6cp illegal up in state
req-sent" all the time.
Hm - sounds like a broken peer to me; at least the kernel sync ppp
engines of NetBSD used to work with the legacy IP (IPv4) only peers
I've used in the past; only logging a warning. (Unless some other
parameter of pap and ipv4 negotiation is wrong on your side, too).

Our async PPP implementation has a workaround for broken peers: you can
disable ipv6 with "pppd -ipv6", but I didn't find such an option for
ipppctl.

Regards,
-is

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Zafer Aydogan
2007-10-02 12:32:18 UTC
Permalink
Post by Ignatios Souvatzis
Post by Zafer Aydogan
hello list,
I'm having trouble to establish an isdn connection.
Everything seem to work but somehow ippp0 tries to establish a ppp
connection via ipv6. This attempt (ipv6cp) is rejected by the peer.
After that, the ipcp pap authentication succeeds and I get an IP
(ipv4) but before the connection is established the connection is
closed. During dialing my console prints: "ipv6cp illegal up in state
req-sent" all the time.
Hm - sounds like a broken peer to me; at least the kernel sync ppp
engines of NetBSD used to work with the legacy IP (IPv4) only peers
I've used in the past; only logging a warning. (Unless some other
parameter of pap and ipv4 negotiation is wrong on your side, too).
Our async PPP implementation has a workaround for broken peers: you can
disable ipv6 with "pppd -ipv6", but I didn't find such an option for
ipppctl.
I've build a kernel without INET6, but the problem remains.
The connection is always closed in the end.
Is this possible because I set link1 for ippp0 ?

inet 0.0.0.0 0.0.0.1 link1 down

which should bring up the interface and the connection on demand.


This is the last part of the log with the ipv4 only kernel:

Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp parse opts: address
Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp parse opt values: address
0.0.0.1 [ack] send conf-ack
Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp output <conf-ack id=0x1
len=10 03-06-53-f2-20-fc>
Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp input(ack-sent): <conf-nak
id=0x15 len=10 03-06-53-f2-3e-03>
Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp nak opts: address [wantaddr
83.242.62.3] [agree]
Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp output <conf-req id=0x16
len=10 03-06-53-f2-3e-03>
Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp input(ack-sent): <conf-ack
id=0x16 len=10 03-06-53-f2-3e-03>
Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp tlu
Sep 30 13:38:57 pembe /netbsd: ippp0: lcp down(opened)
Sep 30 13:38:57 pembe /netbsd: ippp0: phase terminate
Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp down(opened)
Sep 30 13:38:57 pembe /netbsd: ippp0: ipcp close(starting)
Sep 30 13:38:57 pembe /netbsd: ippp0: Down event (carrier loss)
Sep 30 13:38:57 pembe /netbsd: ippp0: lcp close(starting)
Sep 30 13:38:57 pembe /netbsd: ippp0: phase dead

I also tried another provider to connect with the same result.

Is there anything else I can do ?

Cheers, Zafer.
Post by Ignatios Souvatzis
Regards,
-is
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Ignatios Souvatzis
2007-10-02 12:55:20 UTC
Permalink
Post by Zafer Aydogan
inet 0.0.0.0 0.0.0.1 link1 down
which should bring up the interface and the connection on demand.
ahem.

remove the down here. Add "up" instead. Unless you tried that already.

The "lcp down" even near the end of your log might be created by that
"down" keyword.

-is

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Ignatios Souvatzis
2007-10-02 12:47:30 UTC
Permalink
Hi,
Post by Zafer Aydogan
I've build a kernel without INET6, but the problem remains.
Ok, then its no problem with ipv6cp.
Post by Zafer Aydogan
The connection is always closed in the end.
Is this possible because I set link1 for ippp0 ?
inet 0.0.0.0 0.0.0.1 link1 down
which should bring up the interface and the connection on demand.
Ah - you should first try with -link1 , to find out about this (link1 is
default, I think).

Regards,
-is

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Zafer Aydogan
2007-10-15 13:01:36 UTC
Permalink
Well, big thanks to Martin Husemann who fixed it.

Problem was neither ipv6 nor up/down issues. (The documentation is
correct.), but a timecounter issue (difference between time_second and
time_uptime).

See also:

http://cvsweb.de.netbsd.org/cgi-bin/cvsweb.cgi/src/sys/netisdn/i4b_global.h.diff?r1=1.7;r2=1.8;f=h

Cheers, Zafer.
Post by Ignatios Souvatzis
Post by Zafer Aydogan
inet 0.0.0.0 0.0.0.1 link1 down
which should bring up the interface and the connection on demand.
ahem.
remove the down here. Add "up" instead. Unless you tried that already.
The "lcp down" even near the end of your log might be created by that
"down" keyword.
-is
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...