Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 811 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Performance Problems / Policy Route Proxied Traffic to a second WAN connection

bayst
Hi,

we got two internet connections (t1 with standard gateway and dsl).

As described in the 

KB article AKB000249 (https://support.astaro.com/support/index.php/Policy_Route_Proxied_Traffic_to_a_Second_WAN_Connection)

we configured our Astaro V8 to send all proxied traffic to our DSL Router, which is connected to a dedicated Interface (please take a look at the attachment).

The whole thing works, but the surfing experience is more than worse. Websites with lot of multimedia content need many, many seconds to be loaded completely. If there is only one request (i.e. video streams), the download performance matches the performance of the dsl line.

If we disable the policy routing and the snat rule, everything works like a charm. But we don't want to use our T1 line for websurfing...

Did we configured the policy route and snat rule correctly? (Attachment)

Thanks in advance!


This thread was automatically locked due to age.
Parents
  • 0
    Hi, bayst, and welcome back to the User BB!

    That looks correct, so I'll guess that you have some other issue.  One trap that many fall into is binding a network/host definition to a specific interface.  I assume that you are using the Proxy in a non-transparent mode - correct?

    Since V7.4, the preferred solution is Uplink Balancing as that would allow failover to the T1 if the DLS connection died.  There's an active thread on that right now: https://community.sophos.com/products/unified-threat-management/astaroorg/f/55/t/44831

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    Hi, bayst, and welcome back to the User BB!

    That looks correct, so I'll guess that you have some other issue.  One trap that many fall into is binding a network/host definition to a specific interface.  I assume that you are using the Proxy in a non-transparent mode - correct?

    Since V7.4, the preferred solution is Uplink Balancing as that would allow failover to the T1 if the DLS connection died.  There's an active thread on that right now: https://community.sophos.com/products/unified-threat-management/astaroorg/f/55/t/44831

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    thanks for the speedy reply [[;)]]

    We do not bind any host/network to a specific interface.

    Proxy: On the "Global HTTP Proxy Settings Tab" the proxy operation mode is set to "transparent".
    Also we use lots of proxy profiles with different operation modes (transparent, standard, ad sso)...

    Before implementing the routing an nat solution I considered, if uplink balacing would be the best for our environment [[;)]] I'll give it a try...