I'm seeing something very strange when I try to debug queues on
pf. I'm simply trying to view queue activity on the net using either:
# pfctl -vvsq
or
# systat queue
I'm trying to assign all udp traffic from my iPad to a priority queue
with a ruleset in pf like this:
...
match out on $ext_if inet proto { udp, icmp } \
set queue ob_default set prio 3
match out on $ext_if inet proto tcp \
set queue (ob_default, ob_priorty) set prio (3, 4)
match out on $ext_if inet proto { tcp, udp } to any port 53 \
set queue ob_priority set prio 5
match out on $ext_if inet proto udp from <ipads-and-iphones> \
set queue ob_priority set prio 5
When I start a video chat on the iPad to a friend I'm expecting
the packet and byte counts in the ob_priority queue shown with
# systat queue
to increase. But I didn't initially see that. When I first looked, the
packets in the default queue were increasing and that queue showed A
little less than 2Mbit/s of traffic. I found that consistant with my
video chat being carried on the ob_default queue. No amount of playing
with queueing in my ruleset seemed to fix that, including setting the
default queue to ob_priority and deleting any assignments to the
ob_default queue. In a fit of pique, I rebooted the box against the
"everything goes in the priority queue" config. After that I noticed
that now everything went into the priority queue. And nothing would
change that. I put the box back to the configuration that I thought
would work with both priority and default queues and it appears to
work now.
My question is:
Is there some way besides rebooting the machine to get pf to
recognize a change in the queuing and queueing assignment setup
in /etc/pf.conf without rebooting the box?
I've tried:
# pfctl -Frules -f/etc/pf.conf
# pfctl -Fstate
# pfctl -Fall -f /etc/pf.conf
# shutdown -r now
and the only thing that updated the queueing was the reboot.
Thanks for any help
-- Chris
