Re: queueing TOS'ed packet

On Sun, Jan 31, 2010 at 8:26 PM, Stuart Henderson <[email protected]> wrote:
> On 2010/01/31 16:11, Agung T. Apriyanto wrote:
>> pass out quick log on $client_if proto tcp from any to <client> tos
>> 0x30 no state queue q_tos
>
> There's an implicit "flags s/sa" so this rule only matches SYN packets.
>

i tried this
pass out quick log on $client_if proto tcp from any to <client> flags
any tos 0x30 queue q_tos

still unable to queue marked tos

>> no state used because after searching archive i found some suggest to use it.
>
> This is usually from people who haven't worked out how to assign
> packets to queues.
>
> http://archives.neohapsis.com/archives/openbsd/2009-11/0127.html
>
>

as you see in my conf i've already using altq method as you described,
but still, no state or keep state won't make any difference.

even when i remove queue, nothing showed in pflog0, when tcpdump interface
a lot of packets with tos 0x30 showed

# tcpdump -vni vlan100 | grep 'tos 0x30'
tcpdump: listening on vlan100, link-type EN10MB
21:02:22.299867 112.78.131.2.80 > 192.168.101.100.1720: P
759:1137(378) ack 2269 win 10153 (DF) [tos 0x30] (ttl 63, id 41942,
len 418)
21:02:22.370105 112.78.131.2.80 > 192.168.101.100.1708: P 380:758(378)
ack 1544 win 8657 (DF) [tos 0x30] (ttl 63, id 35548, len 418)
21:02:22.377301 112.78.131.2.80 > 192.168.101.100.1707: P 380:758(378)
ack 1537 win 8613 (DF) [tos 0x30] (ttl 63, id 60730, len 418)
21:02:22.383958 112.78.131.2.80 > 192.168.101.100.1718: P
1138:1516(378) ack 3003 win 11760 (DF) [tos 0x30] (ttl 63, id 51651,
len 418)
21:02:22.545928 202.169.62.8.80 > 192.168.101.100.1747: P 1:376(375)
ack 697 win 6960 (DF) [tos 0x30] (ttl 63, id 44641, len 415)
21:02:22.571802 202.169.62.8.80 > 192.168.101.100.1746: P 1:377(376)
ack 698 win 6970 (DF) [tos 0x30] (ttl 63, id 43445, len 416)
21:02:22.572557 202.169.62.8.80 > 192.168.101.100.1748: P 1:377(376)
ack 698 win 6970 (DF) [tos 0x30] (ttl 63, id 57262, len 416)
21:02:22.587260 202.169.62.8.80 > 192.168.101.100.1749: P 1:376(375)
ack 697 win 6960 (DF) [tos 0x30] (ttl 63, id 7419, len 415)
21:02:22.589574 202.169.62.8.80 > 192.168.101.100.1750: P 1:377(376)
ack 707 win 7060 (DF) [tos 0x30] (ttl 63, id 5244, len 416)
21:02:22.609438 202.169.62.8.80 > 192.168.101.100.1751: P 1:376(375)
ack 705 win 7040 (DF) [tos 0x30] (ttl 63, id 65124, len 415)


thanks & regards,
-Agung