<![CDATA[Floating rule, Alias in source or destination for both ways?]]>I have an aliasgroup of clients on LAN that should go into qOthersLow queue.

Can this be done with a single floating rules?
Or two floating rules?
Or a single floating rule plus a LAN interface rule?
Or…

This is my setup but it only works for traffic download (seen from clinet). Client upload is not in qOthersLow queue:

  • Create new floating rule
  • Action: Queue
  • QUICK to apply it at once
  • no interface (then it should count for all interfaces?...)
  • Direction is any (again to bind traffic in both directions)
  • source: alias "lowPrio" with low priority clients on LAN
  • destination: any
  • acc/queue: qACK / qOthersLow

It works for traffic in. That goes into the qOthersLow on WAN
But traffic out does not go into qOthersLow

What should I change to make sure both traffic in and out from/to clients on LAN go into qOthersLow?

BR. Anders

]]>https://forum.netgate.com/topic/54428/floating-rule-alias-in-source-or-destination-for-both-waysRSS for NodeFri, 17 Jul 2026 07:48:18 GMTThu, 21 Mar 2013 14:09:18 GMT60<![CDATA[Reply to Floating rule, Alias in source or destination for both ways? on Thu, 18 Apr 2013 13:05:32 GMT]]>Sorry. First see your answer now.

Thanks a lot. I will experience with a LAN/WAN rule and see if I can get same result.

BR. Anders

]]>https://forum.netgate.com/post/390530https://forum.netgate.com/post/390530Thu, 18 Apr 2013 13:05:32 GMT<![CDATA[Reply to Floating rule, Alias in source or destination for both ways? on Wed, 27 Mar 2013 18:58:55 GMT]]>You can't have a floating rule that checks out on WAN with a private IP source - NAT has already happened, there's no way to match it by IP.

]]>https://forum.netgate.com/post/386861https://forum.netgate.com/post/386861Wed, 27 Mar 2013 18:58:55 GMT