CentOS / RHEL: Remove Routes 169.254.0.0 / 255.255.0.0 From the System

Posted on in Categories , last updated November 4, 2011

How do I disable the route 169.254.0.0 / 255.255.0.0 from CentOS or RHEL 6 Linux server?

zeroconf (Zero configuration networking), is a techniques that automatically creates a usable Internet Protocol (IP) network without manual operator intervention or special configuration servers. 169.254.0.0/255.255.0.0 route is part of zeroconf under RHEL 6 / CentOS 6 or older versions. To see current routing table, enter:
# route -n
Sample outputs:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
74.8x.4y.zz     0.0.0.0         255.255.255.248 U     0      0        0 eth1
10.10.29.64     0.0.0.0         255.255.255.192 U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 eth1
10.0.0.0        10.10.29.65     255.0.0.0       UG    0      0        0 eth0
0.0.0.0         74.8x.yy.zz     0.0.0.0         UG    0      0        0 eth1

Every time the server or Linux desktop boots, the zeroconf route 169.254.0.0 is enabled and added to the kernel routing table. To disable zeroconf route under RHEL / CentOS / Fedora Linux, enter:
# vi /etc/sysconfig/network
Append the following directive:

NOZEROCONF=yes

Save and close the file. Reboot the system / server or restart the networking service:
# /etc/init.d/network restart
Verify routing table, enter:
# route -n
OR
# ip route

9 comment

      1. Thats not really an answer, the answer to this would be you defeat the possibility of having machines setup networks between each other in the absence of operator intervention.

        1. I ask myself, what are the benefits of changing a default setting, especially when I have bigger fish to fry. If it ain’t broken, don’t fix it.

          1. … until something breaks and you are lost in a sea of “defaults” and “unknown configurations” !
            The best recipe for serious troubles.
            The reason we keep our place tidy, is to be able to get what we want when we want it. I have the feeling that you have not lived any troubleshooting nightmares, swearing at the people that prepared that stuff.
            I suppose, you never got a NFS mount not working just because of such a default route driving somewhere else.

    1. That is outside of the scope of this article.
      However, googling will show you that you edit /etc/sysconfig/network and add the keyword “gateway” like so:
      GATEWAY=10.0.0.1

      Replace 10.0.0.1 with the default gateway you desire. After, just restart networking. (/etc/init.d/networking restart)

Leave a Comment