Sponsored Content
Special Forums IP Networking Packet going out of wrong interface due to OS automatically added cache route with lower metric Post 303004795 by msr1981 on Monday 9th of October 2017 07:34:34 AM
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 ?
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. 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

10. 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
ROUTE(8)						      System Manager's Manual							  ROUTE(8)

NAME
route - manually manipulate the routing tables SYNOPSIS
/sbin/route [ -f ] [ -n ] [ command args ] DESCRIPTION
Route is a program used to manually manipulate the network routing tables. It normally is not needed, as the system routing table manage- ment daemon, routed(8), should tend to this task. Route accepts two commands: add, to add a route, and delete, to delete a route. All commands have the following syntax: /sbin/route command [ net | host ] destination gateway [ metric ] where destination is the destination host or network, gateway is the next-hop gateway to which packets should be addressed, and metric is a count indicating the number of hops to the destination. The metric is required for add commands; it must be zero if the destination is on a directly-attached network, and nonzero if the route utilizes one or more gateways. If adding a route with metric 0, the gateway given is the address of this host on the common network, indicating the interface to be used for transmission. Routes to a particular host are dis- tinguished from those to a network by interpreting the Internet address associated with destination. The optional keywords net and host force the destination to be interpreted as a network or a host, respectively. Otherwise, if the destination has a ``local address part'' of INADDR_ANY, or if the destination is the symbolic name of a network, then the route is assumed to be to a network; otherwise, it is pre- sumed to be a route to a host. If the route is to a destination connected via a gateway, the metric should be greater than 0. All sym- bolic names specified for a destination or gateway are looked up first as a host name using gethostbyname(3N). If this lookup fails, get- netbyname(3N) is then used to interpret the name as that of a network. Route uses a raw socket and the SIOCADDRT and SIOCDELRT ioctl's to do its work. As such, only the super-user may modify the routing tables. If the -f option is specified, route will ``flush'' the routing tables of all gateway entries. If this is used in conjunction with one of the commands described above, the tables are flushed prior to the command's application. The -n option prevents attempts to print host and network names symbolically when reporting actions. DIAGNOSTICS
``add [ host | network ] %s: gateway %s flags %x'' The specified route is being added to the tables. The values printed are from the routing table entry supplied in the ioctl call. If the gateway address used was not the primary address of the gateway (the first one returned by gethostbyname), the gateway address is printed numerically as well as symbolically. ``delete [ host | network ] %s: gateway %s flags %x'' As above, but when deleting an entry. ``%s %s done'' When the -f flag is specified, each routing table entry deleted is indicated with a message of this form. ``Network is unreachable'' An attempt to add a route failed because the gateway listed was not on a directly-connected network. The next-hop gateway must be given. ``not in table'' A delete operation was attempted for an entry which wasn't present in the tables. ``routing table overflow'' An add operation was attempted, but the system was low on resources and was unable to allocate memory to create the new entry. SEE ALSO
intro(4N), routed(8), XNSrouted(8) 4.2 Berkeley Distribution November 16, 1996 ROUTE(8)
All times are GMT -4. The time now is 02:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy