[c-nsp] ipv6 tunnels and static routes
Pierfrancesco Caci
p.caci at seabone.net
Fri Apr 1 02:19:31 EST 2005
:-> "Bernhard" == Bernhard Schmidt <berni at birkenwald.de> writes:
> On 2005-03-31, Pierfrancesco Caci <p.caci at seabone.net> wrote:
> [6PE Setup]
>> Pings and traceroutes done on the GSR where the tunnel is defined work properly:
> [...]
>> ...while from another router:
>>
>> R_7206A-MI_MM_19#ping 2001:41A8:604::1
>>
>> Type escape sequence to abort.
>> Sending 5, 100-byte ICMP Echos to 2001:41A8:604::1, timeout is 2 seconds:
>> .....
>> Success rate is 0 percent (0/5)
>>
>> R_7206A-MI_MM_19#trace 2001:41A8:604::1
>>
>> Type escape sequence to abort.
>> Tracing the route to 2001:41A8:604::1
>>
>> 1 2001:41A8:600::1E 12 msec 8 msec 12 msec
>> 2 * * *
> I have never used 6PE so I'm not really sure, but I guess it could be
> connected with the source address selection of your second cisco. Cisco
> chooses the IPv6 address of the egress interface as source address for
> your trace and ping. If the egress interface has no IPv6 address it
> might become confused and use something like mapped addresses and would
> break.
well it should use the loopback address if the egress interface
doesn't have one, or not ?
> When you enter traceroute without options it will ask you for a source
> address, try using a local address to R_7206A-MI_MM_19 there.
Now this is crazy. Why doesn't it give me the option when I write
"trace ipv6" like it does for "trace ip" ? CLI BUG!!!!
Anyway, I tried forcing the use of the loopback address and also the
address of another interface. No change, it still doesn't go through.
Thanks
Pf
--
-------------------------------------------------------------------------------
Pierfrancesco Caci | Network & System Administrator - INOC-DBA: 6762*PFC
p.caci at seabone.net | Telecom Italia Sparkle - http://etabeta.noc.seabone.net/
Linux pippo 2.4.21-pre3 #1 SMP Wed Jan 8 09:04:02 CET 2003 i686 GNU/Linux
More information about the cisco-nsp
mailing list