Routing Lan to Lan via private WAN

We have set up a suggestion for how a LAN to LAN routing via a private WAN could be set up. For various reasons the default gateway for the headquarter can not be used for routing to the different branches, and only one route can be configured on the gateway (192.168.10.3) for this purpose.

Would this be a good solution?:
http://public.questus.dyndns.org/lan2lan.html

Would there be a better way to design this? The 192.168.10.x is a layer3 switch.

The only path to the Internet would be through 192.168.10.3
McEveAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

td_milesCommented:
When you say only one route, you can still add a route to the gateway thus:

ip route 10.0.0.0 255.0.0.0 192.168.10.x

so that all traffic for 10.x.x.x is sent to 192.168.10.x, then simply configure 192.168.10.x to route as required to the remote LANs.

-----------
If not:

If the device that is labled 192.168.10.x is capable of routing (you say it is a layer-3 switch, so it should be), then make this the default gateway for all of the devices on your network. Then configure the routing in this switch so that anything destined for the remote LANs is sent over the private WAN and then anything else is sent to the gateway (192.168.10.3).

You haven't indicated whether the remote LANs will be accessing the Internet via the 192.168.10.3 gateway or not. If they are going to, then either:
a. The gateway needs to know how to send the traffic back to the 10.0.x.x network (meaning you will still need to add these routes to the gateway)
b. The switch 192.168.10.x does NAT, so that the gateway thinks the traffic is from the local LAN and hence doesn't need to route it.
Remember, this is only if the remote LANs need to access the Internet via the gateway.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
McEveAuthor Commented:
Yes - the "only a (one) route we can add means we can add ip route i.e 10.0.0.0 255.0.0.0 192.168.10.x to the gateway.

The gateway will have to stay gateway for the network.

The remote LAN's will need to access Internett via the gateway yes.

Nat is not an option, there will be printers on each remote lan, whith a static IP, and they will be installed on a printserver on the 192.169.10 net, and will need to be remotely administered.

If 10.0.0.10 needs acess the Internet, then 192.168.10.3 will need to know more than to send 10.0.0.0 255.0.0.0 to 192.168.0.x ?


McEveAuthor Commented:
I haven't forgotten about this question, we just haven't had a chanse to set it up yet, as there's a problem with the lines.

I'll get back to the question when things are set up right.

BTW - What happened to all the coments? I can only see three comments on this thread, and there was quite a few more earlier..?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers

From novice to tech pro — start learning today.