01-10-2008
Thanks for a reply!
I just found out the reason y we are able to ping the private network from our local workstation.
I did a tracert on the command prompt:
[ISS] C:\>tracert 192.168.2.1
Tracing route to 192.168.2.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 172.16.101.254 <- PC gateway
2 <1 ms <1 ms <1 ms 172.16.102.200
3 <1 ms <1 ms <1 ms 192.168.2.1 <- private ip
After disable the private network on 172.16.102.200,
[ISS] C:\>tracert 192.168.2.1
Tracing route to 192.168.2.1 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 172.16.101.254
2 172.16.102.200 reports: Destination host unreachable.
Not sure why the tracert pass through 172.16.102.200. Any ideas?
7 More Discussions You Might Find Interesting
1. IP Networking
i have one private network with one ip address, and i have a seperate network on a seperate ip address.
now, each network is behind a firewall/router. now what i want to do is be able to access one server on the second network from a computer on the first., but with the private ip address, (this... (2 Replies)
Discussion started by: norsk hedensk
2 Replies
2. IP Networking
Hi all,
Currently we are in the progress of setting up a private network on all of our Sun Solaris servers. Purpose is to move all backup tasks to the private, hence reduce load on public network.
Some of our servers only consists of 1 network card but with several ports. Shall we purchase... (10 Replies)
Discussion started by: *Jess*
10 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I just purchased 2 Ultra 10 servers and I want to practice with home networking. I want to create a private network where I can connect both boxes to the internet via broadband using my four port adsl modem/router. My ISP assigns me 192.168 addresses via DHCP and I use the ISP's DNS but... (1 Reply)
Discussion started by: Kongowea
1 Replies
4. IP Networking
Hi all,
please help solving my small issue
below is the configuration
I have 3 systems
sytem1 -------- system 2 ----------system 3
system 1 : 10.255.1.4 & default gw 10.255.1.55
system2 : ip 1 : 10.255.1.55 , ip 2: 10.255.2.1
system 3 : ip : 10.255.2.3
on system 2 : ... (4 Replies)
Discussion started by: Gopi Krishna P
4 Replies
5. IP Networking
how does a router directs the internet traffic to a specific host in the private network?
Example:
My PC has ip 192.168.134.100
Router has ip 192.168.134.200
My company's ip 202.52.150.33
When i try to access internet, say google, it traverses from... (1 Reply)
Discussion started by: Arun_Linux
1 Replies
6. Windows & DOS: Issues & Discussions
Hello,
I have a desktop which has two network cards installed on it and I connected these two card through a hub.
On the desktop in have installed a Windows Vista Home Edition SO and a Windowx XP SO in a virtual way. I also had intalled a Virtual BOX software and Windows XP run through it.
By... (1 Reply)
Discussion started by: zendcool
1 Replies
7. AIX
Able to ping the server but not able to login through putty it says network timeout
Please assist (3 Replies)
Discussion started by: Vishal_dba
3 Replies
LEARN ABOUT FREEBSD
nos-tun
NOS-TUN(8) BSD System Manager's Manual NOS-TUN(8)
NAME
nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel
SYNOPSIS
nos-tun -t tunnel -s source -d destination -p protocol_number [source] target
DESCRIPTION
The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.
Tunnel is the name of the tunnel device /dev/tun0 for example.
Source and destination are the addresses used on the tunnel device. If you configure the tunnel against a cisco router, use a netmask of
``255.255.255.252'' on the cisco. This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
really implement.
Protocol number sets tunnel mode. Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.
Target is the address of the remote tunnel device, this must match the source address set on the remote end.
EXAMPLES
This end, a FreeBSD box on address 192.168.59.34:
nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45
Remote cisco on address 192.168.56.45:
interface tunnel 0
ip address 192.168.61.2 255.255.255.252
tunnel mode nos
tunnel destination 192.168.59.34
tunnel source 192.168.56.45
AUTHORS
Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page. Isao SEKI
<iseki@gongon.com> added a new flag, IP protocol number.
BUGS
We do not allow for setting our source address for multihomed machines.
BSD
April 11, 1998 BSD