01-25-2011
The reason is quite simple: you've placed the VM in the 192.168.50.0/24 network, but the host machine is in the 172.20.3.0/24 network. To establish communication between these the default gateway (172.20.3.2) would have to know how to route between these.
Put the VM into the correct network and connections should work without problems.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, dear all, I am rather new to Unix and have this problem where I cant seem to ping from 1 host to another. The scenerio is as follows: -
1 QNX host->Eth->1 SCO host
the SCO host is configured with it's IP
the QNX host is configured with another IP
both in the same domain, ie, 172.20.3.XX... (3 Replies)
Discussion started by: gavon
3 Replies
2. IP Networking
The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot (2 Replies)
Discussion started by: gavon
2 Replies
3. Solaris
Hello,
I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems:
1. When I execute the command ping, I get weird results:
bash-3.00$ usr/sbin/ping localhost ... (4 Replies)
Discussion started by: Przemek
4 Replies
4. Solaris
Hello
I have a server in it.siroe.com
I added it.siroe.com in /etc/resolv.conf.
I still can't ping the server.
any service to restart here?
any other file to edit?
thx (4 Replies)
Discussion started by: melanie_pfefer
4 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
I have a VM on Solaris 10 setup on a windows vista host machine.
1) Vista host i configure
VMnet 1: 10.1.1.10
Mask : 255.255.255.0
Subnet : 10.1.1.2
DNS : 10.1.1.100
2) Solaris on VM
Network device is on Custom(VMNET1)
IP : 10.1.1.4
Mask : 255.255.255.0
... (8 Replies)
Discussion started by: JuveZzZ
8 Replies
6. Windows & DOS: Issues & Discussions
Hello All,
I have searched and searched, but I am not finding any answers. Any help would be very welcome.
I have a home LAN centered around an Untangle gateway (up to date).
I have a Windows 7 PC and a Snow Leopard Mac
I also have two virtualized instances of windows (xp and 7) running... (1 Reply)
Discussion started by: toadtilley
1 Replies
7. Linux
Hi,
I am using win7 on my PC and installed VMware on it on which i am running linux
I am unable to ping my linux guest from my win machine,
but i can ping my windows host from linux guest :
Below is my system configuration
Linux
root@localhost ~]# ifconfig
eth0 Link... (9 Replies)
Discussion started by: chander_1987
9 Replies
8. Solaris
Hi All,
I am new to solaris environment and we are using Solaris 9
The problem is am unable to ping a particular server from from one of the solaris server
The traceroute also shows only * * * for all the 30 hops
I tried to check all the settings like
1) /etc/hosts -> contains the... (17 Replies)
Discussion started by: Sanjay255
17 Replies
9. Solaris
Dear,
I hope you all will be ok.
I have an issue with Solaris box running on x86 Blade.
I am unable to ping a node neither traceroute. I am able to do traceroute from oce0:6 port which have IP and subnet of same type which oce0:1 has.
details are as follows:
Problem:
root@rinams02:/#... (3 Replies)
Discussion started by: khaniqshahid
3 Replies
10. Solaris
Hello All,
Host - Windows 7 64 BIT
Guest OS - Solaris 10 64 on VMWARE workstation
Problem : I can not ping solaris VM from my host OS. please suggest the solution.
Host OS:ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : INPS01900LT
... (5 Replies)
Discussion started by: sunil_1111
5 Replies
route(8c) route(8c)
Name
route - manually manipulate the routing tables
Syntax
/etc/route [ -f ] [ -n ] command args ]
Description
The program is used to manipulate the network routing tables manually. However, normally it is not needed, as the system routing table
management daemon, should tend to this task.
The program accepts two commands: add, to add a route and delete, to delete a route.
All commands have the following syntax:
/etc/route command [ net | host ] destination gateway [ metric ]
In this syntax, destination is a host or network for which the route is to, gateway is the gateway to which packets should be addressed,
and metric is an optional count indicating the number of hops to the destination. The metric is required for add commands. It must be
zero if the destination is on a directly-attached network, and nonzero if the route utilizes one or more gateways.
When adding a route with metric 0, the gateway given is the address of this host on the common network, indicating the interface to be used
for transmission. Routes to a particular host are distinguished from routes to a network by interpreting the Internet address associated
with destination. The optional keywords net and host force the destination to be interpreted as a network or host, respectively. If the
destination has a local address part of INADDR_ANY, then the route is assumed to be to a network. Otherwise, it is presumed to be a route
to a host. If the route is to a destination connected via a gateway, the metric should be greater than 0. All symbolic names specified
for a destination or gateway are looked up first as a host name using If this lookup fails, is then used to interpret the name as that of a
network.
The command uses a raw socket and the SIOCADDRT and SIOCDELRT ioctls to do its work. As such, only the superuser can modify the routing
tables.
Options
-f Flushes the routing tables of all gateway entries. If is used with one of the commands described above, the tables are flushed prior
to the command's application.
-n Prevents attempts to print host and network names symbolically when reporting actions.
Restrictions
The change operation is not implemented. Therefore, you should first add the new route, and then delete the old one.
Diagnostics
add [host | network] %s: gateway %s flags %x"
The specified route is being added to the tables. The values printed are from the routing table entry supplied in the ioctl call. If the
gateway address used was not the primary address of the gateway (the first one returned by the gateway address is printed numerically as
well as symbolically.
delete [ host | network] %s: gateway %s flags %x
The specified route is being deleted from the tables. The values printed are from the routing table entry supplied in the ioctl call. If
the gateway address used was not the primary address of the gateway (the first one returned by the gateway address is printed numerically
as well as symbolically.
%s %s done
When the flag is specified, each routing table entry that is deleted is indicated with a message of this form.
Network is unreachable
An attempt to add a route failed because the gateway listed was not on a directly-connected network. The next-hop gateway must be given.
not in table
A delete operation was attempted for an entry which was not present in the tables.
routing table overflow
An add operation was attempted, but the system was low on resources and was unable to allocate memory to create the new entry.
See Also
intro(4n), routed(8c)
route(8c)