LinuxQuestions.org - What has happened to networking?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - What has happened to networking? (https://www.linuxquestions.org/questions/slackware-14/what-has-happened-to-networking-4175701737/)

What has happened to networking?

I have updated Slackware (32 bit version) to its bleeding end, and now I have a problem with networking.
Ping three days ago always returned times around 7 ms to ping 8.8.8.8.
Now the times have greatly changed and is trashing download speeds.
Here is what I see:

ping: socket: Address family not supported by protocol
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=41.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=114 time=44.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=114 time=40.1 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=114 time=47.3 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=114 time=38.3 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=114 time=44.5 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=114 time=35.7 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=114 time=38.0 ms

--- 8.8.8.8 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7011ms
rtt min/avg/max/mdev = 35.678/41.338/47.335/3.749 ms

I never used to get the first statement about the socket error.

Seems other linux distros may have the same problem, but it really is limiting my download speeds.

It looks like it's trying to use ipv6 and then falling back to ipv4. What happens if you use ping -6?

And why do you think it has anything to do with networking in Slackware or any other distribution?

Code:

root@liet:~# ping 8.8.8.8

ping: socket: Address family not supported by protocol

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=31.1 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=39.8 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=27.8 ms

^C

--- 8.8.8.8 ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 2003ms

rtt min/avg/max/mdev = 27.782/32.904/39.824/5.077 ms

Yup, an average of 33ms, but if you dig a bit furhter:

Code:

root@liet:~# traceroute -n 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets

1  192.168.0.1  0.369 ms  0.435 ms  0.333 ms

2  172.24.79.202  29.199 ms  49.278 ms  49.274 ms

3  172.24.67.225  44.443 ms  44.300 ms  44.344 ms

4  172.24.226.217  43.205 ms  43.242 ms  43.304 ms

5  172.24.226.218  44.275 ms  44.391 ms  44.321 ms

6  80.233.113.60  44.503 ms  44.184 ms  44.055 ms

7  80.233.113.61  44.759 ms  22.900 ms  32.801 ms

8  * * *

9  8.8.8.8  31.486 ms  31.504 ms  31.019 ms

root@liet:~#

The first hop, the home-router, outside already of the Linux box, has a response time of 0.333-0.435ms, it is beyond the router where the latency increases.

Maybe Google has changed the location of the DNS servers, or maybe your broadband provider is having some issues, it can be multiple different things, but so far it doesn't look as a problem with the Linux box.

Today, all is back to normal ping times. I have no idea what could have caused the initial problem, but thankfully Slackware seems to be back to normal.

Let me believe that may not be related at all to slackware...