[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 370
  • Last Modified:

I need to connect to the internet from all sites on a WAN via a broadband connection in one of the branch offices.

I have a WAN consisting of a head office with 3 Cisco 805 routers and three remote sites each with its own 805 router. The Cisco 805's have 1 serial connection and 1 ethernet connection.

One of the branch offices has a broadband connection to the internet which all of the other sites want to access. A SonicWall firewall in the branch office is the gateway to the internet.  All of the sites need to be able to access each other.

I'm undecided as to whether to use RIP or static routes.

If I use RIP how do I make the firewall in the branch office the gateway of last resort for all of the other sites.


Can I have static routes for all inter-site traffic and have a gateway of last resort that routes through to the firewall in the branch office.


1 Solution
Hi johnhickey,
For security you are better off using static routes.
For the remote sites just have the default gateway being their router which is what you would have already.
For the routers at the main site have static routes for all remote sites defined and a default gateway pointing to the firewall.
On the firewall have the default gateway set to the Internet router and static routes defined to the remote sites.
Brother John,
I would say that GR isn't incorrect, but just a difference of philosophy.  Rip is the easiest of the routing protocols to configure and even in a small network, it's helpful to build yourself the foundation for growth.  Who knows when the boss is going to come to you and say "head to punxatawney and get that office up" .  Using rip as we add locations, routers, circuits (because certainly you always want to press for more redundancy and reliability out of your wan..) makes it easier and more reliable.  And if it's all internal, we don't usually need to get too complicated with the protocols, another reason why rip is tried and true.
Here's a quick doc on setting it up, too easy to do. http://www.cisco.com/en/US/tech/tk365/tk554/technologies_tech_note09186a0080094374.shtml
I agree with JP. Static routes can eventually come back to bite you, or the next guy that comes in. RIP is where it is at. You will also want to consider which protocols you want to allow between the routers. Quite possible you only need a few. That allows less opportunity for an exloit.

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now