Ed, you cannot ping the link local address because the computer does not automatically know which interface it should use. So, you should specify the link. Like the following:
ping6 -I eth0 e80::2e0:c5ff:febc:4aa3 That should do the trick, I hope. Cheers, Jonne. -----Original Message----- From: [EMAIL PROTECTED] on behalf of ext Ed Kapitein Sent: Fri 3/18/2005 19:46 To: Bellino, Phil; [email protected] Subject: Re: 6to4 question Hi mike, I have a working setup with an ipv6 tunnel and can connect from all my internal hosts to ipv6 hosts. But i cannot ping the link local addres of my router, and beacause it is a link local address, AFAIK you can not ping it from other hosts. [EMAIL PROTECTED]:~> ping6 fe80::2e0:c5ff:febc:4aa3 connect: Invalid argument [EMAIL PROTECTED]:~> ping6 2001:960:2:4c1::2 PING 2001:960:2:4c1::2(2001:960:2:4c1::2) 56 data bytes 64 bytes from 2001:960:2:4c1::2: icmp_seq=1 ttl=64 time=0.508 ms 64 bytes from 2001:960:2:4c1::2: icmp_seq=2 ttl=64 time=0.491 ms I believe making a picture for people to look at would make things more clear for eveyone. Can you provide us with a link to a drawing of your network? Please provide ipv4 addreses, ipv6 adresses and interface names in the drawing. If you can't host the drawing yourself, feel free to mail it to me, i will host in on my webserver somewhere and send a link to the list. Kind regards, @ On Friday 18 March 2005 15:17, Bellino, Phil wrote: > Ed, > eth0 can(and does) have the autoconfigured Native Link-Local address > fe80:xxxx.xxxx.xxxx.xxxx.xxxx.xxxx address. > Thanks. > > -----Original Message----- > From: Ed Kapitein [mailto:[EMAIL PROTECTED] > Sent: Friday, March 18, 2005 7:27 AM > To: [email protected] > Cc: [EMAIL PROTECTED] > Subject: Re: 6to4 question > > > Hi Mike, > > If you use a tunnel to connect to ipv6 land i would expect that you ping6 > tun0/sit0 or the other end of the tunnel, not your eth0 interface. > If you are using a tunnel, eth0 should only have an ipv4 address, not a > ipv6 address. > > Hope this helps. > > Kind rgards, > @ > > >Forwarding is turned on. > > > >The internal clients (1 winxp box, 1 MDK linux box) both obtain an ipv6 > >address. They can both ping6 to the router's lan interface (eth1), > >both > >neither can ping6 the outside interface of the router (eth0). From my > >experience in the ipv4 world, this would sound like a routing issue, or > >gateway issue. I can ping6 the router but can't traverse the router. > > > >Thanks Guys, will keep trying. > > > >Mike > > > >Fredrik Tolf wrote: > > --------------------------------------------------------------------- > The IPv6 Users Mailing List > Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED] > --------------------------------------------------------------------- > The IPv6 Users Mailing List > Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED] --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED] --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
