On Wed, Jul 23, 2003 at 05:35:05PM -0700, Trevor Talbot wrote:
On Wednesday, Jul 23, 2003, at 16:28 US/Pacific, matthew j weaver wrote:
On Wed, Jul 23, 2003 at 03:18:05PM -0700, Trevor Talbot wrote:
simple rate limiting, where traffic exceeding the limit is dropped.
While the ALTQ
Hello,
I was wondering if its possible to either set up one queue on a single
interface to do both incoming and outgoing traffic? (probably not
possible)
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
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:
Hello Trevor,
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.
Regards
Mark
On Wed, 23 Jul 2003, Trevor
On Wed, Jul 23, 2003 at 11:44:31AM -0700, 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.
and never will
On Wednesday, Jul 23, 2003, at 13:04 US/Pacific, Mark Bojara wrote:
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
On Wednesday, Jul 23, 2003, at 16:28 US/Pacific, matthew j weaver wrote:
On Wed, Jul 23, 2003 at 03:18:05PM -0700, Trevor Talbot wrote:
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
