RE: ip6-localhost (::1) 2990.86 ms !H -> Why ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 18 Nov 2001, NDSoftware wrote:
> > -----Original Message-----
> > From: Pekka Savola [mailto:pekkas@netcore.fi] 
> > Sent: Sunday, November 18, 2001 11:07 AM
> > To: NDSoftware
> > Cc: linux-net@vger.kernel.org
> > Subject: RE: ip6-localhost (::1) 2990.86 ms !H -> Why ?
> > 
> > 
> > On Sun, 18 Nov 2001, NDSoftware wrote:
> > > > > traceroute to 6bone.net (3ffe:b00:c18:1::10) from 
> > > > 3ffe:8271:2101:1::1,
> > > > > 30 hops max, 16 byte packets
> > > > >  1  ip6-localhost (::1)  2990.86 ms !H  2999.53 ms !H  
> > 2999.92 ms !
> > > > > 
> > > > > Routes on Woody:
> > > > > 
> > > > > Kernel IPv6 routing table
> > > > > Destination                                 Next Hop
> > > > > Flags Metric Ref    Use Iface
> > > > > ::1/128                                     ::
> > > > > U     0      0        0 lo      
> > 
> > > > > 3ffe:8271:2101:1::1/128                     ::
> > > > > U     0      8        1 lo      
> > > > > 3ffe:8271:2101:1::/64                       ::
> > > > > UA    256    594       0 eth0    
> > 
> > Please also remove these two routes above (at least the former), as 
> > pointed out in the 6bone etc lists.
> 
> route -A inet6 del 3ffe:8271:2101:1::1/128 dev lo
> SIOCDELRT: No such process
> 
> I can't remove it.
> 
> If i add a another ip to eth0 et /128 route for lo will be created :(

Hmm, it may be that I'm misremembering your network topology.

In short, locally assigned addresses should have a /128 route to loopback.  
The on-link prefix (/64) should have a /64 route to Ethernet.

Off-link prefixes should not have routes, except a default or a 2000::/3 
route to the link-local address of the gateway.  Global address of the 
gateway also works, but is deprecated and is easier to get broken.

> 
> traceroute6 fe80::2d0:70ff:fe01:811b
> connect: Invalid argument

ping6 -I eth0 fe80::2d0:70ff:fe01:811b

With link-local addresses, the interface must always be specified, in some 
way or another.

When that works, try ping6'ing the global address of your gateway.  If 
that doesn't work, most probably your gateway has wrong routes pointing 
towards your system (and return packets get lost).

Hope this helps.

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords

-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux