08-31-2005
The system startup files are located in /etc/rc2.d. You can add a file to this directory with the routing entries you have made and each time the system boots, it will add the entries automatically.
I always use a filename that will appear at the bottom of the list in the /etc/rc2.d/directory: for example, "S99zed"
Create the file and using vi, make the following entries:
route add 192.168.1.0 -gateway 192.168.0.90
route add 192.168.200.0 -gateway 192.168.0.200
Each time the system boots it will read the S99zed file and add the routes.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need some help adding routes in sco.
I am using SCO Openserver 5.0.4.
Basically I have 2 gateways here. The first is 10.15.1.1 and allows me access to the rest of the computers in the office and in other offices.
The other gateway is 10.15.10.2 and is the sonicwall that will allow access... (3 Replies)
Discussion started by: cstovall
3 Replies
2. 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
3. AIX
Hi All,
I have a AIX server running v5.2 and its having multiple default routes configured to two seperate gateway.
Here's the output of -- netstat -rn
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups
Route Tree for Protocol Family 2... (2 Replies)
Discussion started by: rramanuj
2 Replies
4. 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
5. IP Networking
Hi,
How can i delete the following routes on my OpenBSD 4.1 system?
# route -n show (including only relevant ipv6-routes)
Internet6:
Destination Gateway Flags Refs Use Mtu Interface
::/104 ::1 UGRS 1 0 ... (1 Reply)
Discussion started by: phalcos
1 Replies
6. Solaris
Hey Gurus.
My routes add using route add , are lost , after reboot.....where caould i save this routes a dont lost them ? Sun Solaris 10 is my OS.
Thanks in advance,
AGADEA. Unix ADMIN (3 Replies)
Discussion started by: aggadtech08
3 Replies
7. 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
8. IP Networking
I would really appreciate some help with HP UX's Network Routes.
Basically, what I want to do is, I would want a system with global ip (eg: 202.144.138.122) to ping/access my HP-UX server which is with private IP address (192.168.1.23). I have all the routers/switches in between properly route... (2 Replies)
Discussion started by: damchey
2 Replies
9. 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
10. SCO
Hi,
Just a question of thought. Why one needs to add static routes on Unix servers ? If I had ethernet card, it already has the settings for gateway for incoming and outgoing requests. We donot have to explicitly set the route it should take. Then what is the use... (3 Replies)
Discussion started by: dextergenious
3 Replies
GRE(4) BSD Kernel Interfaces Manual GRE(4)
NAME
gre -- encapsulating network device
SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file:
device gre
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_gre_load="YES"
DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where
they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop.
gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands.
This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the
type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco
routers. gre also supports Cisco WCCP protocol, both version 1 and version 2.
The gre interfaces support a number of additional parameters to the ifconfig(8):
grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option.
enable_csum Enables checksum calculation for outgoing packets.
enable_seq Enables use of sequence number field in the GRE header for outgoing packets.
EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.*
/
/
+------ the Internet ------+
Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal
address 192.168.2.1, the following commands will configure the tunnel:
On router A:
ifconfig greN create
ifconfig greN inet 192.168.1.1 192.168.2.1
ifconfig greN inet tunnel A B
route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1
On router B:
ifconfig greN create
ifconfig greN inet 192.168.2.1 192.168.1.1
ifconfig greN inet tunnel B A
route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1
NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending
on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8).
For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop.
The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero.
SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8)
A description of GRE encapsulation can be found in RFC 2784 and RFC 2890.
AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org>
Heiko W.Rupp <hwr@pilhuhn.de>
BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as
if they would belong to this interface.
The sequence number field also used only for outgoing packets.
BSD
November 7, 2014 BSD