Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 5 subscribers
  • Views 6580 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

Upload shaping - what is wrong in my configuration

MatthiasNeumeister

hi Community!

I have a problem with setting up traffic shaping on my UTM. I want to restrict the bandwidth for my Synology Diskstation, especially the upload bandwidth to my Amazon and Google Drives. I also read a few forum posts that describes how it's done. But still my Diskstation is using more upload bandwidth than I set up on my UTM. Here are my settings and I'll be happy if someone could give me a hint what I did wrong.

 

Here is the definition of the source server (my Diskstation):

Here are the QoS settings:

 

The external interface:

I also put the setting to the internal interface ... just in case:

As mentioned above ... it's doesn't work. [:'(]My Diskstation still uses more bandwidth than it should.
So, what am I doing wrong?



This thread was automatically locked due to age.
Parents
  • 0

    tldr; Create an exception in webfiltering for Synology and the rule would work as expected.

    Long reasoning:

    Qos on Internal Network = Apply QoS to traffic leaving UTM towards Internal network/LAN and similarly

     

    Qos on External Network = Apply QoS to traffic leaving UTM towards External network/Internet so your internal network rule is not doing anything.(I know you are just testing but wanted to clarify)

    As far as your problem, you are applying QoS on external interface when the traffic is originating from Synology. The problem most people run into is when they are using webfiltering at the same time because the traffic reaching the external interface is not coming from synology but coming from http proxy so the QoS rule is not applied. Create an exception for Synology in webfiltering and your rule would work as expected.

    If you have to use webfiltering, then you will have to use application control to throttle google drive and amazon. I generally prefer this method.

Reply
  • 0

    tldr; Create an exception in webfiltering for Synology and the rule would work as expected.

    Long reasoning:

    Qos on Internal Network = Apply QoS to traffic leaving UTM towards Internal network/LAN and similarly

     

    Qos on External Network = Apply QoS to traffic leaving UTM towards External network/Internet so your internal network rule is not doing anything.(I know you are just testing but wanted to clarify)

    As far as your problem, you are applying QoS on external interface when the traffic is originating from Synology. The problem most people run into is when they are using webfiltering at the same time because the traffic reaching the external interface is not coming from synology but coming from http proxy so the QoS rule is not applied. Create an exception for Synology in webfiltering and your rule would work as expected.

    If you have to use webfiltering, then you will have to use application control to throttle google drive and amazon. I generally prefer this method.

Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?

Unfiltered HTML