Islands in the Net: Subnets and Samba

[swinggang]

Ok. Big question:

I have two subnets: 192.168.254.* and 192.168.0.*. The 0.* machines are in another room, connected via a "router" PC with two ethernet cards, one with 192.168.254.72 and the other with 192.168.0.1. The 0.1 address acts as the gateway and the 0.* machines see the 254.* machines perfectly.

Now, the 254.* PCs can't see the 0.* PCs. I'm sure I need to set up a gateway on the 254.* PCs to access the 0.* PCs, but I'm not sure how. Which IPs should I use? Netmasks? Help! My poor users are stuck on the other side of a wide chasm!

;)

Thanks for the help.

[chikn]

Whatever machine is routing the 0 to 254 should be the same to route 254 to 0 on your network. That machine should be the gateway for both. 254.72 should be the gateway for the 254 subnet and 0.1 should be the gateway for the other.

[cowanrl]

Originally posted by swinggang:
<STRONG>
Now, the 254.* PCs can't see the 0.* PCs. I'm sure I need to set up a gateway on the 254.* PCs to access the 0.* PCs, but I'm not sure how. Which IPs should I use? Netmasks? Help! My poor users are stuck on the other side of a wide chasm!

;)

Thanks for the help.</STRONG>

On the 254.* PCs, the default gateway needs to be set to 192.168.254.72. A suitable netmask for you situation should be 255.255.255.0 Make sure you have your subnet masks the same on all machines.

When you say the 254.* PCs can't see the 0.* PCs, do you mean they can't even ping them or they just can't see Samba or Windows shares on them?

[swinggang]

I can't even ping them...

I'm a little confused where to assign the gateway. I know 192.168.254.72 should be the gateway to 0.*, but how do I tell the 254.* machines to look for 192.168.0.* machines through that gateway.

JB

[swinggang]

Another problem: my gateway out to the internet is 192.168.254.254. By changing the default, am I cutting those machines off?

JB :confused:

[chikn]

Originally posted by swinggang:
<STRONG>Another problem: my gateway out to the internet is 192.168.254.254. By changing the default, am I cutting those machines off?

JB :confused:</STRONG>


What device is using 254.254. If its another other than your PC router than yes you will cut them off. You can howevwer add a static route to your router to direct that traffic through the 192.168.254.254 gateway.

[DMR]

Originally posted by swinggang:
<STRONG>I know 192.168.254.72 should be the gateway to 0.*, but how do I tell the 254.* machines to look for 192.168.0.* machines through that gateway.</STRONG>On each of the 254.* machines:
route add default gw 192.168.254.72

But yes, that will blow away your current default gateway to the Net.

[cowanrl]

If you just want to add a route to the 192.168.0.0 network on a 254.* machine without changing the default gateway, you might want to use something like this on a Linux machine:

route add -net 192.168.0.0 netmask 255.255.255.0 eth0

Of cours, use the netmask you are using on your network and the ethernet interface on computer you are adding the route on. Usually if there is only 1 nic it is eth0.

If they are Windoze machines, it's just a little different:

route add 192.168.0.0 mask 255.255.255.0

On linux machines you can use route --help or man route to get specifics on the command. On Windoze machines, use route /? to get some help.

[ 20 June 2002: Message edited by: cowanrl ]

[cowanrl]

I wanted to delete it but I couldn't figure out how. Is one of the icons at the top of the post for deleting it?

[chikn]

Originally posted by cowanrl:
<STRONG>I wanted to delete it but I couldn't figure out how. Is one of the icons at the top of the post for deleting it?</STRONG>

Choose to edit the post and check the little delete this post box kinda top leftish.

[cowanrl]

Originally posted by chikn:
<STRONG>Choose to edit the post and check the little delete this post box kinda top leftish.</STRONG>

Found it. It's gone.

[bwkaz]

So delete them!

Duh :p

[chikn]

Originally posted by The original mdwatts:
<STRONG>Now we have 4 (now 5) extra posts on discussing how to delete one single post. :rolleyes:</STRONG>

Heh now 7

[swinggang]

Wow, just think. I caused all this traffic.

Re: my problem: figured it all out, I guess. 254.* still can't talk to 0.*, but we can get full connectivitiy vi ip-based printing (lpr) and file-sharing via http. But thanks for the help, anyway. I guess we'll just have to suffer not being able to ping a bunch of crappy old Windoze boxes and Macs from our fancy Linux machines.

All the best,
JB :D