• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Problem with assigning IPv6 to new server

VojinP

Basic Pleskian
I have purchased new Centos 8 server without IPv6 support. Since I needed IPv6, they have added it. When I checked ip a I got:

Code:
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:00:82:33:b4:3c brd ff:ff:ff:ff:ff:ff
    inet xxx.xx.xxx.xx/24 brd xxx.xx.xxx.xxx scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::82ff:fe33:b43c/64 scope link
       valid_lft forever preferred_lft forever

and sysctl -a | grep ipv6.*disable :

Code:
net.ipv6.conf.all.disable_ipv6 = 0
net.ipv6.conf.all.disable_policy = 0
net.ipv6.conf.default.disable_ipv6 = 0
net.ipv6.conf.default.disable_policy = 0
net.ipv6.conf.eth0.disable_ipv6 = 0
net.ipv6.conf.eth0.disable_policy = 0
net.ipv6.conf.lo.disable_ipv6 = 0
net.ipv6.conf.lo.disable_policy = 0

so it looks all is OK with IPv6. However when I try to reread IP addresses, got nothing, and when want manually to add one, fe80::82ff:fe33:b43c/64, I got following message:

The specified IP address cannot be used on network interface. You need to specify a valid IP address with subnet prefix range or mask.

Any ide why and how to fix that?
 
CentOS 8 is using NetworkManager. The NetworkManager is not supported in Plesk, and it is recommended to disable this component. I think this may be a reason for this issue.
 
I have tried to ping that IPv6 and it looks it is working, but not in plesk yet...

Code:
[root@scala ~]# ping6 fe80::82ff:fe33:b43c
PING fe80::82ff:fe33:b43c(fe80::82ff:fe33:b43c) 56 data bytes
64 bytes from fe80::82ff:fe33:b43c%eth0: icmp_seq=1 ttl=64 time=0.145 ms
64 bytes from fe80::82ff:fe33:b43c%eth0: icmp_seq=2 ttl=64 time=0.068 ms
64 bytes from fe80::82ff:fe33:b43c%eth0: icmp_seq=3 ttl=64 time=0.074 ms
64 bytes from fe80::82ff:fe33:b43c%eth0: icmp_seq=4 ttl=64 time=0.100 ms
 
Hmm.. it looks it was problem with network configuration. Just edited it and it works now like a charm.
 
Back
Top