static routes

skiv71

Inactive User
Joined
Jan 23, 2007
Messages
41
Reaction score
0
hi,

i have a small network....

linksys am200
adsl modem router----> 192.168.0.* LAN ----> linksys BEFSR41 router -----> 192.168.10.* LAN

the AM200 is: -

ip: 192.168.0.1
sub: 255.255.255.0

the BEFSR41 is config as: -

WAN
ip: 192.168.0.254
sub: 255.255.255.0
g/w: 192.168.0.1
DNS: 192.168.0.100 (active directory server)

LAN
ip: 192.168.10.254
sub: 255.255.255.0

all pc's on the .10 subnet are config by DHCP: -

ip: 192.168.10.*
sub: 255.255.255.0
g/w: 192.168.10.254
dns 192.168.10.254
and can reach the .0 subnet and the internet.

the pc's on the .0 subnet are config by DHCP: -
ip: 192.168.0.*
sub: 255.255.255.0
g/w: 192.168.0.1
dns 192.168.0.100 (active directory)
and can reach the internet and the BEFSR41 (WAN).

i tried adding a static route in the AM200....

ip: 192.168.10.0
sub: 255.255.255.0
g/w: 192.168.0.254
i/f: LAN

when i try a ping, get host unreachable...

does the am200 broadcast the new subnet to the .0 subnet clients, so they may reach it?

am i forced to add a route at the .0 subnet clients, i.e. ROUTE ADD 192.168.10.0 mask 255.255.255.0 192.168.0.254

with it working, should a tracert to a .10 subnet ip , show a hop as 192.168.0.1, then 192.168.0.254?

please, what am i missing?

thanks

neil

PS am i right in thinking that if the .10 clients dont have the correct g/w, they cannot be reached outside their network?

now i think about it, i'm pretty sure they dont have the g/w filled in :-s lol

comments please
 
Last edited:

Timbo

Member ++
Joined
May 8, 2006
Messages
782
Reaction score
18
Location
In the arcade!
hi,

i have a small network....

linksys am200
adsl modem router----> 192.168.0.* LAN ----> linksys BEFSR41 router -----> 192.168.10.* LAN

the AM200 is: -

ip: 192.168.0.1
sub: 255.255.255.0

the BEFSR41 is config as: -

WAN
ip: 192.168.0.254
sub: 255.255.255.0
g/w: 192.168.0.1
DNS: 192.168.0.100 (active directory server)

LAN
ip: 192.168.10.254
sub: 255.255.255.0

all pc's on the .10 subnet are config by DHCP: -

ip: 192.168.10.*
sub: 255.255.255.0
g/w: 192.168.10.254
dns 192.168.10.254
and can reach the .0 subnet and the internet.

the pc's on the .0 subnet are config by DHCP: -
ip: 192.168.0.*
sub: 255.255.255.0
g/w: 192.168.0.1
dns 192.168.0.100 (active directory)
and can reach the internet and the BEFSR41 (WAN).

i tried adding a static route in the AM200....

ip: 192.168.10.0
sub: 255.255.255.0
g/w: 192.168.0.254
i/f: LAN

when i try a ping, get host unreachable...

does the am200 broadcast the new subnet to the .0 subnet clients, so they may reach it?

am i forced to add a route at the .0 subnet clients, i.e. ROUTE ADD 192.168.10.0 mask 255.255.255.0 192.168.0.254

with it working, should a tracert to a .10 subnet ip , show a hop as 192.168.0.1, then 192.168.0.254?

please, what am i missing?

thanks

neil

PS am i right in thinking that if the .10 clients dont have the correct g/w, they cannot be reached outside their network?

now i think about it, i'm pretty sure they dont have the g/w filled in :-s lol

comments please


OK, I have drawn out your network on a piece of paper and all it fine for outgoing traffic due to the correct default gateways being setup on the routers and clients so:

INTERNAL LAN ---> Internet works fine.

The problem you have is the reverse routing. You will indeed need to setup static routes on each of the clients if the routers are not capable of having static routes added to their routing tables.

and remember, the default gateway on clients (unless in extreme cases static routes have been added) must be in the same subnet as your NIC's.

e.g default gateway for a 192.168.0.* machine will be on the same 192.168.0.* network and 192.168.10.* clients must have 192.168.10.1 or 254 etc set as gateway.

So, have a look on the linksys router (sorry I am not familiar with it) in your network to see if you can add a static routes on them (better than adding routes to all client PC's)... e.g. on the BEFSR41 try to add a route:

192.168.10.0
255.255.255.0
192.168.0.1

the router should then see the traffic for 192.168.10.* and say "hey.. I have those addresses" and shove all data to that subnet to be dealt with by the relevent node.

otherwise you will indeed need to add a static route to each PC on the 192.168.0.* network to gain access to hosts on the 192.168.10.* network, but as i said earlier you'd be better with a router that can have a static route added to it's own table.

Hope that helps and I have understood the problem...
 

magistral

Inactive User
Joined
Mar 16, 2007
Messages
32
Reaction score
0
A simpler answer is to change the subnet mask to 255.255.0.0

the 3rd octet of 255 in your current mask only allows you to access 192.168.0.x addresses. If you use 192.168.10.x addresses then you have to increase the subnet mask

Mike
:FRIGHT:
 
TEST
Top