two networks + static routing

[beagle9479]

I have two networks, one 192.168.0.x and one 192.168.2.x . The purpose for splitting up my small company is so that half of the people use one DSL line and half use another. I have two BEFSRU31 routers, one for each network. I have both working as DHCP servers for their network. I want the people on the 192.168.2.x network to be able to talk to/see the people on the 192.168.0.x network. From what I understand, static routing is the way I want to go.

I setup static routing on the 192.168.2.x router with destination LAN of 192.168.0.0, subnet of 255.255.255.0 and default gateway 192.168.2.10 (LAN IP of the router). I then ran a network cable from a LAN port on both routers. Machines on the 192.168.2.x network should be able to see computers on the 192.168.0.x network. But they can't.
Please help
Thanks

 

[jimbopalmer]

It is possible that, a computer set as 192.168.1.x with a gateway of 192.168.1.10 and a subnet mask of 255.255.253.0 could see a computer of 192.168.2.x with a gateway of 192.168.2.10 and a subnet mask of 255.255.253.0

the odd subnet mask should tell the computers to allow the following subnets without a router
192.168.0.x
192.168.1.x
192.168.2.x
192.168.3.x
that should include all your computers, so they should not need to route locally, but WILL route to get to any other subnets
I tried to remain child-like, all I acheived was childish.

 

[jimbopalmer]

oops I used .1 and .2, you used .0 and .2 sorry the solution will still work as I covered .0 as well
I tried to remain child-like, all I acheived was childish.

 

[fubartr]

dsl being fibre optic can handle all the traffic your business needs, so why would you have two lines?

Stlll having problems or did the DHCP scope fix it?

the problem you have is a LAN problem Local area network and I think you are correct with the cableing.

you may want to try a protocol other than tcp/ip..my guess is tcp/ip is the only protocol you have loaded.

 

[beagle9479]

Due to the location of the company and the nearest DSL provider, we can only get 144kbps DSL lines. And during these economic times and a boss that doesn't like to spend money, they won't approve for a fractional T1. Therefore, I'm stuck with two 144kbps DSL lines.

The question I have about the subnet mask is that I have a class C network and I believe that the Linksys routers only allow me to have subnet of 255.255.255.0 for all of the client machines. This is from a drop down box. When I use a subnet of 255.255.252.0 (as corrected by someone in a different forum) in the static routing page, I can access the other router, but not the rest of the other network because their subnets are still 255.255.255.0 .

Thanks for the help

 

[jimbopalmer]

By the Way, they make routers for multiple DSL lines, which solves the whole problem

http://www.nexland.com/nexlandstore/merchant.mv?Screen=PROD&Store_Code=NO&Product_Code=200040

the router's subnet mask would not change from 255.255.255.0, just the computers would go to 255.255.252.0 which would let them see both subnets I tried to remain child-like, all I acheived was childish.

 

[AdmanOK]

You are overlooking the fact that, by connecting the two "networks" together you are going to end up with the DHCP servers on the same segment, this is a big no no. The only way that you are going to manage to do this is to manually specify IP addresses at each machine, this way you can split the load between the two boxes. If you do it this way they can even be the same subnet.

Something like shown below. Just alternate between the two routers for different machines.

[tt]Router 1 (192.168.0.1)----| |-----(192.168.0.10) PC1
| | (GW=192.168.0.1)
|------|
| |-----(192.168.0.11) PC2
Router 2 (192.168.0.2) ---| | (GW=192.168.0.2)
|
|-----(192.168.0.12) PC3
(GW=192.168.0.1)[/tt]

 

[pansophic]

Actually, if it were me, I'd turn off one of the router's DHCP server and set one of the routers up with 2 DHCP scopes, delivering IP addresses for both subnets.

Also, you should NEVER assign a subnet mask that is larger than the Class of the subnet, and fortunately the router did not let you do that. If you really want a subnet mask of 255.255.254.0, you should assign a Class B subnet address (like 172.16.x.x) or a Class A subnet (like 10.x.x.x). Assigning this netmask to a Class C subnet (anything where the first octet is greater than 191) is an absolute violation of the standard numbering assignment for IP.

What you really want to do, is just assign a secondary address to each of the routers that has an IP address that falls in the other subnet. I'm not sure how to do this with the Linksys router though.

I would probably purchase a single, real router (like a Cisco 2600) that can support both DSL circuits and actually do load balancing, as opposed to having one circuit fully loaded while another is unutilized. The model that you are operating right now makes this scenario highly probable.

pansophic