02-21-2011 09:41 AM - edited 03-04-2019 11:30 AM
My ISP is *starting* to roll out native-v6, quiet-like, and I'm trying to get it running in the ADSL-connected home-lab.
However, for some reason, PPP link setup fails for v6; v4 is fine, as always.
The argument which seems to be sent from IPV6CP as the link-ID seems like it might be overlong from some examples I've seen elsewhere. I have seen 48-bit-ish examples, and this one is clearly longer. I've not seen any config extracts that suggest I may have control over this, though. At least not directly.
I'd love to know where to look further, or if this is a known bug, but GOOG searches aren't giving me anything seeming relevant. It's *possible* that the ISP needs to tweak something on the LNS side, but says he has another customer with a working setup (not necessarily on the c8xx ISR series hardware, though). I had the same problems on c880data-universalk9-mz.124-22.YB8.bin image as well, and moved to the 15.1(3)T in hopes of better functionality.
Apologies in advance if I dropped this into the wrong area.
-jml
Relevant config extracts:
boot system flash c880data-universalk9-mz.151-3.T.bin
! ...
ipv6 unicast-routing
ipv6 cef
!...
!
interface ATM0
no ip address
no atm ilmi-keepalive
pvc 0/32
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
! ...
!
interface Dialer1
description PPPoA Dialer to ipHouse
ip address negotiated
ip mtu 1492
ip flow ingress
encapsulation ppp
dialer pool 1
dialer-group 1
ipv6 address 2001:4980:1000:1E00::2/64
ipv6 address autoconfig
ipv6 enable
ppp authentication chap pap callin
ppp pap sent-username user@isp [snip]
!
ip forward-protocol nd
!...
dialer-list 1 protocol ipv6 permit
ipv6 route ::/0 Dialer1
Which all seems well and good, but something seems to go wrong in the PPPoA negotiation. "debug ppp nego" gives me:
Feb 21 12:29:24: Vi2 IPV6CP: I CONFREQ [UNKNOWN] id 1 len 14
Feb 21 12:29:24: Vi2 IPV6CP: (0x010A02044EFFFE112400)
Feb 21 12:29:24: Vi2 LCP: O PROTREJ [Open] id 3 len 20 protocol IPV6CP (0x01010010010A02044EFFFE112400)"
The log with more context:
Feb 21 06:29:24 gw.lioness.net 1038: Feb 21 12:29:24: Vi2 LCP: State is Open
Feb 21 06:29:24 gw.lioness.net 1039: Feb 21 12:29:24: Vi2 PAP: I AUTH-ACK id 1 len 5
Feb 21 06:29:24 gw.lioness.net 1040: Feb 21 12:29:24: Vi2 PPP: Phase is FORWARDING, Attempting Forward
Feb 21 06:29:24 gw.lioness.net 1041: Feb 21 12:29:24: Vi2 PPP: Phase is ESTABLISHING, Finish LCP
Feb 21 06:29:24 gw.lioness.net 1042: Feb 21 12:29:24: Vi2 PPP: Phase is UP
Feb 21 06:29:24 gw.lioness.net 1043: Feb 21 12:29:24: Vi2 IPCP: Protocol configured, start CP. state[Initial]
Feb 21 06:29:24 gw.lioness.net 1044: Feb 21 12:29:24: Vi2 IPCP: Event[OPEN] State[Initial to Starting]
Feb 21 06:29:24 gw.lioness.net 1045: Feb 21 12:29:24: Vi2 IPCP: O CONFREQ [Starting] id 1 len 10
Feb 21 06:29:24 gw.lioness.net 1046: Feb 21 12:29:24: Vi2 IPCP: Address 0.0.0.0 (0x030600000000)
Feb 21 06:29:24 gw.lioness.net 1047: Feb 21 12:29:24: Vi2 IPCP: Event[UP] State[Starting to REQsent]
Feb 21 06:29:24 gw.lioness.net 1048: Feb 21 12:29:24: Vi2 CDPCP: Protocol configured, start CP. state[Initial]
Feb 21 06:29:24 gw.lioness.net 1049: Feb 21 12:29:24: Vi2 CDPCP: Event[OPEN] State[Initial to Starting]
Feb 21 06:29:24 gw.lioness.net 1050: Feb 21 12:29:24: Vi2 CDPCP: O CONFREQ [Starting] id 1 len 4
Feb 21 06:29:24 gw.lioness.net 1051: Feb 21 12:29:24: Vi2 CDPCP: Event[UP] State[Starting to REQsent]
Feb 21 06:29:24 gw.lioness.net 1052: Feb 21 12:29:24: Vi2 IPCP: I CONFREQ [REQsent] id 1 len 16
Feb 21 06:29:24 gw.lioness.net 1053: Feb 21 12:29:24: Vi2 IPCP: CompressType VJ 15 slots (0x0206002D0F00)
Feb 21 06:29:24 gw.lioness.net 1054: Feb 21 12:29:24: Vi2 IPCP: Address 216.250.189.51 (0x0306D8FABD33)
Feb 21 06:29:24 gw.lioness.net 1055: Feb 21 12:29:24: Vi2 IPCP: O CONFREJ [REQsent] id 1 len 10
Feb 21 06:29:24 gw.lioness.net 1056: Feb 21 12:29:24: Vi2 IPCP: CompressType VJ 15 slots (0x0206002D0F00)
Feb 21 06:29:24 gw.lioness.net 1057: Feb 21 12:29:24: Vi2 IPCP: Event[Receive ConfReq-] State[REQsent to REQsent]
Feb 21 06:29:24 gw.lioness.net 1058: Feb 21 12:29:24: Vi2 IPV6CP: I CONFREQ [UNKNOWN] id 1 len 14
Feb 21 06:29:24 gw.lioness.net 1059: Feb 21 12:29:24: Vi2 IPV6CP: (0x010A02044EFFFE112400)
Feb 21 06:29:24 gw.lioness.net 1060: Feb 21 12:29:24: Vi2 LCP: O PROTREJ [Open] id 3 len 20 protocol IPV6CP (0x01010010010A02044EFFFE112400)
Feb 21 06:29:24 gw.lioness.net 1061: Feb 21 12:29:24: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Feb 21 06:29:24 gw.lioness.net 1062: Feb 21 12:29:24: Vi2 IPCP: I CONFNAK [REQsent] id 1 len 10
Feb 21 06:29:24 gw.lioness.net 1063: Feb 21 12:29:24: Vi2 IPCP: Address 216.250.178.166 (0x0306D8FAB2A6)
Feb 21 06:29:24 gw.lioness.net 1064: Feb 21 12:29:24: Vi2 IPCP: O CONFREQ [REQsent] id 2 len 10
Feb 21 06:29:24 gw.lioness.net 1065: Feb 21 12:29:24: Vi2 IPCP: Address 216.250.178.166 (0x0306D8FAB2A6)
Feb 21 06:29:24 gw.lioness.net 1066: Feb 21 12:29:24: Vi2 IPCP: Event[Receive ConfNak/Rej] State[REQsent to REQsent]
Feb 21 06:29:24 gw.lioness.net 1067: Feb 21 12:29:24: Vi2 LCP: I PROTREJ [Open] id 3 len 10 protocol CDPCP (0x01010004)
Feb 21 06:29:24 gw.lioness.net 1068: Feb 21 12:29:24: Vi2 CDPCP: Event[Receive CodeRej-] State[REQsent to Stopped]
Feb 21 06:29:24 gw.lioness.net 1069: Feb 21 12:29:24: Vi2 IPCP: I CONFREQ [REQsent] id 2 len 10
Feb 21 06:29:24 gw.lioness.net 1070: Feb 21 12:29:24: Vi2 IPCP: Address 216.250.189.51 (0x0306D8FABD33)
Feb 21 06:29:25 gw.lioness.net 1071: Feb 21 12:29:24: Vi2 IPCP: O CONFACK [REQsent] id 2 len 10
Feb 21 06:29:25 gw.lioness.net 1072: Feb 21 12:29:24: Vi2 IPCP: Address 216.250.189.51 (0x0306D8FABD33)
Feb 21 06:29:25 gw.lioness.net 1073: Feb 21 12:29:24: Vi2 IPCP: Event[Receive ConfReq+] State[REQsent to ACKsent]
Feb 21 06:29:25 gw.lioness.net 1074: Feb 21 12:29:24: Vi2 IPCP: I CONFACK [ACKsent] id 2 len 10
Feb 21 06:29:25 gw.lioness.net 1075: Feb 21 12:29:24: Vi2 IPCP: Address 216.250.178.166 (0x0306D8FAB2A6)
Feb 21 06:29:25 gw.lioness.net 1076: Feb 21 12:29:24: Vi2 IPCP: Event[Receive ConfAck] State[ACKsent to Open]
Feb 21 06:29:25 gw.lioness.net 1077: Feb 21 12:29:24: Vi2 IPCP: State is Open
Feb 21 06:29:25 gw.lioness.net 1078: Feb 21 12:29:24: Di1 IPCP: Install negotiated IP interface address 216.250.178.166
Feb 21 06:29:25 gw.lioness.net 1079: Feb 21 12:29:24: Di1 Added to neighbor route AVL tree: topoid 0, address 216.250.189.51
Feb 21 06:29:25 gw.lioness.net 1080: Feb 21 12:29:24: Di1 IPCP: Install route to 216.250.189.51
"sho ipv6 int" gives:
Dialer1 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::223:EBFF:FE02:21F0
No Virtual link-local address(es):
Description: PPPoA Dialer to ipHouse
Stateless address autoconfig enabled
Global unicast address(es):
2001:4980:1000:1E00::2, subnet is 2001:4980:1000:1E00::/64
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:2
FF02::1:FF02:21F0
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
Hosts use stateless autoconfig for addresses.
"sho int" gives:
ATM0 is up, line protocol is up
Hardware is MPC ATMSAR (with Alcatel ADSL Module), address is 0023.eb02.21f0 (bia 0023.eb02.21f0)
MTU 4470 bytes, sub MTU 4470, BW 896 Kbit/sec, DLY 410 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Keepalive not supported
Encapsulation(s): AAL5
20 maximum active VCs, 1024 VCs per VP, 1 current VCCs
VC Auto Creation Disabled.
VC idle disconnect time: 300 seconds
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 5
Queueing strategy: Per VC Queueing
5 minute input rate 2000 bits/sec, 2 packets/sec
5 minute output rate 2000 bits/sec, 2 packets/sec
382996 packets input, 333092514 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 782 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
370638 packets output, 47916612 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
[ ... ]
Dialer1 is up, line protocol is up (spoofing)
Hardware is Unknown
Description: PPPoA Dialer to ipHouse
Internet address is 216.250.178.166/32
MTU 1500 bytes, BW 56 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 9/255
Encapsulation PPP, LCP Closed, loopback not set
Keepalive set (10 sec)
DTR is pulsed for 1 seconds on reset
Interface is bound to Vi2
Last input never, output never, output hang never
Last clearing of "show interface" counters 15:09:47
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 164
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/16 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 42 kilobits/sec
5 minute input rate 2000 bits/sec, 2 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
372302 packets input, 331431241 bytes
370599 packets output, 46433584 bytes
Bound to:
Virtual-Access2 is up, line protocol is up
Hardware is Virtual Access interface
MTU 1500 bytes, BW 896 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Open
Stopped: CDPCP
Open: IPCP
PPPoATM vaccess, cloned from Dialer1
Vaccess status 0x44
Bound to ATM0 VCD: 1, VPI: 0, VCI: 32, loopback not set
Keepalive set (10 sec)
DTR is pulsed for 5 seconds on reset
Interface is bound to Di1 (Encapsulation PPP)
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters 15:08:40
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 2000 bits/sec, 2 packets/sec
5 minute output rate 2000 bits/sec, 2 packets/sec
382996 packets input, 331568906 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
370645 packets output, 46434358 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
[ ... ]
Solved! Go to Solution.
02-21-2011 01:35 PM
Jim apologies for the trouble, this is a known issue in 12.4T and 15.x releases, the problem being that the dialer sw doesn't pick up
the ipv6 configuration correctly, hence PROTOREJ the ipv6cp.
Your config is correct and I just verified this with other releases to be working fine.
You may want to reach out to TAC so they can disclose the DDTs number with you and advise of the release to use that has this
fix integrated.
thanks
xander ccie isp/voice
sr Tech Lead ASR9000
02-21-2011 02:00 PM
12.4(22)YB is a derivate from 12.4(22)T which is indeed affected by this also, hence you see the problem there too.
Thanks for the SR number, I reached out to the engineer handling your case with the ddts info.
regards
xander
02-21-2011 01:35 PM
Jim apologies for the trouble, this is a known issue in 12.4T and 15.x releases, the problem being that the dialer sw doesn't pick up
the ipv6 configuration correctly, hence PROTOREJ the ipv6cp.
Your config is correct and I just verified this with other releases to be working fine.
You may want to reach out to TAC so they can disclose the DDTs number with you and advise of the release to use that has this
fix integrated.
thanks
xander ccie isp/voice
sr Tech Lead ASR9000
02-21-2011 01:52 PM
I've got a TAC case open (616911841), but I started this problem with 12.4(22)YB8 so that should go on the busted list as well.
Thanks.
-jml
02-21-2011 02:00 PM
12.4(22)YB is a derivate from 12.4(22)T which is indeed affected by this also, hence you see the problem there too.
Thanks for the SR number, I reached out to the engineer handling your case with the ddts info.
regards
xander
02-22-2011 03:49 AM
Near as I can tell there are no generally-available fixes at this time, at least for the 880 ISR routers, though there appear to be a plethora of releases that have the fix.
In a post-v4 exhaustion world, one might quibble with this bug being tagged as Severity 3 - "minor features do not work at all"
For me, with my ISP doing a completely standard dynamic configuration (on Cisco gear) for their customers, and Cisco manufactured business class CPE not being able to make native v6 work is arguably not so minor. Or will be pretty soon.
-jml
08-02-2011 01:01 PM
I have the same problem with the Cisco 887 running the latest c880data-universalk9-mz.151-4.M1.bin image running at license level advsecurity.
Changing license level to advipservices resolves the problem ans allows the C887 to negotiate an IPv6 address on the PPPoA Dialer interface.
This is the config:
!
! No configuration change since last restart
version 15.1
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Router
!
boot-start-marker
boot system flash c880data-universalk9-mz.151-4.M1.bin
boot-end-marker
!
!
!
no aaa new-model
!
memory-size iomem 10
crypto pki token default removal timeout 0
!
!
ip source-route
!
!
!
!
!
ip cef
ipv6 unicast-routing
ipv6 cef
!
!
multilink bundle-name authenticated
license udi pid CISCO887-K9 sn FCZ1514C4A9
license boot module c880-data level advipservices
!
interface ATM0
no ip address
no atm ilmi-keepalive
!
interface ATM0.1 point-to-point
ip flow ingress
pvc 0/35
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
!
interface FastEthernet0
no ip address
!
interface FastEthernet1
no ip address
!
interface FastEthernet2
no ip address
!
interface FastEthernet3
no ip address
!
interface Vlan1
ip address dhcp
!
interface Dialer0
ip address negotiated
ip access-group ACL-INTERNET in
ip nat outside
ip virtual-reassembly in
encapsulation ppp
ip tcp header-compression iphc-format
dialer pool 1
dialer-group 1
ipv6 address autoconfig default
ipv6 enable
ppp authentication pap callin
ppp pap sent-username zzz password xxx
ppp ipcp dns request
no cdp enable
ip rtp header-compression iphc-format
!
ip forward-protocol nd
no ip http server
no ip http secure-server
!
!
To show it works, i'll include the output of the sh ipv6 int dialer0 command:
Router#sh ipv6 int dialer0
Dialer0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::4255:39FF:FE9B:25F6
No Virtual link-local address(es):
Stateless address autoconfig enabled
Global unicast address(es):
2A03:BE00:4:0:4255:39FF:FE9B:25F6, subnet is 2A03:BE00:4::/64 [EUI/CAL/PRE]
valid lifetime 2591753 preferred lifetime 604553
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF9B:25F6
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses.
R Router#sh ipv6 int dialer0
Dialer0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::4255:39FF:FE9B:25F6
No Virtual link-local address(es):
Stateless address autoconfig enabled
Global unicast address(es):
2A03:BE00:4:0:4255:39FF:FE9B:25F6, subnet is 2A03:BE00:4::/64 [EUI/CAL/PRE]
valid lifetime 2591753 preferred lifetime 604553
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF9B:25F6
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses.
Best regards, Simon Poels
08-02-2011 01:11 PM
Simon, that is correct, you need the "adv" type images for this platform in order to have ipv6cp support. I apologize if that is not clear from the documentation. If it is not documented well, perhaps you want to file a submit feedback option on the documentation referecing ipv6cp that adv-like images are required as an additional note/disclaimer.
the universal image does not have the right subsystem and the right hooks between ppp and ipv6 available.
thanks
xander
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide