The tricky part that I can’t seem to figure out is that I need outbound 80
and 443 for *some* sites over the Metro-E connection.  The goal would be to
use the Metro-E connection for SaaS apps we subscribe to and then use the T1
for things like Google, news sites, etc. all from the same workstation.

 - Andy O.

>-----Original Message-----
>From: Kurt Buff [mailto:[email protected]]
>Sent: Wednesday, April 01, 2009 3:27 PM
>To: NT System Admin Issues
>Subject: Re: OT: Bandwidth Splitting?
>
>Perfect case for a squid box. Just make the default gateway on the
>squid box point to the router for the T1. Then you just have to
>configure the proxy settings on the clients to use the squid box, and
>you can then deny all outbound port 80 for the Metro-E link.
>
>That is, assuming that your network is set up to take advantage of
>that. I have a subnet between my core switch and my firewalls that is
>relatively unpopulated, except for my squid box and my mail gateway,
>so I can do just that sort of thing.
>
>Kurt
>
>On Wed, Apr 1, 2009 at 13:57, Andy Ognenoff <[email protected]> wrote:
>> I'm not really sure how to explain what I want to do, what tech to use,
>or
>> if it's even possible so here it goes:
>>
>> I have 2 Internet connections, a standard T1 and a Metro-E fiber
>connection.
>> I'm not interested in traditional load balancing or failover, I just want
>to
>> use the Metro-E connection for critical business web sites and web apps
>and
>> all my servers would use that as well, and then use the T1 for things
>like
>> non-critical business stuff, general surfing, etc...
>>
>> Is it possible to do this, where an individual client would be using 2
>> different gateways to the Internet based on the site or service they were
>> trying to access?
>>
>>  - Andy O.
>
>~ Finally, powerful endpoint security that ISN'T a resource hog! ~
>~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to