Sponsored Content
Operating Systems Linux Add persistent route in cent os 6.5 Post 302959134 by omkar.jadhav on Thursday 29th of October 2015 07:39:09 AM
Old 10-29-2015
Add persistent route in cent os 6.5

Hi ,

I have cent os 6.5 and am trying to make few routes permanent for bond:
i have added two routes using below two commands :
Code:
/sbin/route add -net 10.0.0.0 netmask 255.0.0.0 gw  10.59.160.128
/sbin/route add -net 0.0.0.0 netmask 0.0.0.0 gw  49.44.52.90

post which route command output is as below :
Code:
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
49.44.52.96     *               255.255.255.224 U     0      0        0 bond1
10.59.163.128   *               255.255.255.192 U     0      0        0 eth0
10.70.77.0      *               255.255.255.192 U     0      0        0 bond0
link-local      *               255.255.0.0     U     1002   0        0 eth0
link-local      *               255.255.0.0     U     1014   0        0 bond0
link-local      *               255.255.0.0     U     1015   0        0 bond1
10.0.0.0        10.59.160.128   255.0.0.0       UG    0      0        0 eth0
default         49.44.52.90    0.0.0.0         UG    0      0        0 bond1

but afeter i restart the network routes are not persistent , output of route command post network restart is as follows :
Kernel IP routing table
Code:
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
49.44.52.96     *               255.255.255.224 U     0      0        0 bond1
10.59.163.128   *               255.255.255.192 U     0      0        0 eth0
10.70.77.0      *               255.255.255.192 U     0      0        0 bond0
link-local      *               255.255.0.0     U     1002   0        0 eth0
link-local      *               255.255.0.0     U     1014   0        0 bond0
link-local      *               255.255.0.0     U     1015   0        0 bond1
default         10.59.160.128   0.0.0.0         UG    0      0        0 eth0

can someone please let me know how i can add correct routes permanently which will persist post network restart as well.
 

10 More Discussions You Might Find Interesting

1. AIX

route add

Hello , We have 3 rs/6000 server's running aix on our local network, so each time I try to ping one of these servers we get a "network is down" error , I've been instructed to use to route add command which is ... #route add server.ip router.ip after this the ping command works fine ,... (6 Replies)
Discussion started by: cubicle^dweller
6 Replies

2. IP Networking

Do I need to add a route??

I have two networks connected by cisco routers. My first subnet is 192.168.0.0 and my second is 192.168.1.0. My SCO unix machine is on the 192.168.1.0 subnet with an IP of 192.168.1.231. It can see the entire .1.0 subnet but nothing on the other network. My cicso router(gateway) to the other... (6 Replies)
Discussion started by: agoodrich
6 Replies

3. HP-UX

Add Route on HP-UX v10.x, help.

Hi, My H-UX box has the GW pointing to 10.10.10.1 and I need add it a new route pointing to 192.168.80.x with the GW 10.10.10.13 I tried with: #route add 192.168.80.2 255.255.255.255 10.10.10.13 but I get: add net 192.168.80.0: gateway 255.255.255.0: Network is unreachable I tried with... (4 Replies)
Discussion started by: efrenba
4 Replies

4. IP Networking

Route add probleme

I have a system that i want to reach via a vpn created vi a fierwall.The fierwall in an other system. The ip i am trying to get to is 172.16.4.48 I need to get to it via the hme1 interface. The vpn gateway has this ip 172.30.50.1 I need to clean up the routing table and make this work; or is it... (5 Replies)
Discussion started by: waterboy
5 Replies

5. Solaris

Route Add

Hi, I am trying to add route command in Solaris 10 machine in the following fashion: route add -host 10.8.112.10 180.144.1.250 -interface lo0:1 this command fails with an error "lo0:1: bad value" I want to add a route to 10.8.112.10 that picks 180.144.1.250 as the gateway via the... (3 Replies)
Discussion started by: sudhir_shet
3 Replies

6. IP Networking

route add

