03-13-2012
Who told it's mandatory to add static routes on UNIX servers? If you have a router in place, just make an entry for default gateway (IP of the Router's interface connected to the server) on the UNIX server and that's it. Your router should be able to route the packets to and from the UNIX server. In case if you do not have a dedicated router and your network is small enough (why would anyone need multiple subnets in that case!!), you may enable static routes in your UNIX server.
This User Gave Thanks to admin_xor For This Post:
10 More Discussions You Might Find Interesting
1. Debian
Ok, I made changes to my routing tables..... which file do I modify to make the routes initialize correctly when the machine boots up? I work with all flavours of Unix/Linux... but this is an older box...
Linux, Release 2.2.14-5.0.
I did a grep for the default route in /etc, but didnt find... (2 Replies)
Discussion started by: djsal
2 Replies
2. SCO
Hi,
I add following routes manually each time system reboots:
#route add 192.168.1.0 -gateway 192.168.0.90
#route add 192.168.200.0 -gateway 192.168.0.200
Is there any way in SCO 7.1.1 to automate this route add process? i.e. each time system reboots, it automatically adds these routes in... (1 Reply)
Discussion started by: tayyabq8
1 Replies
3. Solaris
Hi there
When adding a route (or indeed deleting a route) which file is amended ? I am moving a box from one network to another and when it starts up it tries to connect run 'add net 192.x.x.x' etc etc ...but i dont want it to do that
where do I edit these route additions
cheers (5 Replies)
Discussion started by: hcclnoodles
5 Replies
4. AIX
I added a static route through smit using:
Communications applications and Services ==>
TCIP/IP ==>
Further Configuration ==>
Static Routes ==>
Add a Static Route ==>
Route Type of host
Filled in Destination Address, Default Gateway Address and Network Interface of en0.
This... (2 Replies)
Discussion started by: jyoung
2 Replies
5. Solaris
Hi,
I need help to add new route:
10.252.0.138, GW 10.252.0.129 to e1000g1
and
10.252.0.10, GW 10.252.0.1 to e1000g2
tnx (4 Replies)
Discussion started by: mehrdad68
4 Replies
6. IP Networking
hello, i need help on setting my coyote linux, i've working on this for last 5 days, can't get it to work. I've been posting this message to coyote forum, and other linux forum, but haven't get any answer yet. Hope someone here can help me...... please see my attached picture first.
... (0 Replies)
Discussion started by: dlwoaud
0 Replies
7. SCO
Hi all,
n00b here. We currently have 3 SCO 5.0.5 machines in our network that run a mission management system.
Our internal network was always a 10.0.0.0 network and the machines worked fine.
Our company is going through a network upgrade for VoIP and some of our departments are now on... (5 Replies)
Discussion started by: gibson_hg
5 Replies
8. Programming
I'm writing a program which uses curl to be run on Linux PCs which will be used by a number of different users. I cannot make the users all install curl on their individual machines, so I have tried to link curl in statically, rather than using libcurl.so. I downloaded the source and created a... (8 Replies)
Discussion started by: BrandonShw
8 Replies
9. Red Hat
Hi All,
Is there a quick way to check whether the current routes on my centos are
persistent or not before rebooting ?
i can take a route -n output but i may completely lost access to my server if the routes are gone.
thanks. (1 Reply)
Discussion started by: coolatt
1 Replies
10. Red Hat
I have three systems A,B,C. I want to configure A in such a way that all packets from A to C goes via B.
I tried:
1. ip route add 'ip of C' via 'ip of B'
2. route add -net 'net address' netmask gw 'ip of B'
These commands work initially when I try a ping or traceroute and expire after... (2 Replies)
Discussion started by: kanak
2 Replies
LEARN ABOUT CENTOS
ocf_heartbeat_route
OCF_HEARTBEAT_ROUTE(7) OCF resource agents OCF_HEARTBEAT_ROUTE(7)
NAME
ocf_heartbeat_Route - Manages network routes
SYNOPSIS
Route [start | stop | monitor | meta-data | validate-all]
DESCRIPTION
Enables and disables network routes.
Supports host and net routes, routes via a gateway address, and routes using specific source addresses.
This resource agent is useful if a node's routing table needs to be manipulated based on node role assignment.
Consider the following example use case:
- One cluster node serves as an IPsec tunnel endpoint.
- All other nodes use the IPsec tunnel to reach hosts in a specific remote network.
Then, here is how you would implement this scheme making use of the Route resource agent:
- Configure an ipsec LSB resource.
- Configure a cloned Route OCF resource.
- Create an order constraint to ensure that ipsec is started before Route.
- Create a colocation constraint between the ipsec and Route resources, to make sure no instance of your cloned Route resource is started
on the tunnel endpoint itself.
SUPPORTED PARAMETERS
destination
The destination network (or host) to be configured for the route. Specify the netmask suffix in CIDR notation (e.g. "/24"). If no
suffix is given, a host route will be created. Specify "0.0.0.0/0" or "default" if you want this resource to set the system default
route.
(unique, required, string, no default)
device
The outgoing network device to use for this route.
(unique, optional, string, no default)
gateway
The gateway IP address to use for this route.
(unique, optional, string, no default)
source
The source IP address to be configured for the route.
(unique, optional, string, no default)
table
The routing table to be configured for the route.
(optional, string, no default)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 20.
stop
Stops the resource. Suggested minimum timeout: 20.
monitor
Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10.
reload
Suggested minimum timeout: 20.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 20.
EXAMPLE
The following is an example configuration for a Route resource using the crm(8) shell:
primitive p_Route ocf:heartbeat:Route
params
destination=string
op monitor timeout="20" interval="10" depth="0"
SEE ALSO
http://www.linux-ha.org/wiki/Route_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_ROUTE(7)