Generic kernels have no ALTQ support. pfctl barks: No ALTQ support in kernel ALTQ related functions disabled every time it is run when the kernel doesn't have ALTQ support. This is useless noise. The default kernels are not compiled with ALTQ, and the majority of pf users don't use queues anyway. pfctl already fails with an appropriate diagnostic when faced with an altq-related directive in the absence of ALTQ support, so why not move this diagnostic into that specific error scenario? The current behavior just annoys: (a) those who don't care, (b) those who don't know about ALTQ, and (c) those who have to explain to (b) that their firewall has not suddenly been breached by hordes of hackers. Can we please move this diagnostic out of the default code path and into a more appropriate location?
Created attachment 152504 [details] quiesce pfctl's diagnostic about ALTQ until -v is set.
A commit references this bug: Author: gnn Date: Mon Jul 20 23:24:26 UTC 2015 New revision: 285730 URL: https://svnweb.freebsd.org/changeset/base/285730 Log: Only report the lack of ALTQ support if pfctl is using verbose (-v) mode. PR: 194935 Submitted by: Jim Thompson MFC after: 2 weeks Changes: head/sbin/pfctl/pfctl.c
Can this be merged into 10-stable? Thanks.
A commit references this bug: Author: gnn Date: Thu Mar 3 23:25:31 UTC 2016 New revision: 296370 URL: https://svnweb.freebsd.org/changeset/base/296370 Log: MFC 285730 Only report the lack of ALTQ support if pfctl is using verbose (-v) mode. PR: 194935 Submitted by: Jim Thompson Approved by: re (gjb) Changes: _U stable/10/ stable/10/sbin/pfctl/pfctl.c
I believe this can be closed?