I have built a new linux server, via a iLo connection. and I am trying to connect via my desktop to the server I have just built to the management port eth0 via putty. Please could some one advise how to connect to this server from my desktop. Do i need to create add a route access on the... (0 Replies)
Discussion started by: venhart
0 Replies

7. Solaris

Add route to solaris10

Hi need to add 2 routes, one on each server. I know the route add comand but I have always been given the parameters to put in. I need a route in each of the 2 following servers to be able to ping and ssh between them. But how do i know which netmask to put in the route add command ? In... (6 Replies)
Discussion started by: vettec3
6 Replies

8. AIX

Unable to add persistent IP

i am trying to make HACMP but when i add a persistent ip, error shows unable to determine address for 'UPIDGIS1_pers' pls help me out AIX - 5.3 HACMP -5.4 thanks (2 Replies)
Discussion started by: reply.ravi
2 Replies

9. Solaris

Add route to solaris 10

I need to add a new route on solaris10 machine. I want that all traffic on the 23 port (telnet) use 192.168.200.1 gateway. How I do ? Thank you in advance. (1 Reply)
Discussion started by: arfry
1 Replies

10. IP Networking

Add explicit route

Add explicit route to 10.128.255.41/32 , gateway: 10.128.201.254 if not working, please try gateway through management port: 10.128.55.254 Just want to double confirm if this would be the correct command #route add -net 10.128.255.41/32 10.128.201.254 And if didnt work #route add... (1 Reply)
Discussion started by: Thilagarajan
1 Replies
ARP(4)							   BSD Kernel Interfaces Manual 						    ARP(4)

NAME
arp -- Address Resolution Protocol SYNOPSIS
#include <netinet/if_ether.h> DESCRIPTION
The Address Resolution Protocol (ARP) is a protocol used to dynamically map between Internet host addresses and Ethernet addresses. It is used by all the Ethernet interface drivers. It is not specific to Internet protocols or to Ethernet, but this implementation currently sup- ports only that combination. ARP caches Internet-Ethernet address mappings. When an interface requests a mapping for an address not in the cache, ARP queues the message which requires the mapping and broadcasts a message on the associated network requesting the address mapping. If a response is provided, the new mapping is cached and any pending message is transmitted. ARP will queue at most one packet while waiting for a response to a mapping request; only the most recently ``transmitted'' packet is kept. If the target host does not respond after several requests, the host is con- sidered to be down for a short period (normally 20 seconds), allowing an error to be returned to transmission attempts during this interval. The error is EHOSTDOWN for a non-responding destination host, and EHOSTUNREACH for a non-responding router. The ARP cache is stored in the system routing table as dynamically-created host routes. The route to a directly-attached Ethernet network is installed as a ``cloning'' route (one with the RTF_CLONING flag set), causing routes to individual hosts on that network to be created on demand. These routes time out periodically (normally 20 minutes after validated; entries are not validated when not in use). An entry for a host which is not responding is a ``reject'' route (one with the RTF_REJECT flag set). ARP entries may be added, deleted or changed with the arp(8) utility. Manually-added entries may be temporary or permanent, and may be ``published'', in which case the system will respond to ARP requests for that host as if it were the target of the request. In the past, ARP was used to negotiate the use of a trailer encapsulation. This is no longer supported. ARP watches passively for hosts impersonating the local host (i.e. a host which responds to an ARP mapping request for the local host's address). DIAGNOSTICS
duplicate IP address %x sent from ethernet address %x:%x:%x:%x:%x:%x. ARP has discovered another host on the local network which responds to mapping requests for its own Internet address with a different Ethernet address, generally indicating that two hosts are attempting to use the same Internet address. SEE ALSO
inet(4), route(4), arp(8), ifconfig(8), route(8) Plummer, D., "RFC 826", An Ethernet Address Resolution Protocol. Leffler, S.J. and Karels, M.J., "RFC 893", Trailer Encapsulations. BSD
April 18, 1994 BSD
All times are GMT -4. The time now is 08:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy