Basically why I want them to have the same name is because there are multiple interfaces on this server were clients are connected too, So if I want borrowing (HFSC) to work overall for everybody it has to be assigned under a single parent.
Oh, management of inbound traffic on your uplink is the goal? There aren't any mechanisms to do that at present.
Queueing would not be effective for that purpose anyway, as Henning mentions. One point is that it's impossible to guarantee full use of the inbound pipe; you can't prioritize or drop traffic you never see (because the pipe was saturated and the other end couldn't send it). Another point is that in order to prioritize packets, the queues must be partially full. In order to fill the queues, you need to delay the packets. Since the packets are already here, on the other side of the bottleneck, delaying them serves little purpose.
The only mechanism that's generally effective for inbound traffic is simple rate limiting, where traffic exceeding the limit is dropped. While the ALTQ framework does have that capability, it isn't exposed in PF. It lacks the flexibility that most people would want anyway (rough approximation of sharing, per-host limits, etc).
On Wed, 23 Jul 2003, Trevor Talbot wrote:
On Wednesday, Jul 23, 2003, at 10:21 US/Pacific, Mark Bojara wrote:
I was wondering if its possible to either set up one queue on a single interface to do both incoming and outgoing traffic?
No, not at present.
Or maybe possibly having it on split interface's but assigned to one queue. eg:
pass out on dc1 from <za> to 196.34.165.210 keep state queue opium_01_l
pass in on fxp0 from <za> to 196.34.165.210 keep state queue opium_01_l
A queue must be tied to an interface; it can't be "floating" for use with any flow. One thing you can do is specify queues with the same name on different interfaces (this ties in with the IN tagging I mentioned in the last thread), but this probably isn't what you're after.
