Bug #8954
closed
hn0: driver does not support altq
0%
Description
hyper-v 2016
gen1 and gen2
Files
| pfsense.2.4.4-hyper-v-altq-bug-feedback.PNG (60.5 KB) pfsense.2.4.4-hyper-v-altq-bug-feedback.PNG | |||
| 8954-feedback-system-tunable-set.PNG (65.7 KB) 8954-feedback-system-tunable-set.PNG | force to 1 | ||
| 8954-feedback-system-tunable-set-sysctl-output-0.PNG (5.99 KB) 8954-feedback-system-tunable-set-sysctl-output-0.PNG | output still 0, traffic shaper wizard still errors |
Updated by Arthur Hirstein over 5 years ago
Das gleiche Problem mit Hyper-V 2012, gen1
Updated by Anonymous over 5 years ago
- Target version changed from 2.4.4-GS to 2.4.4-p1
Updated by Gustavo Mello over 5 years ago
Dmitry Ivanov wrote:
hyper-v 2016
gen1 and gen2
same here, using windows server 2016 on pfsense 2.4.4
Updated by Jon Gav over 5 years ago
Windows 10 Pro w/latest updates + Hyper-V.
2.4.3 was/is flawless. Upgraded to 2.4.4 and got this error and can't use Queue Status either
Updated by Dave Pone over 5 years ago
Having exactly the same issue. Fresh install of pfSense under Hyper-V on 2012R2.
Updated by Nadav Rak over 5 years ago
This bug was also before, see isue #7869
Updated by Jon Gav over 5 years ago
hyper-v 2016
gen1 and gen2
Issue persistent in 2.4.5.development as well
Updated by Renato Botelho over 5 years ago
Jon Gav wrote:
hyper-v 2016
gen1 and gen2Issue persistent in 2.4.5.development as well
can you please run following command on your system and let me know the output?
sysctl -a | grep use_if_start
Updated by Renato Botelho over 5 years ago
- Status changed from New to In Progress
Updated by Ben T over 5 years ago
On psense 2.4.4 running as vm gen2 on windows 10 build 1803 Hyper-V, the output of the command: (screenshot also attached)
sysctl -a | grep use_if_start
results in:
hw.hn.use_if_start: 0
edit: checked in 2.4.3, the result of the same command is: hw.hn.use_if_start: 1
Thanks @Renato Botelho for looking into this bug! It appears you are already narrowing in on the problem!
Updated by Renato Botelho over 5 years ago
Ben T wrote:
On psense 2.4.4 running as vm gen2 on windows 10 build 1803 Hyper-V, the output of the command: (screenshot also attached)
sysctl -a | grep use_if_start
results in:hw.hn.use_if_start: 0
edit: checked in 2.4.3, the result of the same command is: hw.hn.use_if_start: 1
Thanks @Renato Botelho for looking into this bug! It appears you are already narrowing in on the problem!
Please try to set it to 1 on System -> Advanced -> System Tunables and test to see if it helps
Updated by Ben T over 5 years ago
- File 8954-feedback-system-tunable-set.PNG 8954-feedback-system-tunable-set.PNG added
- File 8954-feedback-system-tunable-set-sysctl-output-0.PNG 8954-feedback-system-tunable-set-sysctl-output-0.PNG added
I've created a new "System Tunable" with : hw.hn.use_if_start with value of 1 Then rebooted the VM.
Output of sysctl -a | grep use_if_start still results in hw.hn.use_if_start: 0
The error still appears when enabling the traffic shaper, or after a reboot with the traffic shaper enabled:
"There were error(s) loading the rules: pfctl: hn0: driver does not support altq - The line in question reads [0]: "
For anyone else troubleshooting this issue, you can test repro the original issue by installing pfsense 2.4.4 in a Hyper-V vm, with synthetic nics. Then in pfsense goto "Firewall" > Traffic Shaper -> Wizards -> traffic_shaper_wizard_multi_all.xml > then just click next a bunch of times, the filter reload page will appear and show the error at the bottom of the output.
Updated by Renato Botelho over 5 years ago
- Status changed from In Progress to Feedback
I pushed a fix on FreeBSD-src. Please try next round of 2.4.5 snapshots
Updated by Ben T over 5 years ago
The fix Renato pushed yesterday has fixed the issue! Traffic shaper starts up no problem now.
Looks like the first build with the fix is this one:
pfSense-CE-2.4.5-DEVELOPMENT-amd64-20181102-0213.iso
In this fixed build, the output of: sysctl -a |grep use_if_start results in:
hw.hn.use_if_start: 1
Thanks so much Renato for getting this addressed!
https://github.com/pfsense/FreeBSD-src/commit/82fb779f75798e0b3f8f048d7035c813edac52fc
Updated by Renato Botelho over 5 years ago
- Status changed from Feedback to Resolved
Updated by Ben T over 5 years ago
In case anyone has already upgraded to 2.4.4 and wants to workaround the issue without waiting for a patch or downgrading back to 2.4.3, you can fix it via Loader Tunables. (see: https://www.netgate.com/docs/pfsense/book/config/advanced-tunables.html)
This is VERY dangerous for non-experienced users, proceed at your own risk! This is only if you are desperate to fix this problem in released version 2.4.4!
Goto the web interface of your 2.4.4 pfsense, click "Diagnostics" -> "Edit File"
For path, type: /boot/loader.conf
Click "Load"
Add this as a new line to the bottom of the file contents:
hw.hn.vf_transparent="0"
Click "Save"
Then reboot the PFSense, ALTQ will now work.
Thanks Renato for finding the root cause of this problem and getting it fixed upstream!
Updated by Greg M almost 5 years ago
Hello!
This one is back in 2.5.0 snapshots.
Updated by Greg M almost 5 years ago
Restored to 2.4.4-p3 and output is: hw.hn.use_if_start: 1
Clean install 2.5.0 snapshot: hw.hn.use_if_start: 0
Updated by Jim Pingle almost 5 years ago
Please open a new issue with specific error messages and reference this one there.
Updated by Renato Botelho about 3 years ago
- Target version changed from 2.4.4-p1 to 2.5.0
Moving target to 2.5.0 since it regressed
Updated by Renato Botelho about 3 years ago
- Status changed from Resolved to Feedback
I've enabled hn_altq_enable option on default config. It was missing
I've also added needed loader tuning to installer to be configured by default on new installations.
It should be enough to cover this one
Updated by Renato Botelho about 3 years ago
- Status changed from Feedback to Resolved