Bug 175471 - ping6 tells "can't receive hop limit: Protocol not available"
ping6 tells "can't receive hop limit: Protocol not available"
Product: Fedora
Classification: Fedora
Component: iputils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Radek Vokal
Mike McLean
Depends On:
Blocks: 175637
  Show dependency treegraph
Reported: 2005-12-11 06:34 EST by Robert Scheck
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-12-13 07:40:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
ipv6-hoplimit patch (1.11 KB, patch)
2005-12-13 07:46 EST, Radek Vokal
no flags Details | Diff

  None (edit)
Description Robert Scheck 2005-12-11 06:34:29 EST
Description of problem:
I can't use ping6 to ping IPv6 ressources:

# ping6 ::1
can't receive hop limit: Protocol not available

Another example:

# ping6 irc6.ipv6.uni-erlangen.de
can't receive hop limit: Protocol not available

IPv6 itself works very well on the system, look here for example:

# mtr -6 -c 5 -r ::1
HOST: localhost                  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. ::1                          0.0%     5    0.1   0.1   0.1   0.2   0.0

Version-Release number of selected component (if applicable):

How reproducible:
Everytime, try yourself.

Actual results:
ping6 isn't working as expected.

Expected results:
Working ping6 like in the past ;-)

Additional info:
Maybe this problem is related to bug #173762, which we already had at 
Comment 1 Radek Vokal 2005-12-11 14:56:06 EST
May I also have a kernel version and glibc version? It might be the same problem
as you pointed me to, but it seems to work on my rawhide machine. 
Comment 2 Robert Scheck 2005-12-11 17:56:36 EST
I've got kernel-2.6.14-1.1697_FC5 and glibc-2.3.90-18, but with glibc-2.3.90-17 
I had the same.
Comment 3 Radek Vokal 2005-12-12 03:38:00 EST
Hmm, you're right. Looks like IPV6_HOPLIMIT no longer works as setsockopt()
option. Again I wonder what happened to this option. 

Addig glibc maintainer for some hints. 

Snip of a code which doesn't work as expected

int on = 1;
if (setsockopt(fd, SOL_IPV6, IPV6_HOPLIMIT, &on, sizeof(on))) {
Comment 4 Radek Vokal 2005-12-12 06:24:59 EST
Here's src rpm with IVP6_HOPLIMIT option removed. It should work but I'm not
convinced this solution is good. 


Comment 5 Jakub Jelinek 2005-12-12 06:27:28 EST
This has nothing to do with glibc.  glibc has just a tiny setsockopt around
kernel syscall, all the work is done in the kernel.  So, if IPV6_HOPLIMIT
used to be accepted before and now is not any longer, it is kernel's decision.
Comment 6 Robert Scheck 2005-12-12 06:38:29 EST
Is it possible, that some IPv6 specific parts of glibc-kernheaders are broken? 
IIRC, there is (was?) e.g. a bug which prevents ip6tables from a working reject 
option...maybe this is related - just guessing.
Comment 7 Jakub Jelinek 2005-12-12 07:03:51 EST
Adding glibc-kernheaders maintainer.  But better would be really just
read what the kernel does and whether something hasn't changed recently.
Comment 8 David Woodhouse 2005-12-12 07:51:48 EST
More likely to be 32/64 compat in the kernel which broke. Although it works for
me with kernel-2.6.14-1.1718_FC5, iputils-20020927-30 and glibc-2.3.90-18.

I'll upgrade that machine when I get home this week and try again.
Comment 9 Radek Vokal 2005-12-13 07:40:43 EST
ok, seems like old advanced API was using IPV6_HOPLIMIT but with the latest
kernel update this was changed to IPV6_RECVHOPLIMIT. Fix is now in rawhide,

I'm afraid this will appear on RHEL with the latest kernel update. 

Comment 10 Radek Vokal 2005-12-13 07:46:56 EST
Created attachment 122176 [details]
ipv6-hoplimit patch

Note You need to log in before you can comment on or make changes to this bug.