Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2 Lan's, One Internet Gateway

Status
Not open for further replies.

tomjermy

IS-IT--Management
Aug 21, 2003
13
GB
Hi,

We have 2 lans set up at the office... one works with an old SCO (eugh) system:
client ip addresses: 6.0.0.11 and up
server ip address: 6.0.0.10

We also have a seperate windows network:
192.168.1.1 - internet gateway
192.168.1.2 and up are all client machines.

The subnets for both of these networks are 255.255.255.0.


I would like to give the unix network to access to the windows network internet gateway.


I would have thought that putting the following entry into MSDOS on those machines on the UNIX network would do the trick;
"
route add 0.0.0.0 mask 255.255.255.0 192.168.0.1
"

But I get the following problem:
"
The route addition failed: Either the interface index is wrong or the gateway do
es not lie on the same network as the interface. Check the IP Address Table for
the machine.
"

Please could you give me advice on whether this is feasible and if so how to do it?

Thanks,
Tom Jermy
 
You cannot add a Gateway IP that is on a different subnet.
 
Hmm... both the unix network and the MS Network are on subnet:
255.255.255.0

Does this not make them on the same subnet? Confused.

Thanks,
Tom J
 
Are both networks connected to a common router?

Must be, right?

Anyway, the route add is incorrect and should be:
0.0.0.0 0.0.0.0 to the router interface IP address for the UNIX subnet.

Then, in the router, you need a similar route statement: 0.0.0.0 0.0.0.0 192.168.1.1 (or whatever IP address the FIREWALL has)

Your goal is to create a path for all, 0.0.0.0 0.0.0.0, unknown addresses from the client to your internet device.

Nettekkie1010
 
255.255.255.0 means that only the last portion of the address identifies hosts in the same subnet.

6.0.0.x and 192.168.1.x are different networks.

 
For starters, the 255.255.255.0 is not the network address, it is the subnet mask which tells which part of the IP is the network address and which part is the host address. In your case, the SCO side network address is 6.0.0 and the host is the last number. Windows, you have 192.168.1 for a network address and the last number is the host.

You have bigger problems, I'm afraid. If you work for the US Dept of Defense, you might be good to go. Otherwise, your 6.0.0.xxx IP addresses are not going to fly when you connect to the internet. DOD owns those addresses. Based upon the description of your Windows network, I would guess that you have something doing address translation for internet access, which is well and good.

Most devices that do address translation will only handle one network, so the box that is translating your 192.168.1 network will not handle another. If you need to keep the networks separate, you will need another such device and another internet connection.

If there is no need to continue maintaining two networks, change the 6.0.0 addresses to 192.168.1 addresses and set 192.168.1.1 as your default route and you should be good to go.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top