Either I don't catch how use it, either it does not work as intended. So, I click on "Traffic Shaper", on the "by Interface" tab then click on "Enable this discipline" (the queue name that shows up is "wan" by the way) and enter some BW limit then I click on "Save" then "Apply".
To my surprise nothing has been changed for the interface "WAN" but a new icon with no name appears on the left of the page, just on the top of "WAN". Whenever I click this icon I get an error => Queue not found :)
Also, how to add a sub-queue? The button "Add new queue" does not seems to do something... :-\
Same here, that is the most important feature i need, now i will switch to pfsense.
OPNSense is nice, but not functional.
Trying to cope with a disappearing open source repository named pfsense-tools.git a little over 14 months ago is still showing how bad the move really was for the open source community. We wish you luck on your endeavour. We only do what we can given the circumstances and the willingness of users to help us get better. Thank you.
Well, perfectly normal for something "young" to have angles to be polished. It will improve over time, thank you for your good work and continuous efforts :)
Why not using the traffic shaper of monowall? It works
Gesendet von iPhone mit Tapatalk
Just trying to get through the "Dedicated Links" wizard now comes up with:
QuoteYou have less interfaces than number of connections!
Was previously working (well, I could get through the wizard at least) before build 15.1.9.
I'm assuming WAN count "1" works, but "2" doesn't. The code checks which interfaces have gateways (IPv4 or v6) or is of the following type: dhcp, pppoe, pptp, l2tp, ppp, ovpn, gif, gre.
Maybe your setup changed? Maybe an interface setting got lost? We haven't touched the wizard in the last 3 months. Any help to debug this is appreciated. :)
Just took the time to update to the latest release (15.1.9.1), now it works wonderfully well but I did not test it with 15.1.9... according to the changelog for the 15.1.9.1 release it should work as well under 15.1.9 :-)
Unfortunately OPNsense 15.1.9.1-amd64 is still showing the same issue for me. I'll try a fresh install of 15.1.9 later on the same configuration to see if that helps.
Some further information about my set-up:
- Generation 1 VM in Hyper V 2012 R2
- 1024MB RAM (Static)
- 1 vCPU
- 2x vNIC (Both VLAN tagged within the Hyper-V configuration)
Originally I installed and configured with a single vNIC with VLAN support but I found then that I was seeing errors in the logs for features not being supported, so I reconfigured to two vNIC's & factory reset the OS.
Right, still not working on a reinstall.
Seems to be Hyper-V / VM related though? https://forum.pfsense.org/index.php?topic=83475.0
Aergan, thanks for narrowing that down. `hn' is now in the list, will be in 15.1.9.2 (this week most likely):
https://github.com/opnsense/core/commit/72bcc260e442865965bb0b09dd2bf7de3bced32e
Many thanks, seems to be working again now :)