Login or Register to Ask a Question and Join Our Community


IP Networking

Packet going out of wrong interface due to OS automatically added cache route with lower metric

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums IP Networking Packet going out of wrong interface due to OS automatically added cache route with lower metric
# 1  
Old 10-09-2017
Packet going out of wrong interface due to OS automatically added cache route with lower metric
RHEL 7.0, IPV6

Scenario:
I have routed specific network using network scripts.
1. "ip -6 route show" shows that route has been added. ( with metric 1024)
2. Ping of the specific IP through that route is successful.
3. Now after few days, for some reason, we see that cache route appears for that given destination IP with lower metric ( which is actually trying to take it through interface/bond of the default route.)Ping to that destination IP fails then because packet is going out of wrong interface.
4. If I delete that cache route, again the packet starts going out of the correct interface ( which is not interface of the default route) and ping is successful.

Has anyone faced similar issue with REHL. I am using RHEL 7
Questions:
Q1. In what situation OS will try to route through default, even if static route for specific IP/network exists.
Q2. How to configure the route so that OS does not fall back on default route if specific interface is assigned for a specific ip/network by static configuration. Please note, we can not delete the default route.
Q3. Even if OS is creating cache route for some temporary situation, why is it not detecting that situation has normalized and why it is not deleting the automatically created cache route then. ( assuming that some temporary network side failure caused this issue )

Please note, we are not facing this issue for IPV4. We are facing this with IPV6
Can anyone suggest on how to permanently resolve this situation ?
# 2  
Old 10-09-2017
So to save us from guessing and trying to interpret your description only, can you paste the output from your various network display commands so we can actually see the configuration. It will be far easier to work it out from that.


Thanks, in advance,
Robin
This User Gave Thanks to rbatte1 For This Post:
RudiC
# 3  
Old 10-10-2017
Please see below output of ip -6 route show.

default route is
Code:
default via 2405:200:370:237::1 dev bond1  metric 1

specific route for network that was added:
Code:
2405:200:370:10::/64 via 2405:200:370:236::1 dev bond0.236  metric 1024

cache route added automatically by OS with metric 0 was as below.
Code:
2405:200:370:10::20 via 2405:200:370:237::1 dev bond1  metric 0  cache

This cache route caused packet to go out of default route instead of the specific route. Destination IP is not reachable from the default route. cache route had to be deleted manually for normal traffic to resume.
--------------------------------------------------------------------------


