On Dec 3, 2013, at 8:03 PM, josh Grosse wrote:
On 2013-12-03 13:46, Gabor Berczi wrote:
On Dec 3, 2013, at 7:15 PM, Andy wrote:
queue ack on $extinterface bandwidth 10% priority 6 hfsc
( realtime 10% )
queue ack on $intinterface bandwidth 10% priority 6 hfsc
( realtime 10% )
One queue can't be on two interfaces.
"queue XYZ already exists on interface pppoe0"
Child queues are able to use the same name. Here's an example,
using the new queuing syntax, where the "std" and "pig" queue names
are assigned to queues on different interfaces with different
settings:
/etc/pf.conf.test:4: unknown unit M
/etc/pf.conf.test:5: queue pig has no parent
/etc/pf.conf.test:5: errors in queue definition
/etc/pf.conf.test:6: queue std has no parent
/etc/pf.conf.test:6: errors in queue definition
/etc/pf.conf.test:8: unknown unit M
/etc/pf.conf.test:9: queue local has no parent
/etc/pf.conf.test:9: errors in queue definition
/etc/pf.conf.test:10: queue down has no parent
/etc/pf.conf.test:10: errors in queue definition
/etc/pf.conf.test:11: queue pig has no parent
/etc/pf.conf.test:11: errors in queue definition
/etc/pf.conf.test:12: queue std has no parent
/etc/pf.conf.test:12: errors in queue definition
