Issue Correct IPV6 Traffic Routing

[Robert Alexander]

Server operating system version

Ubuntu 22.04.4 LTS

Plesk version and microupdate number

Plesk Obsidian v18.0.60_build1800240421.18 os_Ubuntu 22.04

Hi. I bought my 2nd Server from Ionos. It turns out that although they added IPV6, I can not use Imunify360 subscription fully and keep the server secure.
They appear to say that it's not configured for IPV6 Traffic Routing and that will now be an extra cost.

Does anyone know how to do this and if it's very difficult? I'm willing to give it a try once I can see what is required.
I may have misinterpreted this, but it's not 100% easy to get someone to say that if this is done, you won't have the problem.
I'm told also that I could disable IPV6 from the server. Wanted to know the correct way of doing this.
Please feel free to read the answer from Ionos?
____________________________________
Please see below for the latest from Plesk:

"Thank you for the update.
Your server cannot communicate with any IPv6 address (such as Google or other domains). It is related to IPv6 traffic routing.
I see on the server configured these IP addresses:
I haven't displayed everything for security reasons:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
scope global ens6
valid_lft forever preferred_lft forever
scope global
valid_lft forever preferred_lft forever
/128 scope global dynamic noprefixroute
valid_lft 3790sec preferred_lft 2790sec
/64 scope link
valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether d ff:ff:ff:ff:ff:ff
inet brd scope global docker0
valid_lft forever preferred_lft forever

Also, server routing is configured via IPv4 and IPv6:

root@server:~# ip r
default via dev ens6 proto static
dev ens6 proto kernel scope link src
prohibit
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown

root@server:~# ip -6 r
::1 dev lo proto kernel metric 256 pref medium
:/80 dev ens6 proto kernel metric 256 pref medium
:/64 dev ens6 proto ra metric 1024 expires 86139sec pref medium
fe80::/64 dev ens6 proto kernel metric 256 pref medium
default via fe80::1 dev ens6 proto ra metric 1024 expires 1539sec pref medium

Using this address with different masks also looks quite strange (there should be one IP address, no duplication with different masks 80/128):
inet6 /80 scope global
valid_lft forever preferred_lft forever
1/128 scope global dynamic noprefixroute
valid_lft 3790sec preferred_lft 2790sec

root@server:~# traceroute -6 google.com
traceroute to google.com , 30 hops max, 80 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
You need to contact the server provider or network administrator and get the correct settings for IPv6 and also that the provider allows IPv6 routing for your server.
Since the question does not affect the functionality of Plesk and routing is an administrative task, the server administrator and provider should perform this.
As soon as the IP addresses, mask, and IPv6 routing are configured correctly, the server will be able to establish connections with other IPv6 addresses and everything will work without errors.
To check the operation of IPv6, you can use the following command:

# ping -6 google.com

You should see this:

# ping -6 google.com
PING google.com(fra16s51-in-x0e.1e100.net ()) 56 data bytes
64 bytes from fra15s10-in-x0e.1e100.net (): icmp_seq=1 ttl=116 time=4.82 ms
64 bytes from fra16s51-in-x0e.1e100.net (): icmp_seq=2 ttl=116 time=3.73 ms
64 bytes from fra15s10-in-x0e.1e100.net (): icmp_seq=3 ttl=116 time=3.75 ms
64 bytes from fra15s10-in-x0e.1e100.net (): icmp_seq=4 ttl=116 time=3.76 ms
This will mean that IPv6 is configured correctly and routing is working.