cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3733
Views
0
Helpful
10
Replies

Host cannot ping IPv6 in c7200 router

chch6597
Level 1
Level 1

Hello, I'm still a newbie in networking. I'm trying to ping IPv6 from my cloud host (running Ubuntu) to DHCP IPv6 c7200 router in GNS3, but I always got From fe80::f8ac:aaff:fe9a:a103 icmp_seq=1 Destination unreachable: Address unreachable. I ran out of my ideas what it could go wrong. Could everyone teach me and guide me?

 

This is a short topology:

Screenshot 2019-02-14 00.46.48.png

 

My cloud host IPv6 address is like the following:

Screenshot 2019-02-14 00.53.58.png

 

And my DHCP Server (R4) running IPv6:

 

Screenshot 2019-02-14 00.52.14.png

 

Screenshot 2019-02-14 00.52.56.png

10 Replies 10

Seb Rupik
VIP Alumni
VIP Alumni

Hi there,

My first thought without testing it would be you need to specify a source interface for your ping. The link-local FE80 address provides no information to the router (subnet prefix) to tell it which connected interface to source the ping from.

 

cheers,

Seb.

Thank you for your response. Here's the command I did: `ping6 FE80::C803:7FF:FE27:6%tap0` at Ubuntu host. As you can see, I have specified the tap0 is my source interface. Am I missing something else?
`

Tomhoppen
Level 1
Level 1

Hey,

 

I have 2 questions. Are you trying to ping from ubuntu host tot R4 or R5? if R5 then you would need to specifiy to R4 where R5 is this can be done by making a static route or by configuring a routing protocol. 

 

i see that in the topology R4 is directly connected with your ubuntu host. For pinging R4 you would need to put a router between ubuntu host and R4 that has a link with R4 in the same subnet. i think this is the case because you do get a DHCP ip because there is a layer 2 link between R4 and ubuntu host. If you haven't already done this please try to configure a router between R4 and host with the following aspects:

 

1. interface from new router to R4 that is in the same subnet

2. interface from new router to ubuntu host that is in the same subnet

3. new router should see a connected route to R4 if this is not the case configure on R4 an ip route to new router and configure an ip route from new router to R4

 

hope this helps let me know!

 

regards,

Tom 

Thank you for your detailed response. My goal is to ping from ubuntu to ping R4 first, then later on, I can ping R5 from Ubuntu. Right now, I have no routing protocol configured on R4 and R5, it's just IPv6 DHCP server on R4 and DHCP client on R5.

 

And this is a requirement, I cannot add a new router between R4 and Ubuntu, nor between R4 and R5. And I thought Ubuntu IPv6 address is link local, same as R4 so they can ping each other?

Harold Ritter
Spotlight
Spotlight

Did you try pinging the link local address of the Ubuntu host from the router?

If you want your Ubuntu host to get an IPv6 address through StateLess Address AutoConfiguration (SLAAC), you should change the prefix length from /65 to /64 on R4 F0/1.

 

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Thank you for the reply. It's /64, not /65, but I found out the reason.... I feel so dump... I enable the wrong interface... it should be f0/0... not f0/1... I'm sorry 

Sergey Lisitsin
VIP Alumni
VIP Alumni
chch6597,

Are you able to ping using IPv4? May be there is a lower layer issue, not related to IPv6.

Thank you for the reply. That could be other reasons later on for my other cases, but I found out the reason.... I feel so dump... I enable the wrong interface... it should be f0/0... not f0/1... I'm sorry. But thank you for the tips, I could use your tips to figure out other problems

Deepak Kumar
VIP Alumni
VIP Alumni

Hi,

As I understood the issue. Your cloud host is getting only Link-Local (Fe08) IP address and it is a no-routable IPv6 address block.

I hope if you will check your router CEF and routing table, will get the reason because this subnet (Link-local) is auto-configured with a null0 interface.

 

Regards,

Deepak Kumar

 

Regards,
Deepak Kumar,
Don't forget to vote and accept the solution if this comment will help you!

The link-local FE80 address provides no information to the router     https://audacity.onl/ https://findmyiphone.onl/ https://origin.onl/

Review Cisco Networking for a $25 gift card