Update on altq and interface groups

Hi list, I know this question has been asked before, but I'm after an up-to-date answer, or at least a confirmation. Has support for interface groups been implemented for altq? By that, I mean the possibility to use an interface group name with baltq on GROUPb to set up similar queues for each

Re: Update on altq and interface groups

On Mon, Jul 5, 2010 at 8:50 AM, Olivier Mehani sht...@ssji.net wrote: I know this question has been asked before, but I'm after an up-to-date answer, or at least a confirmation. Has support for interface groups been implemented for altq? No.

Re: pf, altq and interface groups

* Daniel Melameth dan...@melameth.com [2010-05-22 03:58]: I've considered migrating my macro-based interface names to interface groups, but, it appears, altq does not grok interface groups--and pfctl spits back a pfctl: SIOCGIFMTU: Device not configured when I try. Am I missing something

pf, altq and interface groups

I've considered migrating my macro-based interface names to interface groups, but, it appears, altq does not grok interface groups--and pfctl spits back a pfctl: SIOCGIFMTU: Device not configured when I try. Am I missing something here? pf.conf's BNF, it appears, says I'm not...

altq and interface groups

Hi, setup: 4.2 with tun0 being a pppoe(8) int and tun1 being a ssh-vpn over tun0. altq is running on tun0. I know that altq doesn't support interface groups (and that support is not planned (see http://marc.info/?l=openbsd-miscm=112431574118264w=2)) but is there a way around this? Currently altq