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

Understanding Traffic Selectors

tscott_16
Someone please explain. When creating a Traffic Selector, if I want to throttle download bandwidth from ftp.example.com to User1 on the LAN, what should I use for Source and Destination in the Traffic Selector?

Does "Source" refer to the origin of the traffic? (The FTP site in this case)

If I also wanted to do the reverse of this and throttle UPLOAD bandwidth from User1 to ftp.example.com, would the Source and Destination be swapped?


This thread was automatically locked due to age.
Parents
  • 0
    In this case, you can't identify the user when the traffic arrives at the External interface - that's only possible after the connection tracker has replaced the IP of "External (Address)" with User1's private IP.

    If there were a unique port or unique IP involved, then I would prefer a Download Throttling rule.  In fact, for many years, we didn't have Download Throttling.  Both approaches do the same thing, but it's easier for people to wrap their heads around it and it makes for "cleaner," easier-to-understand configurations.

    Cheers - Bob
Reply
  • 0
    In this case, you can't identify the user when the traffic arrives at the External interface - that's only possible after the connection tracker has replaced the IP of "External (Address)" with User1's private IP.

    If there were a unique port or unique IP involved, then I would prefer a Download Throttling rule.  In fact, for many years, we didn't have Download Throttling.  Both approaches do the same thing, but it's easier for people to wrap their heads around it and it makes for "cleaner," easier-to-understand configurations.

    Cheers - Bob
Children
No Data