I have read lots of helpful pf.conf examples that seem to do reasonably complex queueing and that's fine but I am sure there is a simple way to do what I want. No Google lead pointed at someone doing just the task described below. I did STFA here too
In order to demonstrate how slow a webpage looks to a dial-up user (when the browser is behind my pf firewall and there is a 1536/256Kb/s ADSL line to the world) I'd like to be able to reload the pf ruleset with pf.slow which would limit inbound bandwidth by queueing on the internal interface so that e.g. 192.168.1.200 suddenly was restricted to 33 Kb/s and no other LAN host was affected and .200 could not get any more even if all the others were idle. Doable? Hint? Is RED required? ATM I'm a bit confused about the rich plethora of options in pf's queueing. >From the land "down under": Australia. Do we look <umop apisdn> from up over? Do NOT CC me - I am subscribed to the list. Replies to the sender address will fail except from the list-server.
