Are we seeing the same thing? 🤔
netcup.de is a valid domain from netcup,from what I can see.
In fact,is the domain where this forum is... You can see the attachment.
For me redirects for the .com domain
Edit: I see what you mean.
The link itself is redirecting. The text domain is ok. 😅
netcup.de is the valid DE domain from Netcup.
And the email seems legit. Is a renewal notification about the SSL in your domain.
Just to update: the configuration was correct. Was a issue in the routing - contacted the support and everything is OK now.
Thanks everyone.
Is the rescue system in general capable of using IPv6?
You asked for a clean configuration, there is nothing more clean that the rescue system - where it should be the IPv6 configured from scratch, or at least is what makes sense...since is the system used to debug issues, and if Netcup is providing a /64 address, it should be configured there (of course i can't confirm).
I have mentioned several times, what I want to see.
... where?
What you asked i provided, and you said that "is not valid" and is wrong...
This happens also in rescue system,so is not a change in my os. But fell free for what you need
but there are prefix routes.
Because the config?
Unfortunately, we can't see the configuration you are making. We just see some commands you are typing in, without knowledge of other flying around.
The configuration is there: /etc/sysconfig/network-scripts/ifcfg-eth0
The commands that "i am making" change the configuration file of the system (/etc/sysconfig/network-scripts/ifcfg-eth0).
System eth0" ipv6.method "manual" ipv6.addresses "xxxxx/64" ipv6.gateway "fe80::1
Adds the
IPV6ADDR=2xxxx::1/64
IPV6_DEFAULTGW=fe80::1
etc...
This is how you config ips in Almalinux....
But as I said, the shown configuration files are not matching your active configuration
Where?
And it makes sense to see the default config and start from there since the custom config is not working.
Yes, but the "default" config isn't there anymore - reboot doesn't bring them back.
What can be made, for what i see, is put everything back to a basic state and start from there.
In the configuration above, is there anything wrong?
(Edit: Also, note that IPv6 doesn't work either with the rescue system, just to exclude possible "system errors" that i don't see where are they)
Are you going to type in these commands after every boot?
I don't get it in how is that related with the issue... My issue is that, with the configuration that i am making, the server is not working with IPv6. If i will or not is irrelevant for this...
What does it help to try out different manual commands?
Because... that is how you configure a server? Things don't "appear" working if i don't input the correct commands for it.
Don't understand your point here.
If there is a configuration error
And with the information provided, that is everything that is needed, do you see any issue?
BTW, the resulting configuration of these manual commands is still wrong, there is a subnet route, which should not be there.
What subnet are you talking?
How looks the active configuration if you reboot your system and touch nothing?
I still don't see in how reboot solve the things here. The command that i enter are the normal ones to everyone use (in Almalinux 8)... in every single server.
This is not a temporary change, those commands are to setup the configurations - as they should. Reboot doesn't do nothing.
Also aside, i don't know why are you being kinda rude in those exchanges... chill dude. Im just asking for help... if you cannot or you think that i don't need a answer, just don't answer. Is better that provide vague sentences that don't make sense...
Lets put this straight.
I reset everything ipv6 related back to "normal", and then i folow by this:
sudo nmcli connection modify "System eth0" ipv6.method "manual" ipv6.addresses "xxxxx/64" ipv6.gateway "fe80::1"
sudo nmcli connection modify "System eth0" ipv6.dns "2001:4860:4860::8888,2001:4860:4860::8844"
sudo nmcli connection up "System eth0"
sudo nmcli connection down "System eth0" && sudo nmcli connection up "System eth0"
The result:
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 xxxxx/64 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::xxxxxxx/64 scope link noprefixroute
valid_lft forever preferred_lft forever
ip -6 r
::1 dev lo proto kernel metric 256 pref medium
2xxxxxxxxxxx/64 dev eth0 proto kernel metric 100 pref medium
fe80::/64 dev eth0 proto kernel metric 1024 pref medium
default via fe80::1 dev eth0 proto static metric 100 pref medium
[root@omega ~]#
ping6 fe80::1%eth0
PING fe80::1%eth0(fe80::1%eth0) 56 data bytes
From fe80::xxxxx%eth0 icmp_seq=1 Destination unreachable: Address unreachable
From fe80::xxxxx%eth0 icmp_seq=2 Destination unreachable: Address unreachable
From fe80::xxxxx%eth0 icmp_seq=3 Destination unreachable: Address unreachable
From fe80::xxxxx%eth0 icmp_seq=4 Destination unreachable: Address unreachable
From fe80::xxxxx%eth0 icmp_seq=5 Destination unreachable: Address unreachable
^C
--- fe80::1%eth0 ping statistics ---
6 packets transmitted, 0 received, +5 errors, 100% packet loss, time 5100ms
ping6 ipv6.google.com
PING ipv6.google.com(prg03s10-in-x0e.1e100.net (2a00:1450:4014:80a::200e)) 56 data bytes
From omega.xxx (2xxxx::1) icmp_seq=1 Destination unreachable: Address unreachable
From omega.xxx (2xxxx::1) icmp_seq=2 Destination unreachable: Address unreachable
From omega.xxx (2xxxx::1) icmp_seq=3 Destination unreachable: Address unreachable
^C
--- ipv6.google.com ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3085ms
cat /etc/sysconfig/network-scripts/ifcfg-eth0
BOOTPROTO=none
DEFROUTE=yes
DEVICE=eth0
GATEWAY=8x.xx.0.1
HWADDR=xxxxxx
IPADDR=8xxxxxxxxx
IPV6INIT=yes
#IPV6_ADDR_GEN_MODE="eui64"
#IPV6_DEFAULTGW="fe80::1%eth0"
IPV6_FORCE_ACCEPT_RA=no
NETMASK=255.255.252.0
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
PROXY_METHOD=none
BROWSER_ONLY=no
PREFIX=22
IPV4_FAILURE_FATAL=no
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME="System eth0"
UUID=xxxxxxxx
IPV6_AUTOCONF=no
IPV6ADDR=2xxxx::1/64
IPV6_DEFAULTGW=fe80::1
DNS1=8.8.8.8
DNS2=8.8.4.4
DNS3=2001:4860:4860::8888
DNS4=2001:4860:4860::8844
better now? 
Yes, you are right: the first tests have been made while i still had an "old" configuration, where what changed was only the /128. (my bad sorry)
But was that, and that doesn't change anything else...
With the /64, the result is exactly the same.
What do you mean?
the "2XXX:4XXX:5x:4xx:4xxx:62ff:fe4b:9f5d/64" was added during the tests to resolve the issue, but it should have no impact in this case.
The configuration is being correctly applied, as it should.
In order to debug your problem, you should post your configuration files (IP, router and nameserver), the output from "ip -6 a" (or "ifconfig -a"), from "ip -6 r" and from ping and traceroute commands to external IPs and hostnames.
Here some:
[root@omega ~]# 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 2XXX:4XXX:5x:4xx::1/128 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 2XXX:4XXX:5x:4xx:4xxx:62ff:fe4b:9f5d/64 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::44a0:xxxx:xxxx:9f5d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
[root@omega ~]# ip -6 r
::1 dev lo proto kernel metric 256 pref medium
2XXX:4XXX:5x:4xx::1 dev eth0 proto kernel metric 100 pref medium
2XXX:4XXX:5x:4xx::/64 dev eth0 proto kernel metric 100 pref medium
fe80::/64 dev eth0 proto kernel metric 1024 pref medium
default via fe80::1 dev eth0 proto static metric 100 pref medium
[root@omega ~]# ping6 fe80::1%eth0
PING fe80::1%eth0(fe80::1%eth0) 56 data bytes
From fe80::44a0:xxxx:xxx:xxxd%eth0 icmp_seq=1 Destination unreachable: Address unreachable
From fe80::44a0:xxxx:xxx:xxxd%eth0 icmp_seq=2 Destination unreachable: Address unreachable
From fe80::44a0:xxxx:xxx:xxxd%eth0 icmp_seq=3 Destination unreachable: Address unreachable
From fe80::44a0:xxxx:xxx:xxxd%eth0 icmp_seq=4 Destination unreachable: Address unreachable
^C
--- fe80::1%eth0 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 9210ms
[root@omega ~]# ping6 ipv6.google.com
PING ipv6.google.com(fra16s50-in-x0e.1e100.net (2a00:1450:4001:810::200e)) 56 data bytes
From omega.xxxxxxx (2XXX:4XXX:5x:4xx::1) icmp_seq=1 Destination unreachable: Address unreachable
From omega.xxxxxxx (2XXX:4XXX:5x:4xx::1) icmp_seq=2 Destination unreachable: Address unreachable
From omega.xxxxxxx (2XXX:4XXX:5x:4xx::1) icmp_seq=3 Destination unreachable: Address unreachable
^C
--- ipv6.google.com ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4084ms
[root@omega ~]# traceroute6 google.com
traceroute to google.com (2a00:1450:4001:810::200e), 30 hops max, 80 byte packets
1 omega.xxxxxxx (2XXX:4XXX:5x:4xx::1) 1444.339 ms !H 1444.302 ms !H 1444.286 ms !H
And the settings:
/etc/sysconfig/network-scripts/ifcfg-eth0
BOOTPROTO=none
DEFROUTE=yes
DEVICE=eth0
GATEWAY=8X.5X.0.1
HWADDR=xxxxxxxxxxxx
IPADDR=8x.5x.2.1xx
IPV6ADDR=2xxx:4xxx:5x:4xx::1/64
IPV6INIT=yes
#IPV6_ADDR_GEN_MODE="eui64"
IPV6_AUTOCONF=no
IPV6_DEFAULTGW=fe80::1
#IPV6_DEFAULTGW="fe80::1%eth0"
IPV6_FORCE_ACCEPT_RA=no
NETMASK=255.255.252.0
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
PROXY_METHOD=none
BROWSER_ONLY=no
PREFIX=22
IPV4_FAILURE_FATAL=no
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME="System eth0"
UUID=xxxxxxxxxxxxxxxx
Thank you all! 
Hello,
Did anyone configure IPv6 successfully in a Root Server.
Tried in two different machines, one with AlmaLinux 9 and another with AlmaLinux 8. Both are configured correctly, and the settings applied are correct - gateway is ok, but he doesn't ping when i try.
He ping to another IP in the same subnetwork, but externally, no.
Gateway fe80::1 doesn't ping at all—and I think it should.
Nevertheless, IPv6 doesn't seem to work.
I'm lost in what to do next. I think the issue is in the gateway not being able to "route" correctly.
Has anyone successfully configured IPv6 in a root server?
Thanks!
