On Thu, 10 Dec 2009 17:37:03 -0000, <[email protected]> wrote:
On 10-Dec-2009 15:13:45 -0000, Simon Baker wrote: > Since I've upgraded one of my machines (running IPv6 natively) > I've hit a strange issue, whereby I can no long ping6 or > tracepath6 to hosts: > tachikoma!simonb:/usr/src/kernel$ ping6 hobo.kaizo.org > can't receive hop limit: Protocol not available > Similar errors occur when trying to run tracepath6 as well: > tachikoma!simonb:/usr/src/kernel$ tracepath6 hobo.kaizo.org > IPV6_HOPLIMIT: Protocol not available grem...@owl-test:~ > zcat /proc/config.gz | grep IPV6 # CONFIG_IPV6 is not set
Hiya,I already have IPv6 in my kernel, indeed it's actually all working fine ; I can create and accept IPv6 connections with no problems.
traceroute6 for example actually works fine:traceroute to k.kaizo.org (2001:470:103:68::2), 30 hops max, 40 byte packets 1 section9.kaizo.org (2001:470:944b:abcd::225) 0.298 ms 0.117 ms 0.119 ms 2 spbkaizo-1.tunnel.tserv5.lon1.ipv6.he.net (2001:470:1f08:514::1) 17.652 ms 21.689 ms 20.913 ms 3 gige-g4-6.core1.lon1.he.net (2001:470:0:67::1) 22.327 ms 21.376 ms 28.828 ms 4 10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1) 91.110 ms 90.114 ms 2001:470:0:128::1 (2001:470:0:128::1) 86.620 ms 5 10gigabitethernet1-2.core1.chi1.he.net (2001:470:0:4e::1) 136.391 ms 135.493 ms 134.498 ms
6 2001:470:1:35::2 (2001:470:1:35::2) 111.786 ms 110.791 ms 114.876 ms 7 k.kaizo.org (2001:470:103:68::2) 113.879 ms 112.886 ms 111.908 ms It's simply ping6 and tracepath6 that are broken. The attached iputils.spec and diff fix this issue. Regards, Simon. --
iputils-ss020927-owl-ipv6.diff
Description: Binary data
iputils.spec
Description: Binary data
-- To unsubscribe, e-mail [email protected] and reply to the automated confirmation request that will be sent to you.