Code:
ip -6 route show 
unreachable ::/96 dev lo  metric 1024  error -101
unreachable ::ffff:0.0.0.0/96 dev lo  metric 1024  error -101
unreachable 2002:a00::/24 dev lo  metric 1024  error -101
unreachable 2002:7f00::/24 dev lo  metric 1024  error -101
unreachable 2002:a9fe::/32 dev lo  metric 1024  error -101
unreachable 2002:ac10::/28 dev lo  metric 1024  error -101
unreachable 2002:c0a8::/32 dev lo  metric 1024  error -101
unreachable 2002:e000::/19 dev lo  metric 1024  error -101
2405:200:201:400:172:16:21:156 via 2405:200:370:243::1 dev bond3.243  metric 1024 
2405:200:201:400:172:16:21:157 via 2405:200:370:243::1 dev bond3.243  metric 1024 
2405:200:310:15::2a via 2405:200:370:240::1 dev bond2.240  metric 0  cache 
2405:200:310:15::56 via 2405:200:370:240::1 dev bond2.240  metric 0  cache 
2405:200:310:15::/64 via 2405:200:370:240::1 dev bond2.240  metric 1024 
2405:200:311:230::11 via 2405:200:370:230::1 dev bond3.230  metric 0  cache 
2405:200:311:230::/64 via 2405:200:370:230::1 dev bond3.230  metric 1024 
2405:200:311:247::11 via 2405:200:370:243::1 dev bond3.243  metric 0  cache 
2405:200:311:247::12 via 2405:200:370:243::1 dev bond3.243  metric 0  cache 
2405:200:311:247::13 via 2405:200:370:243::1 dev bond3.243  metric 0  cache 
2405:200:311:247::/64 via 2405:200:370:243::1 dev bond3.243  metric 1024 
2405:200:314:170::/64 via 2405:200:370:236::1 dev bond0.236  metric 1024 
2405:200:360:10::/64 via 2405:200:370:236::1 dev bond0.236  metric 1024 
2405:200:370:10::20 via 2405:200:370:237::1 dev bond1  metric 0  cache 
2405:200:370:10::/64 via 2405:200:370:236::1 dev bond0.236  metric 1024 
2405:200:370:16::2a via 2405:200:370:240::1 dev bond2.240  metric 0  cache 
2405:200:370:16::56 via 2405:200:370:240::1 dev bond2.240  metric 0  cache 
2405:200:370:16::/64 via 2405:200:370:240::1 dev bond2.240  metric 1024 
2405:200:370:228::/64 dev bond3.228  proto kernel  metric 256 
2405:200:370:230::/64 dev bond3.230  proto kernel  metric 256 
2405:200:370:231::/64 dev bond4  proto kernel  metric 256 
2405:200:370:234::/64 dev bond3.234  proto kernel  metric 256 
2405:200:370:236::/64 dev bond0.236  proto kernel  metric 256 
2405:200:370:237::/64 dev bond1  proto kernel  metric 256 
2405:200:370:238::/64 dev bond0.238  proto kernel  metric 256 
2405:200:370:239::/64 dev bond0.239  proto kernel  metric 256 
2405:200:370:240::/64 dev bond2.240  proto kernel  metric 256 
2405:200:370:242::/64 dev bond3.242  proto kernel  metric 256 
2405:200:370:243::13 dev bond3.243  metric 0  cache 
2405:200:370:243::/64 dev bond3.243  proto kernel  metric 256 
2405:200:370:244::/64 dev bond2.244  proto kernel  metric 256 
2405:200:a10:fc82::/64 via 2405:200:370:243::1 dev bond3.243  metric 1024 
unreachable 3ffe:ffff::/32 dev lo  metric 1024  error -101
fe80::/64 dev bond0  proto kernel  metric 256 
fe80::/64 dev bond1  proto kernel  metric 256 
fe80::/64 dev bond2  proto kernel  metric 256 
fe80::/64 dev bond3  proto kernel  metric 256 
fe80::/64 dev bond4  proto kernel  metric 256 
fe80::/64 dev eno4  proto kernel  metric 256 
fe80::/64 dev ens1f3  proto kernel  metric 256 
fe80::/64 dev bond0.236  proto kernel  metric 256 
fe80::/64 dev bond0.238  proto kernel  metric 256 
fe80::/64 dev bond0.239  proto kernel  metric 256 
fe80::/64 dev bond2.240  proto kernel  metric 256 
fe80::/64 dev bond2.244  proto kernel  metric 256 
fe80::/64 dev bond3.228  proto kernel  metric 256 
fe80::/64 dev bond3.230  proto kernel  metric 256 
fe80::/64 dev bond3.234  proto kernel  metric 256 
fe80::/64 dev bond3.242  proto kernel  metric 256 
fe80::/64 dev bond3.243  proto kernel  metric 256 
fe80::/64 dev ens6f3  proto kernel  metric 256 
default via 2405:200:370:237::1 dev bond1  metric 1

----------------------------------------------------------
Configuration for the bond is as follows.

Code:
 /etc/sysconfig/network-scripts ] cat route6-bond0.236
  2405:200:370:10::/64 via 2405:200:370:236::1 dev bond0.236
  2405:200:314:170::/64 via 2405:200:370:236::1 dev bond0.236
  2405:200:360:10::/64 via 2405:200:370:236::1 dev bond0.236

Code:
 /etc/sysconfig/network-scripts ] cat ifcfg-bond0.236 
  DEVICE=bond0.236
  BOOTPROTO=none
  ONBOOT=yes
  VLAN=yes
  IPV6INIT=yes
  IPV6_AUTOCONF=no
  IPV6ADDR=2405:200:370:236::12/64

Code:
 /etc/sysconfig/network-scripts ] cat route6-bond1 
   via 2405:200:370:237::1 dev bond1

Code:
  /etc/sysconfig/network-scripts ] cat ifcfg-bond1 
  DEVICE=bond1
  BONDING_MASTER=yes
  BONDING_OPTS="miimon=100 mode=1"
  BOOTPROTO=none
  ONBOOT=yes
  IPADDR=10.71.167.102
  NETMASK=255.255.255.240
  IPV6INIT=yes
  IPV6_AUTOCONF=no
  IPV6ADDR=2405:200:370:237::12/64
  IPV6_DEFAULTGW=2405:200:370:237::1


