Posted on 01/24/2010 7:00:06 AM PST by djf
I have tried and tried to find USABLE info on the meaning and use of subnet masks.
Here is my issue.
I have a local wireless DSL router. He's configed to be 192.168.0.1 locally.
All my machines that talk to it have static IP addresses assigned to them from a range starting at 192.168.0.66 upwards
Now I have some software that runs on one of the boxes sorta like VMWARE where it runs a host image. He has a hard assigned IP address of 192.168.0.100
There is packet sniffing and routing software running ON THAT BOX that allows me, from a DOS prompt, to ping 192.168.0.100 Also, from the host image software running on that box, I can successfully ping 192.168.0.70 (the ip address for that flavor of windows).
But none of my other boxes anywhere on the network know who what or where is 192.168.0.100. Neither does the main ethernet dsl router.
So I'm trying to find the right (if there even is one) ROUTE command that I can enter on Box X that tells him "Listen: if you get a request for 192.168.0.100, the route for it is through 192.168.0.70"
I have searched in vain through the internet to find a page that gives a simple explanation of route masks, but it's been a total waste. I UNDERSTAND binary arithmetic!!
WHEN does he use a routing mask? WHAT is the input and WHAT IS THE SIGNIFICANCE of the output.
No matter what I try to enter on a ROUTE command I keep getting DESTINATION is the same as the Start or some such rubbish!!!
ARGHHHHH!!!
TIA!
Your LOCAL network should have a netmask of 255.255.255.0 Let me ask you, do you have more than 1 router on the network or just one, period?
getting a headache as i just flashed on my CCNA classes.
The usual mask used is 255.255.255.0, where for the 192.168.0.x address range the 192.168.0 is the network address and the .x (what ever number x represents) is the device address.
A mask of 255.255.0.0 would be a network address of 192.168 with device addresses of y.x.
A mask of 255.255.255.248 would give a very restricted device address range of only a couple of usable addresses.
Hardware-wise, just one.
But the packet sniffing-routing software on the box I run the vmware stuff could be described as a software router.
Here’s the deal.
The software runs on Box A. Box A has an IP of 192.168.0.70
The virtual software runs also on box A and has an ip of 192.168.0.100
From a dos prompt on box A, I can ping 192.168.0.100
From the virtual machine on box A, I can do a ping 192.168.0.70
So Windows on box A can talk to the virtual machine and the wirtual machine can talk to windows.
But here I come on box B. Box B can ping 192.168.0.70 just fine
But I want box B to know that if he gets a request for 192.168.0.100, to send it to 192.168.0.70, and not just send it to the default gateway, the DSL router, which is 192.168.0.1
Clear the arpa cache on the boxes. arp -a
Try adding a default route on the other boxes to reach the router. Check the rote man page for syntax
These would work under unix:
Route add default 192.168.0.1 netmask 255.255.0.0 (default route)
or
Route add host netmask 255.255.0.0 192.168.0.1 1 (static route, one is a hop)
or
Route add netmask 255.255.0.0 net 192.168.0.0
Lol!
Classic beauty.
No sweats or thongs needed!!
So I’m trying to find the right (if there even is one) ROUTE command that I can enter on Box X that tells him “Listen: if you get a request for 192.168.0.100, the route for it is through 192.168.0.70”
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx?mfr=true
http://linux.about.com/od/commands/l/blcmdl8_route.htm
As I understand it: your VM is able to ping its host computer, and vice versa, but the outside world can’t see the VM, and vice-versa.
Sounds like you have host-only networking selected in VMWare (or whatever you’re using). Change to Bridged or NAT, and you should see the rest of your network from within the VM.
(And why not use DHCP? So much more flexible. Devices such as printers which require a static address can still have their static address.)
What virtual-machine package are you using? Not VMWare, apparently. Parallels? VirtualBox? Xen? ...
First, all devices must be on the same subnet to see each other. It sounds like you’re having problems setting the subnet (which determines the address range).
Second, switches and routers must be properly configured.
Third, make sure the physical cabling isn’t screwed up (for example, using or not using a crossover cable).
This may sound like gibberish, so maybe we need to walk you through it.
Perhaps your router is a she and not a he. ;-)
I think you need to set the default gateway on 192.168.0.100 to 192.168.0.70. Then you would give 192.168.0.70 it's gateway to the router.
Routing can only be between networks. You can not ROUTE within a network. See my earlier reply. The mask defines the networks.
What is the mask on your main router? If it is 255.255.255.0, you can not route anywhere within that range. In other words you can not route between 192.168.0.70 and 192.168.0.100.
See but 192.168.0.100 (the virtual machine on box A) NEVER talks directly to my main DSL router, which is 192.168.0.1
My main router doesn’t know boo about 192.168.0.100
So if I’m sitting on another machine on my wireless network, I can’t log on to or ftb or do anything to 192.168.0.100
I can do whatever I want to 192.168.0.70, but not the virtual machine running on that Windows box.
I need the gateway on all my machines to be 192.168.0.1, which is my main DSL wireless router.
Can you have more than 1 gateway and what happens if you do??
route add -host 192.168.0.100 gw 192.168.0.70
That's for Linux, depending on your OS, YMMV.
Sounds more like a firewall running on the VMWare host machine. also could be that the host needs to bridge the virtual network adapter to the network.
Kinda sorta...
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.