Skip to content
Tnelsom's profile

New problem solver

 • 

20 Messages

Sunday, November 23rd, 2014 12:00 AM

IPv6 and SMCD3G not recognising the PD address

I believe I have my Cisco router configured correctly via:

http://www.cisco.com/c/en/us/support/docs/ip/ip-version-6-ipv6/113141-DHCPv6-00.html and http://packetpushers.net/ipv6-home-prefix-delegation/ and http://networkengineering.stackexchange.com/questions/1665/configure-external-interface-for-dhcpv6-client-on-cisco-ios

 

I am getting a 2601:8:a881:9600/64 on the Router wan port and a 2601:8:a881:96FF/64 on the Router LAN port but in the External Router Delegated Prefix section it's blank.  My clients receive 2601:8:a881:96ff/64 addresses and it can ping the Router IP addresses but cant ping the modem IPs.  The router pings ipv6 sites just fine.  My firmware is 3.1.6.56.  What gives???

 

Modem Shot.jpg

 Screen Shot 2014-11-21 at 8.05.35 PM.png

Advocate

 • 

1.4K Messages

10 years ago

Hello Tnelsm and welcome,

 

Please see my comments/questions below and apparently I must be missing a great deal.  Thanks.

  IPv6 and SMCD3G not recognising the PD address

 

Not sure why you named this post "IPV6 and SMCD3G not recognising the PD address" when you mention your Cisco router?

 

‎11-23-2014 03:36 AM - edited ‎11-23-2014 03:49 AM

I believe I have my Cisco router configured correctly via:

http://www.cisco.com/c/en/us/support/docs/ip/ip-version-6-ipv6/113141-DHCPv6-00.html and http://packetpushers.net/ipv6-home-prefix-delegation/ 

 

This refers to Internode ISP not Comcast, so a little confused about this, too?

 

and http://networkengineering.stackexchange.com/questions/1665/configure-external-interface-for-dhcpv6-c...

 

I am getting a 2601::9600/64 on the wan port

I do not see any display of your WAN information and perhaps you mean LAN? Is whatever modem you are referring to actually running the new Comcast Dual-Stack IPv4 and IPv6?  If so, are your computers also correctly setup to handle IPv6 and IPV4?

and a 2601::96FF/64 on the LAN port

 

In your graphic dispiction, I am only seeing your LAN DHCP Address to be 2601:8:a881:9600::1/64 and not sure where you are getting 2601::96FF/64 from ? 

 

but in the External Router Delegated Prefix section it's blank.  My clients receive 2601::96ff/64 addresses but cant ping the modem IP.  The router pings ipv6 sites just fine.  My firmware is 3.1.6.56.  What gives???

 

Your firmware on what Comcast modem device??

 

Your graphic depiction below does not make any sense because, you are selecting "Feature Settings" and that specific display is specifically for LAN settings?  Could you clarify some of this for us? Thanks/

 

 

Modem Shot.jpg

New problem solver

 • 

20 Messages

10 years ago

VBSSP-RICH wrote:
Hello Tnelsm and welcome,

 

Please see my comments/questions below and apparently I must be missing a great deal.  Thanks.

  IPv6 and SMCD3G not recognising the PD address

 

Not sure why you named this post "IPV6 and SMCD3G not recognising the PD address" when you mention your Cisco router?  

It is the modem that is giving out a PD address that it is not routing to.

 

‎11-23-2014 03:36 AM - edited ‎11-23-2014 03:49 AM

I believe I have my Cisco router configured correctly via:

http://www.cisco.com/c/en/us/support/docs/ip/ip-version-6-ipv6/113141-DHCPv6-00.html and http://packetpushers.net/ipv6-home-prefix-delegation/ 

 

This refers to Internode ISP not Comcast, so a little confused about this, too?

So it uses FA 0/0 instead of Dialer... what is confusing?

 

and http://networkengineering.stackexchange.com/questions/1665/configure-external-interface-for-dhcpv6-c...

 

I am getting a 2001:558:600a:51:191a:7cf6:a18:c184/64 on the wan portScreen Shot 2014-11-21 at 8.05.35 PM.png

I do not see any display of your WAN information and perhaps you mean LAN? Is whatever modem you are referring to actually running the new Comcast Dual-Stack IPv4 and IPv6?  If so, are your computers also correctly setup to handle IPv6 and IPV4?

 

Wan information...  See image above.

Is the modem dual stacked?  How would I get the image in the original post if it was not.

Is the router setup to use IPv6?  See "The router pings ipv6 sites just fine." from the original post.  

Are the clients setup to use IPv6? See "My clients receive 2601:8:a881:96ff/64 addresses but cant ping the modem IP. " from the original post.

and a 2601:8:a881:96FF/64 on the Router LAN port

 

In your graphic dispiction, I am only seeing your LAN DHCP Address to be 2601:8:a881:9600::1/64 and not sure where you are getting 2601::96FF/64 from ?   

2601::96FF left out the unimportant parts of the IP address. 2601:8:a881:9600::1 is the lan address  2601:8:a881:96ff::1 is the PD address. 

 

but in the External Router Delegated Prefix section it's blank.  (This is the important part of the whole post)

 

My clients receive 2601::96ff/64 addresses but cant ping the modem IP.  The router pings ipv6 sites just fine.  My firmware is 3.1.6.56.  What gives???

 

Your firmware on what Comcast modem device??

SMCD3G (See subject) 

 

 

Your graphic depiction below does not make any sense because, you are selecting "Feature Settings" and that specific display is specifically for LAN settings?  Could you clarify some of this for us? Thanks/

What are you talking about?  Which other tab do you want to see? 

 

 

Modem Shot.jpg


 

New problem solver

 • 

20 Messages

10 years ago

The answer appears to lie in the post:  Dual-Stack on SMC D3GCCR and Cisco DPC3939B

PD addresses are not working properly at this time.

Problem solver

 • 

90 Messages

10 years ago

I am looking into the routing issue on the SMC now..

New Contributor

 • 

2 Messages

10 years ago

Tnelsom,

 

You have, of course, precisely defined and accurately described the problem here - regardless of what one of the prior responses may imply - and I am similarly configured and similarly affected by this issue.

 

The last activity in this thread is now two months ago, when there was a declaration (by what I assume to be an official Comcast representative) that the issue would be examined, and yet there is no resolution - regardless of the fact that this thread was marked as "Solved". I am certainly understanding that problems of this nature are not going to be fixed overnight, but I believe it is a resonable expectation to either have a resolution, or be updated with a status of the progress toward such resolution, after two months.

 

This thread-status has been modified now, so that future visitors will not experience the same false hope that I just did upon seeing the subject-title listed in the "New Solutions" section of the navigation-bar.

Problem solver

 • 

326 Messages

10 years ago

Other threads discuss this.  The bootfiles for all router models have been pulled for rework