On ott 23 15:47, BERTRAND Joël wrote:
> and altqd runs as expected. Only a few bugs. Don't try to launch
> /etc/rc.d/altqd reload, altqd will take 100% of a CPU. Don't try to stop
> altqd, you will obtain a kernel panic.
Some updates: if altqd.conf has only a queing discipline per each
interface,
On ott 23 15:47, BERTRAND Joël wrote:
> If I remember, altq is applied after npf.
> My /etc/altqd.conf contains :
>
> legendre:[~] > cat /etc/altq.conf
> #tbrconfig
> interface wm0 bandwidth 8M priq
>
> class priq wm0 high_class NULL priority 1
> class priq wm0 low_class NULL priority 0
Rocky Hotas a écrit :
> Hello!
> Consider a NetBSD 9.0 (release) system using both npf and altqd. This
> machine has two NICs and it is a gateway. First NIC is connected to a
> LAN, with multiple hosts, and second NIC is connected to the modem.
> With npf, the following is applied:
>
> map
On ott 23 8:19, Greg Troxel wrote:
> You should be aware that not that many people use altq.
Yes, I was guessing this.
> (I used to use
> it heavily, even adding new queueing disciplines, but that was a very
> long time ago.)
The only important thing is if it's still a good tool for traffic
Rocky Hotas writes:
> Consider a NetBSD 9.0 (release) system using both npf and altqd. This
> machine has two NICs and it is a gateway. First NIC is connected to a
> LAN, with multiple hosts, and second NIC is connected to the modem.
> With npf, the following is applied:
You should be aware
Hello!
Consider a NetBSD 9.0 (release) system using both npf and altqd. This
machine has two NICs and it is a gateway. First NIC is connected to a
LAN, with multiple hosts, and second NIC is connected to the modem.
With npf, the following is applied:
map $if_second_nic dynamic $internal_lan ->
