Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 2 subscribers
  • Views 3266 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

QoS not working with Proxy

Jet
Hi, we are using UTM320 running on version 9.107-33 of firmware. We would like to control the bandwidth consumption of our guest network so I have this config below:

QoS Status
External (WAN) -> Enabled

Traffic Selectors
InboundGuest (Internet IPv4 -> Any -> Guest)
OutboundGuest (Guest -> Any -> Internet IPv4)

Bandwidth Pools
External (WAN) -> Bandwidth:1, Limit:256, Selector: OutboundGuest

Download Throttling
External (WAN) -> Limit:256, Selector: InboundGuest

Without enabling proxy on clients behind the guest network, QoS works as expected, but once I enable proxy (transparent/standard) the QoS does not work.  

Is this an expected behavior or am I just missing something here. Hope anyone on this forum can point me to the right direction. 

Thanks.


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

    I may not be understanding this exchange, but....

    I wouldn't limit upload from the Guest network - prioritize traffic from the Internal network instead.  I don't know if there's an issue with 9.107, but QoS should work with proxied traffic using the InboundGuest selector, for example.

    Cheers - Bob
  • 0 in reply to BAlfson
    Hi Bob, if you're saying that QoS should work either on proxied or unproxied traffic, then could it be that QoS is broken on 9.107?  What I noticed is when rules are placed on the external interface, SourceIP for outgoing traffic and DestinationIP for incoming traffic seems to be the Proxy/UTM.
Reply
  • 0 in reply to BAlfson
    Hi Bob, if you're saying that QoS should work either on proxied or unproxied traffic, then could it be that QoS is broken on 9.107?  What I noticed is when rules are placed on the external interface, SourceIP for outgoing traffic and DestinationIP for incoming traffic seems to be the Proxy/UTM.
Children
No Data