Differences

This shows you the differences between two versions of the page.

--- wiki:ip_route_issue_with_local_addresses [2021/04/22 10:38] – created walkeradmin
+++ wiki:ip_route_issue_with_local_addresses [2023/03/09 22:35] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Use Watch for repetitive command line actions ======
+====== IP Route Issue with Local Addresses ======
 <color darkorange>Apr 2021</color>
 \\
@@ Line 6: / Line 6: @@
 ----
-When you perform an action from the command line, it gets executed just once. So if you type <color #ed1c24>Date</color>, you will see the current time and date at the execution time of the command. But sometimes it is very useful if you are looking for a change to have your command line executed many times, and this can be achieved with a command called <color #ed1c24>Watch</color>.
+I was having some issues with Teaming interfaces being able to ping outside of the local LAN. When I started to look at the issue I noticed a lot of routes for local addresses that I had not configured.
 \\
 \\
 ----
-==== Using Watch ====
+==== Routes ====
-Using <color
+To see the routes just use:
+\\
+    ip route
+\\
+When doing this I observed the following:
+<file>
+ip route
+default via 192.168.1.1 dev mngt
+.0.0.0/8 dev eth2 proto kernel scope link src 10.0.154.2
+.0.0.0/8 dev eth3 proto kernel scope link src 10.0.154.3
+.0.0.0/8 dev eth4 proto kernel scope link src 11.0.154.4
+.0.0.0/8 dev eth5 proto kernel scope link src 11.0.154.5
+.254.0.0/16 dev eth2 scope link metric 1002
+.254.0.0/16 dev eth3 scope link metric 1003
+.254.0.0/16 dev eth4 scope link metric 1004
+.254.0.0/16 dev eth5 scope link metric 1005
+.254.0.0/16 dev mngt scope link metric 1008
+</file>
+So the default root is fine (via mngt) mngt is my team for the two management interfaces (eth0 and eth1). The rest of the interfaces (eth2-eth5) are for data and are not teamed.
+\\
+\\
+What concerned me was the list of 169.254.0.0 addresses on eth2, eth3, eth4 and eth5. These interfaces have static addresses, dhcp is not configured and the DEFROUTE is set to no.
+\\
+\\
+To be honest, I don't think they were causing any issues, but I wanted them gone, so here is what we did.
+\\
+\\
+----
+==== Remove Routes ====
+I wasn't able to remove the routes by using <color #ed1c24>ip route del</color> so the method used was as follows:
+\\
+\\
+Edit the file <color #ed1c24>/etc/sysconfig/network</color> (it's probably empty)
+\\
+\\
+Add the line <color #ed1c24>NOZEROCONF=yes</color> to the file and save and exit
+\\
+\\
+Now reboot the server.
+\\
+\\
+After this, performing an <color #ed1c24>ip route</color> shows the following:
+\\
+<file>
+ip route
+default via 192.168.1.1 dev mngt
+.0.0.0/8 dev eth2 proto kernel scope link src 10.0.154.2
+.0.0.0/8 dev eth3 proto kernel scope link src 10.0.154.3
+.0.0.0/8 dev eth4 proto kernel scope link src 11.0.154.4
+.0.0.0/8 dev eth5 proto kernel scope link src 11.0.154.5
+.168.1.0/24 dev mngt proto kernel scope link src 192.168.1.154
+</file>
+All of the 169.254.0.0 reference are gone.
+\\
+\\
+\\