| View previous topic :: View next topic |
| Author |
Message |
paulbiz
Guru
Joined: 01 Feb 2004
Posts: 508
Location: St. Louis, Missouri, USA
|
 Posted: Fri Jul 10, 2020 5:33 pm Post subject: IPv6 Suddenly stopped working in my server VM [SOLVED] |
 |
|
Update: SOLVED, it seems kernel related. Updated kernel to latest and now it works again.
Hi, I have a virtual server and have been running Gentoo for a long time. Suddenly, after doing a large round of emerge @world, my IPv6 has become unresponsive to incoming and outgoing communications. IPv4 still works.
I have rebooted the server but it's still unresponsive to IPv6 connections. I have disabled ip6tables but it made no difference.
I didn't change any network settings in years. So it's weird... I am not a networking wizard so maybe somebody can point me in the right direction of what else I can look at? Or do I have it configured in a wrong way?
For now I have removed my AAAA records from DNS to avoid failing incoming connections.
(redacted addresses below)
It looks weird but Hetzner uses fe80::1 as the default gateway on these virtual network adapters. I am able to ping fe80::1 successfully.
I also sent a support request to the host to see if they have any network issues.
/etc/conf.d/net
| Code: |
config_eth0="my:ip:v6:addr:ess/64"
routes_eth0="default via fe80::1"
dhcp_eth0="nodns"
dns_domain_lo="mydomain.us"
dns_search_lo="mydomain.us"
dns_servers_lo="127.0.0.1 ::1"
|
| Code: |
# ip -6 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 my:ip:v6:addr:ess/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::b1e:d809:c287:baa6/64 scope link
valid_lft forever preferred_lft forever
|
| Code: |
# ip -6 r
my:ip:v6::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
ff00::/8 dev eth0 metric 256 pref medium
default via fe80::1 dev eth0 metric 2 pref medium
|
| Code: |
# ping6 fe80::1
PING fe80::1(fe80::1) 56 data bytes
64 bytes from fe80::1%eth0: icmp_seq=1 ttl=64 time=0.190 ms
64 bytes from fe80::1%eth0: icmp_seq=2 ttl=64 time=0.219 ms
64 bytes from fe80::1%eth0: icmp_seq=3 ttl=64 time=0.257 ms
64 bytes from fe80::1%eth0: icmp_seq=4 ttl=64 time=0.241 ms
64 bytes from fe80::1%eth0: icmp_seq=5 ttl=64 time=0.271 ms
64 bytes from fe80::1%eth0: icmp_seq=6 ttl=64 time=0.317 ms
^C
--- fe80::1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5156ms
rtt min/avg/max/mdev = 0.190/0.249/0.317/0.040 ms
|
| Code: |
# traceroute6 hetzner.com
traceroute to hetzner.com (2a01:4f8:d0a:529e::2), 30 hops max, 80 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
|
Last edited by paulbiz on Mon Jul 13, 2020 8:45 pm; edited 1 time in total |
|
| Back to top |
|
 |
paulbiz
Guru
Joined: 01 Feb 2004
Posts: 508
Location: St. Louis, Missouri, USA
|
| Posted: Mon Jul 13, 2020 8:43 pm Post subject: |
|
|
| Solved(-ish). It seems to be kernel-related. I upgraded from kernel 5.4.50 to 5.4.51 (same .config) and now it works. So I guess there was some regression in 5.4.50 kernel. Or maybe something was b0rked in my toolchain when I built it. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
