One has to ask, is the direct privately addressed connection necessary
at all? There is no real security benefit if data can be routed via the
internet anyway.
Since redundancy appears to be a requirement, perhaps both sites having
a 2nd internet connection would be a cleaner solution. This combined
with an encrypted vpn for secure data transfer would give you the
security and availability required.
If both internet connections terminated on the same router at each end,
failing over if one link died would be trivial to set up. The vpn would
be more complex and require some expertise.
cheers,
Ben
SysAdm wrote:
> "lenny" <> wrote in message
> news: ups.com...
>
>>Hi
>>
>>I'm a programmer with very limited net design / admin knowledge, so
>>forgive me if this question sounds naive.
>>
>>We are a small company (10 people) with 2 T1 connections. One T1 gives
>>us public internet access through a Cisco 1700 router (there's a
>>Watchguard Firebox behind the router for security). The second
>>connection is exclusively for access to special purpose data from a
>>single data vendor. I believe this line puts us on the vendors
>>intranet, or it may be a point to point line) It's not on the public
>>internet. The connection on this second line is via a Cisco 1600 doing
>>the job of a boundary router (lan to wan address traslation only). Both
>>T1 connections go onto the our company ethernet (one segment for
>>everyone).
>>
>>The private data source can give us data over the public internet when
>>their intranet line fails (which it does occasionally). We fail over to
>>the data vendors public internet in a pretty crude way: Each user of
>>the data vendors intranet connection has a persistent route to the
>>intranet set in their (Windows XP) computer. When the intranet goes
>>down, we have these users run a batch file that executes the Windows
>>"route" utility and substitutes an ip address of our private data
>>vendor that's available via the public internet. When the intranet T1
>>line comes back, the users execute a second batch file that replaces
>>the persistent route in their computers back to the intranet T1.
>>
>>I'm wondering whether (and how) I can remove all persistent routes in
>>the users computers and substitute some settings in the two cisco
>>routers so the failover to the public internet and back to the intranet
>>happens automagically as the intranet T1 goes down and returns? Is this
>>a job that's doable by a programmer or should I look for a by-the-hour
>>comms expert to do it?
>>
>>Thanks in advance for your advice.
>>
>>Lenny
>
>
> depending on how "smart" you want this setup it could either be done with
> HSRP and interface tracking (that would give you the failover, but wouldnt
> give you dynamic routing), or alternatively combine HSRP and a dynamic
> routing protocol to give you full manipulation of your traffic path.
>
> SysAdm
>
>
|