09-13-2010
From the routing table of server 3, I can see that it already has a route to the server4 ce0 interface.
10.21.125.32 255.255.255.224 10.6.129.1 1500* 0 1 UG 1 0
10.21.125.32 => 10. 21.125.0010 0000
255.255.255.224 => 255.255.255.1110 0000
-----------------------------------------------------------------
From the last 5 host bits, we should know that the network 10.21.125.32/27 implies that the host IPs are from 10.21.125.32 to 10.21.125.63.
So You only need to add a route server4.
server 4
route add host 10.6.129.33 <appropriate gateway>
from the output you have provided its not clear what the gateway should be. If you can provide a small network diagram(if not full picture, atleast the one that shows cabling between the 2 servers) I might be able to help.
Your ping is failing now because the packets from server3 will reach server4 but server4 will not know how to respond as it does not have a route to server3.
good luck
10 More Discussions You Might Find Interesting
1. AIX
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
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
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
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
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
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
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
8. Solaris
Hi Solaris Experts,
I am trying to add a routing table entry on our 5.1 Generic_144488-12 sun4v sparc Solaris 10 SUNW,SPARC-Enterprise-T5220 so that it is possible to ping 10.56.9.34 node
# netstat -rnv
IRE Table: IPv4
Destination Mask Gateway Device Mxfrg Rtt Ref
Flg Out In/Fwd ... (2 Replies)
Discussion started by: gjackson123
2 Replies
9. Linux
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 :
/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... (5 Replies)
Discussion started by: omkar.jadhav
5 Replies
10. IP Networking
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
LEARN ABOUT MINIX
sockd.route
SOCKD.ROUTE(5) File Formats Manual SOCKD.ROUTE(5)
NAME
sockd.route - Route file for multi-homed SOCKS proxy server
SYNOPSIS
/etc/sockd.route
DESCRIPTION
The file /etc/sockd.route is used by the SOCKS server program sockd to determine which of its network interfaces it should use to reach a
given destination host. It is needed only if your SOCKS server host is multi-homed and your version of sockd supports RBIND. A multi-homed
host is a host with more than one network interfaces and with its IP_FORWARDING turned off. Only the multi-homed version of sockd can be
run on such hosts. You can find out the version of your sockd (or rsockd) by command
sockd -ver
or
rsockd -ver
A line in the file can be up to 1024 characters long. Lines starting with a `#' are comments. Non-comment lines must be of the form
if_addr dst_addr dst_mask
All three fields are required and are separated by spaces or tabs. Each filed is specified in the usual dotted form of IP addresses, e.g.,
128.23.16.2. if_addr must be the IP address of one of the network interfaces on the SOCKS server host. dst_addr specifies either the IP
address of a host, a network, or a subnet in the usual dotted form, e.g., 129.201.4.0, or a domain name, e.g., internic.net. dst_mask spec-
ifies mask for the IP address used in dst_addr. Bits in dst_mask that are set to 0 indicate the bit positions to be ignored during compar-
ison of IP addresses. So, specifying 255.255.255.255 in dst_mask demands an exact match with dst_addr, whereas 0.0.0.0 in dst_mask causes a
matching with any given destination address regardless of what is specified for dst_addr. If a domain name is used for dst_addr, the con-
tents of dst_mask are ignored, though it must still be supplied (simply use 0.0.0.0). If the domain name starts with a period, it speci-
fies a zone and matches all domain names within that zone, otherwise it matches only the domain name itself. For example, xyz.com matches
only xyz.comP, while .xyz.com macthes not only xyz.com, but also abc.xyz.com and this.and.that.xyz.com, among others. The special symbol
ALL (which must be entirely in uppercase) matches everything. Domain names are otherwise case-insentive.
When using a domain name in dst_addr, you have be very careful in maintaining your DNS setup. See the last few paragraphs in sockd.conf(5).
When a multi-homed sockd receives a network request, it first checks with /etc/sockd.fc (or /etc/sockd.conf) to decide whether the request
should be allowed or denied. For an allowable request, sockd then checks the given destination IP address or domain name against the
dst_addr dst_mask pair in /etc/sockd.route, one line at a line. Once a match is found, the network interface of the corresponding if_addr
field is used for connection to the destination host. Remaining lines in the file are skipped. Therefore the order of the lines in the
file is of extreme importance. If no match is found throughout the file, a line indicating the error is produced using syslog with facility
daemon and level err and the request is ignored.
You have the option of using the frozen route file /etc/sockd.fr instead of /etc/sockd.route. The frosen file is produced by make_sockdfr
and is essentially the memory image of the parsed route file. Using it can reduce the start-up delay of the SOCKS server since it eliminate
the need for parsing. Since the SOCKS server always looks for /etc/sockd.fr first, be sure that you always run make_sockdfr every time
after you modifify /etc/sockd.route.
EXAMPLES
Suppose you have a dual-homed host with interface 129.1.2.3 connecting to your internal Class B network 129.1, and interface 129.1.254.1
connecting to the outside world. If you only use the SOCKS server to provide connections to outside hosts, then the file /etc/sockd.route
only needs one line:
129.1.254.1 0.0.0.0 0.0.0.0
If you also use the SOCKS server to provide connection to internal hosts as well, then two lines would suffice:
129.1.2.3 129.1.0.0 255.255.0.0
129.1.254.1 0.0.0.0 0.0.0.0
Note that these two lines must be in the order given above.
If you prefer using domain name instead, the lines should be
129.1.2.3 .myown.com 0.0.0.0
129.1.254.1 0.0.0.0 0.0.0.0
assuming that myown.com is your domain.
SEE ALSO
dump_sockdfr(8), make_sockdfr(8), sockd(8), sockd.fr(5)
May 6, 1996 SOCKD.ROUTE(5)