From: YourPal (dearprudence28@gmail.com)
Date: Tue Jan 22 2008 - 17:38:00 ARST
Hi Group,
I have a weird ping issue in IPv6 which I just don't understand. Please see
below:
R3#sh ipv int br
FastEthernet0/0 [up/up]
FE80::212:1FF:FEF6:C00
FEC0:CC1E:1:38:212:1FF:FEF6:C00
Serial0/0 [up/up]
FE80::212:1FF:FEF6:C00
FEC0:CC1E:1:35::3
R3 learns the following two RIP routes:
R3#sh ipv ro FEC0:CC1E:1:4:217:FFF:FE50:1D61
R FEC0:CC1E:1:4::/64 [120/3]
via FE80::21B:54FF:FEBC:5ECC, Serial0/0
R3#sh ipv ro 2001:192:10:1:217:FFF:FE50:1D60
R 2001:192:10:1::/64 [120/3]
via FE80::21B:54FF:FEBC:5ECC, Serial0/0
R3#pi FEC0:CC1E:1:4:217:FFF:FE50:1D61 so f0/0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FEC0:CC1E:1:4:217:FFF:FE50:1D61, timeout
is 2 seconds:
Packet sent with a source address of FEC0:CC1E:1:38:212:1FF:FEF6:C00
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/44/52 ms
R3#pi 2001:192:10:1:217:FFF:FE50:1D60 so f0/0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:192:10:1:217:FFF:FE50:1D60, timeout
is 2 seconds:
Packet sent with a source address of FEC0:CC1E:1:35::3
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/39/48 ms
R3 pings to the first destination IPv6 address (i.e.
FEC0:CC1E:1:4:217:FFF:FE50:1D61) sourcing from its fa0/0 interface seems
correct.
However when R3 pings the second destination IPv6 address (i.e.
2001:192:10:1:217:FFF:FE50:1D60) sourcing from its fa0/0 interface, it
appears that it uses its interface serial0/0 IPv6 address (i.e.
FEC0:CC1E:1:35::3) instead of FEC0:CC1E:1:38:212:1FF:FEF6:C00.
I have tried the extended ping ipv6 but result is the same. Can anyone
explain why?
Thank you.
BR,
Emil
This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:38:00 ARST