SCO # 3
 |
FECO: |
SCO # 3 |
|
MODIFICATION NO: |
N/A | |
|
PRODUCT: |
SCO OPEN SERVER 5 | |
|
SUB-ASSEMBLY: |
N/A | |
|
ESTIMATED MAN HOURS: |
N/A | |
|
CLASS OF CHANGE: |
MANDATORY | |
|
REASON FOR CHANGE: |
SET UP PROCEDURE FOR ROUTES & GATEWAYS | |
|
RELATED FECO/AB |
N/A |
SETTING UP ROUTES & GATEWAYS ON SCO OPEN SERVER 5
1 NOTE:
Throughout this FECO a SPACE in a string is shown by a Ñ .
All other spaces are purely cosmetic
2 ROUTES
2.1 To setup an indirect route
you need to know the destination networks network ID, the next
hop
address (gateway) and the subnet mask to be used. The syntax is as follows:-
route Ñ –v Ñ add Ñ –net Ñ (network ID) Ñ (next hop address) Ñ (subnet mask)
2.2 E.g. you want to connect to an IP
address of 200.201.200.2, with a subnet mask of
255.255.255.0
and you are connecting through a router with a local IP address(next hop
address)
of 128.2.20.7 your route would look like this
route Ñ –v Ñ add Ñ –net Ñ 200.201.200.0 Ñ 128.2.20.7 Ñ 255.255.255.0
2.3 You can type in the route
command from the command line and the route will be added without
having
to stop and start the network. The addition of the route this way is only a temporary
measure
and the route will be lost when the system is rebooted. To avoid this you need to edit
the /etc/tcp
file and add an entry in it, to add the route automatically whenever the system
reboots.
Edit the /etc/tcp file and go to the bottom of the file and add the route before
the exit 0
at
the end of the file.
E.g. / bin / r m Ñ -f Ñ / tmp / tps $$
/ etc / route Ñ -v add Ñ -net Ñ 200.201.200.0 Ñ 128.2.20.7 Ñ 255.255.255.0
exit Ñ 0
2.4 This will then allow
the route to be added when the system reboots. You can check the routes
on
the system by typing netstat Ñ –r n from #
prompt. You should get a result that looks
something
like the following.
2.5 Routing tables
Destination Gateway Flags Refs Use Interface
127.0.0.1 127.0.0.1 UH 2 32 lo0
128.2.20 128.2.20.21 UC 1 0 net1
128.2.20.21 127.0.0.1 UGHS 4 26 lo0
200.201.200 128.2.20.7 UGS 0 2 net1
2.6 This shows our
route has been added and that to get to a destination address with a network
ID
of 200.201.200.0. the system will direct the request to an IP address of 128.2.20.7
for routing.
2.7 You can then test
your routes by trying to ping or telnet an IP address on the destination network
to
see if the routing has been configured correctly on the hardware.
3 GATEWAYS
3.1 A gateway can be
setup to route to another network or IP address but can only be activated by
restarting
the network.
3.2 To add a gateway,
you need to edit the /etc/gateways file and add a gateway to a network or
host.
The syntax is:-
net|host (address) gateway (address2) metric (hops) active|passive|external
3.3 Where (addo UGHS 4 26 lo0
192.168.0.1 128.2.20.7 UGH 0 0 net1
192.168.10 128.2.20.7 UG 0 0 net1
200.201.200 128.2.20.7 UGS 0 0 net1
4 You can
then test your gateway by trying to ping or telnet an IP address on the destination
network
to
see if the routing has been configured correctly on the hardware.