Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 740088 - net-misc/iputils-20200821: ping: socket: Address family not supported by protocol
Summary: net-misc/iputils-20200821: ping: socket: Address family not supported by prot...
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-02 14:51 UTC by lekto
Modified: 2020-09-02 20:08 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info,6.01 KB, text/plain)
2020-09-02 14:51 UTC, lekto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lekto 2020-09-02 14:51:21 UTC
Created attachment 657944 [details]
emerge --info

When I'm using ping I get message "ping: socket: Address family not supported by protocol". Downgrading iputils to 20190709-r1 fix this issue.


>[ebuild   R    ] net-misc/iputils-20190709-r1::gentoo  USE="arping nls ssl -SECURITY_HAZARD -caps -clockdiff -doc -filecaps -gcrypt -idn -ipv6 -libressl -nettle -rarpd -rdisc -static -tftpd -tracepath -traceroute6" 0 KiB
Comment 1 Ionen Wolkens gentoo-dev 2020-09-02 15:57:45 UTC
Hmm, tried iputils-20200821 with the exact same USE on a up-to-date ~amd64 system (uses gcc9 though) and ping works fine. Likely something else at work here.

Does `ping -4 <address>` work?
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2020-09-02 16:05:49 UTC
(In reply to lekto from comment #0)
> When I'm using ping I get message "ping: socket: Address family not
> supported by protocol".

Ping what exactly? A hostname / FQDN / IPv4 address / IPv6 address? In the case of either of the former two, what addresses do those names resolve to?
Comment 3 Ionen Wolkens gentoo-dev 2020-09-02 16:17:59 UTC
Also, do you have IPv6 disabled in the kernel? This is typically not a good idea even if you don't use it (I did notice you use -ipv6). Can cause basic checks to fail given hardly anyone anyone tests this anymore.
Comment 4 lekto 2020-09-02 16:38:09 UTC
>ping gentoo.org
>ping: socket: Address family not supported by protocol
>PING gentoo.org (89.16.167.134) 56(84) bytes of data.
>64 bytes from www.gentoo.org (89.16.167.134): icmp_seq=1 ttl=49 time=35.5 ms
>64 bytes from www.gentoo.org (89.16.167.134): icmp_seq=2 ttl=49 time=33.9 ms
>64 bytes from www.gentoo.org (89.16.167.134): icmp_seq=3 ttl=49 time=35.0 ms
>64 bytes from www.gentoo.org (89.16.167.134): icmp_seq=4 ttl=49 time=35.3 ms
>^C
>--- gentoo.org ping statistics ---
>4 packets transmitted, 4 received, 0% packet loss, time 3004ms
>rtt min/avg/max/mdev = 33.876/34.920/35.471/0.628 ms


Yes, I have disabled IPv6 in kernel, for years. If I remember correctly I had some weird problem with losing Internet or router connection when I built my Gentoo router. I read somewhere that IPv6 might cause this so I disabled it and this fix the problem. Since then I always disable IPv6, plus I don't realy see point in using IPv6 behind NAT when ISP provide only IPv4.
Comment 5 lekto 2020-09-02 16:38:57 UTC
and forgot this:
>ping -4 gentoo.org
>PING gentoo.org (89.16.167.134) 56(84) bytes of data.
>64 bytes from www.gentoo.org (89.16.167.134): icmp_seq=1 ttl=49 time=36.2 ms
>64 bytes from www.gentoo.org (89.16.167.134): icmp_seq=2 ttl=49 time=33.7 ms
>64 bytes from www.gentoo.org (89.16.167.134): icmp_seq=3 ttl=49 time=34.1 ms
>64 bytes from www.gentoo.org (89.16.167.134): icmp_seq=4 ttl=49 time=33.4 ms
>^C
>--- gentoo.org ping statistics ---
>4 packets transmitted, 4 received, 0% packet loss, time 3004ms
>rtt min/avg/max/mdev = 33.363/34.344/36.162/1.085 ms
Comment 6 Mike Gilbert gentoo-dev 2020-09-02 17:14:32 UTC
Please report the issue upstream.

https://github.com/iputils/iputils/issues
Comment 7 lekto 2020-09-02 20:08:00 UTC
Reported upstream.
https://github.com/iputils/iputils/issues/293