Adding Windows route
Syntax - route add -p <Client host backend network> mask 255.255.252.0 <gateway>
Ex. - route add -p 10.214.6.0 mask 255.255.255.0 10.214.6.0
Syntax - route add -p <Client host backend network> mask 255.255.252.0 <gateway>
Ex. - route add -p 10.214.6.0 mask 255.255.255.0 10.214.6.0
Hi Shana,
ReplyDeleteGood morning!!!
Good to see this block here
Could you please explain us steps brifly
In unix Two different n/w how to communicate each other , if possible please share with example
*dhana
Delete*dhana
DeleteIt depends on the type of network and the number of interfaces each company is using
ReplyDeleteConsider Company network as X and customer network as Y
LAN X<---> Router X <---> Unix Server <---> Router Y <---> LAN Y
Unix Server
-----------
# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.169.139.0 10.174.2.1 255.255.255.128 UG 0 0 0 eth1
10.169.140.0 10.174.2.1 255.255.255.128 UG 0 0 0 eth1
10.169.139.0 10.174.2.1 255.255.255.0 UG 0 0 0 eth1
10.174.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
10.169.137.0 10.174.2.1 255.255.255.0 UG 0 0 0 eth1
0.0.0.0 10.174.2.1 0.0.0.0 UG 0 0 0 eth1
route add -net 10.169.137.0 netmask 255.255.255.0 gw 10.174.2.1 dev eth1
Here, i am adding route for an interface called eth1. Gateway information can also get from netstat -rn output. If you are not sure about the gateway and subnet mask
10.169.137 is the network --- get the subnet mask and gateway from the vlan table or from your network team/Team lead whoever knows the information.
Gateway -- is the entry and exit point of your network. so, you need to add the route to allow communication to other server.
sometimes, though the gw is added, there would be firewall blockage. You need to check about that as well.