Moderator's Comments:
Mod Comment
Please wrap all code, files, input & output/errors in CODE tags.
It makes them easier to read and preserves spaces for indenting or fixed width data.

Last edited by rbatte1; 10-10-2017 at 06:54 AM.. Reason: Added CODE tags
# 4  
Old 10-23-2017
Friends,

No one has observed similar problem in RHEL7 for IPV6 ?
No guesses as to why this problem happened ? Let me know if more information is required.

Thanks in anticipation
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

A little complex: why my packet don't route?

I have solaris11 running in a kvm virtual machine,network works fine. I can configure it with dhcp or static. Of course packet forward in kvm machine is enabled The solaris11 machine can ping external network. I have setup a solaris10 zone inside the vm the solaris 10 zone use exclusive ip... (3 Replies)
Discussion started by: Linusolaradm1
3 Replies

2. UNIX for Dummies Questions & Answers

iptables / ip route packet routing with multiple gateways

Hi all. Linux noob here. I was hoping someone could help me with configuring some routing rules on my router, an Asus AC68. The router is connected to two gateways, wan0_gateway and wan1_gateway. I have rules set up in the router gui that will push all traffic from every IP other than my own... (0 Replies)
Discussion started by: Bishi
0 Replies

3. Shell Programming and Scripting

How to automatically store/cache password for kerberos authentication

Hi All, I am currently writing script to get the details for lot of hosts from jump server. Means each and every time it will ssh to the host and get the information. To achieve that I need to automatically accept the password from Jump server to that main hosts. We are using kerberos password... (6 Replies)
Discussion started by: kamauv234
6 Replies

4. IP Networking

Route packets over specified interface

Hi, I'm quite new to unix networking and ip tables. I'm running a debian (htpc) server with two NIC's; eth0 and wlan0. I'm trying to set it up in a way that eth0 is the default interface for internet, but some processes should run through wlan0. For example, I'm using eth0 for downloads... (2 Replies)
Discussion started by: Subbeh
2 Replies

5. Red Hat

Static route not added

Hello Guys.. I am facing this weird problem of static route not added after reboot!! Following is my route-<interface> file.. # cat /etc/sysconfig/network-scripts/route-eth0 ADDRESS0=172.31.0.1 NETMASK0=255.255.255.255 GATEWAY0=192.168.208.1 ADDRESS1=172.31.15.2... (3 Replies)
Discussion started by: parth_buch
3 Replies

6. Solaris

vfstab enteries automatically added during live upgrade

i am trying to patch a solaris 10 server using live upgrade. issue is, when i create a new BE and activate it during reboot the file system that are mounted but doesnt have an entry in vfstab are automatically added in vfstab of new BE. looks like live upgrade uses df -h output as reference... (0 Replies)
Discussion started by: chidori
0 Replies

7. Solaris

Packet loss on ce interface.

Hi, I am using the ce interface on my Solaris 9 server and there is significant packet loss when transmitting large packets. Does anyone have a fix for this? ----10.1.0.0 PING Statistics---- 51 packets transmitted, 42 packets received, 17% packet loss round-trip (ms) min/avg/max =... (12 Replies)
Discussion started by: sparcman
12 Replies

8. HP-UX

How to determine network interface that will be used to send a packet for an IP

Hello, I'm writing to you because I encountered the following problem. My program displayes all network interfaces that are available in the system, but I would like to add a functionality in which a user can enter a destination address IP (ex. the IP address of the Google search engine) and will... (1 Reply)
Discussion started by: foxrafi
1 Replies

9. UNIX for Dummies Questions & Answers

Routes being automatically added

Hello, I have two AIX 5.3 servers that are supposedly set up exactly the same. The problem I am having is on one of the servers, it seems dynamic routes are being added mysteriously and non-periodically. This only happens on one server and not the other. Also, there doesn't seem to be a specific... (1 Reply)
Discussion started by: Conutmonky
1 Replies

10. UNIX for Dummies Questions & Answers

there was a strange character(^M) been added automatically in UNIX

I used Notepad to compile my txt file and then I transferred this file to UNIX. When I use vi to open the file, I found that at the end of each line there was a "^M" character. In the original txt file there was not this character. Why this character would been added automatically in UNIX? (4 Replies)
Discussion started by: Jasmine
4 Replies
Login or Register to Ask a Question