04-09-2006
hello,
if your 10.100.a.b behind somekind of NAT - you need to pass the traffic through a static port translation so your server can reach the other end.
a static route maybe wont do the trick.
cheers.
Last edited by stdout; 04-09-2006 at 03:55 PM..
10 More Discussions You Might Find Interesting
1. IP Networking
Hi
I know this problem is more likely some windows problem but it has also something to do with unix.
We have a windows nt environment wich uses AIX (unix) machines as file servers (samba). In our windows network environment we nicely see al the unix file servers via the 10 MB network. Last... (2 Replies)
Discussion started by: Mark Detrez
2 Replies
2. IP Networking
following Problem.
I configured my SuSE Linux 8.0 as a router. I4l, named, ip_forward, iptables (NAT/MASQUERADING) are running or are aktivatet.
I just can get a internet connection about the proxy server squid, but if i want to use other protocols i need functional routing.
(I had this... (1 Reply)
Discussion started by: razor
1 Replies
3. IP Networking
I have a question concerning networking. Could any forum
members explain to me why I might be getting "no route
to host" messages when I try to connect through ftp and
http protocols?
I have went to my etc/hosts file and everything seems to be
configured properly. I can connect within my... (1 Reply)
Discussion started by: cstovall
1 Replies
4. IP Networking
hi all,
how do i make sure that the new routing should take effect on the os memory right away? what should i run after i add all the new "route add ....".
I have an example below:
bash-2.03# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface... (1 Reply)
Discussion started by: itik
1 Replies
5. Solaris
Hi,
I got problem of Sun Solaris 8 routing.
IP of SunA is 10.16.64.164, and have routing table:
10.16.64.0 10.16.64.164 U 1 19236 bge1
10.6.0.0 10.6.0.3 U 1 16534 bge0
224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
Discussion started by: milo
4 Replies
6. Solaris
I have a SUN ultra 5 machine running Solaris 6. it has two ethernet interfaces qe0 192.168.0.111 and qe1 192.168.1.111
the two subnets are 192.168.0.111 255.255.255.0
192.168.1.111 255.255.255.0
the specified routes are
add route -net 192.168.0.0 255.255.255.0 192.168.0.111
add route... (3 Replies)
Discussion started by: adol65
3 Replies
7. IP Networking
ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2
inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255
ether 0:14:4f:55:82:9
ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
inet 10.231.11.232 netmask... (1 Reply)
Discussion started by: busyboy
1 Replies
8. Solaris
ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2
inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255
ether 0:14:4f:55:82:9
ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
inet 10.231.11.232 netmask... (3 Replies)
Discussion started by: busyboy
3 Replies
9. Solaris
Hi,
I have two physical interfaces on a servers.
We have connected them to differerent subnets.
1) First interface:
10.158.49.87 to newtwork 10.158.49.0, its gateway is 10.158.49.1
(It is added as default gateway)
It is existing set up. It works well
2) Second interface:
... (1 Reply)
Discussion started by: sri243
1 Replies
10. Solaris
Hello All,
Problem is that redundancy doesn't work, probably a routing issue I need to get sorted out When 172.29.11.x net is down, neither node3 nor node4 is trying 172.29.12.x network,The problem lies in network 172.29.13.x
if 172.29.11.x network is down, node3/node4 should route to... (6 Replies)
Discussion started by: nadeemahmed
6 Replies
LEARN ABOUT MINIX
dump_sockdfr
DUMP_SOCKDFR(8) System Manager's Manual DUMP_SOCKDFR(8)
NAME
dump_sockdfr - Display contents of frozen route file for SOCKS server
SYNOPSIS
dump_sockdfr [infile]
DESCRIPTION
dump_sockdfr reads in a frozen route file for the SOCKS server and produces a listing of its contents on the standard output.
The argument is optional; if omitted, /etc/sockd.fr is assumed.
The frozen route file is produced by make_sockdfr and is essentially the memory image of the parsed route file. Using the frozen route file
can reduce the start-up delay of the SOCKS server program since it no longer has to parse the file contents.
When the SOCKS server starts, it always looks for the frozen route file /etc/sockd.fr first. If that file is not found, it then tries to
use the plain-text route file /etc/sockd.route. If you use frozen route file, you must remember to run make_sockdfr every time after you
modify the plain-text file or the SOCKS server will continue to use the frozen version of a previous route file.
FILES
/etc/sockd.fr, /etc/sockd.route
SEE ALSO
make_sockdfr(8), sockd.fr(5), sockd.route(5)
AUTHOR
Ying-Da Lee, yingda@esd.sgi.com or yingda@best.com
May 6, 1996 DUMP_SOCKDFR(8)