AW: route-to with altq problem

[Spenst, Aleksej]

Sorry for spam again, but I have already figured it out.

instead of:

nat on lo0 proto tcp tag PRIQ5 -> ($ext_if)
pass out on lo0 route-to $ext_if tagged PRIQ5 keep state
pass out on $ext_if tagged PRIQ5 queue q5 keep state

it should be:

nat on lo0 proto tcp tag PRIQ5 -> ($ext_if)
pass out on lo0 route-to $ext_if tagged PRIQ5 keep state queue q5

Where the queue q5 belongs to $ext_if and not to lo0, which was not very clear to me before...
 

>-----Ursprüngliche Nachricht-----
>Von: owner-freebsd-pf at freebsd.org 
>[mailto:owner-freebsd-pf at freebsd.org] Im Auftrag von Spenst, Aleksej
>Gesendet: Mittwoch, 16. Juni 2010 18:29
>An: 'freebsd-pf at freebsd.org'
>Betreff: route-to with altq problem
>
> 
>Hi all,
>
>I have the problem that after redirecting the packets with 
>'route-to' keyword to the external interface $ext_if, the 
>packets are not queued at $ext_if but directly go out. The 
>problem is that I have configured queues (ALTQ) at $ext_if to 
>make prioritization of traffic, but queues are ignored as 
>packets are not queued.
>
>Below is my pf.conf without queue configuration, which is not 
>relevant here.
>The last rule is never matched!!!
>
>--- pf.conf ----
>nat on lo0 proto tcp tag PRIQ5 -> ($ext_if) pass out on lo0 
>route-to $ext_if tagged PRIQ5 keep state pass out on $ext_if 
>tagged PRIQ5 queue q5 keep state
>----------------
>
>Thanks a lot for any suggestion about how to force packets to 
>go to queues at $ext_if after 'nat'.
>
>Aleksej.
>
>
>_______________________________________________
>freebsd-pf at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-pf
>To unsubscribe, send any mail to "freebsd-pf-unsubscribe at freebsd.org"
>