Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 1438 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

Questions About QoS

tscott_16
I need a little clarification on how to properly configure QoS.
I have two interfaces, Internal (eth0) and External (eth1).

What difference does it make which interface a bandwidth pool or throttling rule is bound to?

It seems that you could achieve throttling by setting an upper bandwidth limit in bandwidth pools. What's the difference?


This thread was automatically locked due to age.
Parents
  • +1
    Ok, it finally occurred to me. I was visualizing eth0 and eth1 as each having an internal and external side since they are two physical interfaces. Instead, because they are using NAT masquerading, I needed to think of them as a single unit with just an internal facing side and an external facing side... the sides facing each other are transparent due to NAT masquerading (duh [:)] ).

    --------------------------------------------------------------------------------------

    Outbound Traffic (Upload):
    [LAN]>>>outgoing traffic to internet(inbound to internal interface)>>>[internal interface|NAT Masquerading|External Interface]>>>outgoing traffic to internet(outbound from external interface)>>>[Internet]

    Inbound Traffic (Download):
    [LAN][internal interface|NAT Masquerading|External Interface][Internet]

    Bandwidth pools only affect traffic outbound from the interface.
    Download throttling only affects traffic inbound to the interface.
    Therefore:

    To guarantee bandwidth for download traffic, bind bandwidth pool to the Internal interface.

    To guarantee bandwidth for upload traffic, bind bandwidth pool to the External interface.

    To throttle download traffic, bind throttling rule to the External interface.

    To throttle upload traffic, bind throttling rule to the Internal interface.

    --------------------------------------------------------------------------------------

    I hope this helps to clarify the concept for anyone else having trouble with this.
Reply
  • +1
    Ok, it finally occurred to me. I was visualizing eth0 and eth1 as each having an internal and external side since they are two physical interfaces. Instead, because they are using NAT masquerading, I needed to think of them as a single unit with just an internal facing side and an external facing side... the sides facing each other are transparent due to NAT masquerading (duh [:)] ).

    --------------------------------------------------------------------------------------

    Outbound Traffic (Upload):
    [LAN]>>>outgoing traffic to internet(inbound to internal interface)>>>[internal interface|NAT Masquerading|External Interface]>>>outgoing traffic to internet(outbound from external interface)>>>[Internet]

    Inbound Traffic (Download):
    [LAN][internal interface|NAT Masquerading|External Interface][Internet]

    Bandwidth pools only affect traffic outbound from the interface.
    Download throttling only affects traffic inbound to the interface.
    Therefore:

    To guarantee bandwidth for download traffic, bind bandwidth pool to the Internal interface.

    To guarantee bandwidth for upload traffic, bind bandwidth pool to the External interface.

    To throttle download traffic, bind throttling rule to the External interface.

    To throttle upload traffic, bind throttling rule to the Internal interface.

    --------------------------------------------------------------------------------------

    I hope this helps to clarify the concept for anyone else having trouble with this.
Children
No Data