While manually assigning a static IPv6 address on CentOS release 7.9.2009 works. I noticed that another (second) IPv6 address is being generated the so called EUI-64 containing ff::fe in the middle of the host part of the address. I want to remove it and leave only the manually assigned one, but unfortunately not able to. Currently under the interfaces i have the following parameters.


and the interface looks like this:






the interface itself is coming up and L2 and L3 networking is working fine for v4 and v6, but when i issue the command

ip addr show dev br0

I see not only the statically configured ipv6, but also a second ipv6 which is generated based on the EUI-64. I want to get rid of this second IPv6. How do i do that in CentOS?

I have also removed the dhcpv6-client service from all zones in order to see if that will changed anything but it did not .

firewall-cmd --zone=internal --remove-service=dhcpv6-client --permanent
firewall-cmd --zone=home --remove-service=dhcpv6-client --permanent
firewall-cmd --zone=public --remove-service=dhcpv6-client --permanent
firewall-cmd --zone=block --remove-service=dhcpv6-client --permanent
firewall-cmd --zone=dmz --remove-service=dhcpv6-client --permanent
firewall-cmd --zone=drop --remove-service=dhcpv6-client --permanent
firewall-cmd --zone=external --remove-service=dhcpv6-client --permanent
firewall-cmd --zone=trusted --remove-service=dhcpv6-client --permanent
firewall-cmd --zone=work --remove-service=dhcpv6-client --permanent

after that i reloaded the firewall just to be sure.

firewall-cmd --reload 

how to get rid of that EUI-64 address in CentOS/RHEL/FEDORA ?


Linux server 3.10.0-1160.6.1.el7.x86_64 #1 SMP Tue Nov 17 13:59:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

The IPv6 address in question i am trying to remove have scope: scope global mngtmpaddr dynamic i.e. we are not speaking about link local addresses here i.e. not fe80::

  • well there are multiple reasons , here are couple of those. any address containing ff:ffe in the middle is to be considered EUI-64, basically providing the mac address of the machine globally. Some people will consider this a security risk. Another reason is routing. If you have static addresses you know where the traffic is coming from in case you use BGP etc ,, you see the address and you immediately know what prefix that is, in case you have a schema. There are also others, but those 2 should suffice.
    – Tito
    Dec 6, 2020 at 14:41
  • Just to be sure, are you using NetworkManager? Dec 6, 2020 at 17:38
  • @MichaelHampton no i am not using Network manager, thus the line "NM_CONTROLLED=no" in the config. This was deliberate decision. It was related to channel bonding / and 802.1x authentication and ansible, but this is out of the scope of this question.
    – Tito
    Dec 6, 2020 at 19:33
  • You do have a proper mystery then. Might I suggest as a workaround IPV6_PRIVACY=rfc3041 until you are able to find the cause? Dec 6, 2020 at 20:52
  • @MichaelHampton , thank you , i do appreciate it and i will consider it. However the point here is to control the source of the traffic.
    – Tito
    Dec 7, 2020 at 7:49

1 Answer 1


In my case is not enough to put


under the interface config. It was required to put "IPV6_AUTOCONF=no" also in /etc/sysconfig/network

Then the SLAAC was disabled completely and with that also the EUI-64 address.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.