Bug? Traffic Shaper Wizard not working on SG-1000
-
See above. The NICs on the SG-1000 do not currently support ALTQ. It does not matter what shaper type you choose in that area, it's all ALTQ.
Limiters should work OK. (And limiters+NAT works fine on 2.4) No CODEL there but you can setup priority queues with some manual work.
-
Perfect. Thank you jimp!!
-
Thanks for the info jimp, might be good to have the interface tell the admin that altq isn't supported (or something of an indicator) but that's a 'nice' to have :) To help with bufferbloat issues I like to enable codel FQ or similar, if possible. I also have found great results from setting up queues for VOIP as my wife and I both work from home using VOIP as our primary method of communication and prioritizing VOIP had a far better result for quality and reliability than I had anticipated.
Having a way to address buffer bloat seems to really improve general use of anything internet - do you know if there's a way to somehow deal with this on the SG-1000?
Thanks!
-
do you know if there's a way to somehow deal with this on the SG-1000?
See my first reply on this thread for a workaround to use ALTQ.
-
This thread helped - thanks - was banging my head against the wall.
+1 for getting ALTQ working on the SG-1000 Nics. My use case:
The SG-1000 is (hopefully) going to be used at our home offices which each include a VOIP phone registering with a SIP server running on a public IP. Need QOS so that the voip phones don't have crappy performance just because junior is downloading a Torrent, etc.
If we need to purchase the SG-2220s it will be a much tougher sell.
Cheers,
-
I'm pushing some changes that will make the ALTQ situation more obvious ( See https://redmine.pfsense.org/issues/7032 )
I don't know if/when there will be support for ALTQ in the cpsw driver.
As I mentioned earlier in the threads, limiters can be used for shaping if it's necessary.
-
isn't fq_codel part of freebsd 11 could that be enabled on limiters to at least help with buffer bloat ?
-
Thank you for this thread!
I've been banging my head against a wall as well trying to get traffic shaping working as well. A nice little box that can traffic shape is the main reason I bought the SG-1000.
The intended use is a house with six users sharing a horrible ADSL connection (syncs at 0.25/5.0Mbps but actual speed tests put it at about 0.2/1.5Mbps). All it takes is one person sharing a "short video" on snapchat or whatever to take down the whole connection for everyone else.
jimp: Could you please give some pointers or links as to how to use VLANs as a solution? I've been trying to implement it on my own but with no success.
I imagine the solution is something a long the lines of:
WAN <-> WAN_ALTQ(VLAN) <-> LAN_ALTQ(VLAN) <-> LAN
Any help would be appreciated.
Cheers
-
Hi,
I've been trying to get traffic shaping working on the SG-1000 since finding out that the NIC drivers do not support ALTQ. It's been mentioned on these forums that this can be worked around using VLANs (for example: https://forum.pfsense.org/index.php?topic=122798.0). I've managed to get the following setup running:
SG-1000 ISP <--PPPoE--> | WAN LAN | <--VLAN--> Switch <--> LANThe PPPoE and the LAN_VLAN adaptors show up in the Traffic Shaper Interfaces list and I am able to go through the traffic_shaper_wizard_multi_all.xml wizard no problems. However when the rules go to be loaded this error message is given:
There were error(s) loading the rules: pfctl: cpsw1_vlan10: driver does not support altq - The line in question reads [0]To see whether this was port specific or not, I then reconfigured my network in the following way:
SG-1000 Internet <--> Switch <--VLAN--> | WAN LAN | <--VLAN--> Switch <--> LANBut I get a near identical error message:
There were error(s) loading the rules: pfctl: cpsw0_vlan20: driver does not support altq - The line in question reads [0]I'm guessing that the rules for cpws0 are just executed first, hence the different message.
Is this a bug? Or some subtle setting I'm missing when using VLANs? Or contrary to some of the forum posts do VLANs just not support ALTQ?
I'm currently running: 2.4.0.b.20170129.1734
Cheers
EDIT:
Just been browsing the 2.4 tickets and found a ticket with similar symptoms:
https://redmine.pfsense.org/issues/7066 -
https://forum.pfsense.org/index.php?topic=122798.0
-
Well yes … I link to that thread in my post ::)
That very thread (and others) suggest you can use VLANs to as a workaround which is what i am doing. But it still does not work. That fact that you can select the interfaces on the Traffic Shaper page is also odd as it is not meant to display unsupported interfaces.
-
So why are you starting a new duplicate thread? Won't get anything fixed any sooner.
-
Well the earlier thread dealt with limitations of the cpsw NIC driver. This problem is with the vlan driver. It seemed logical to separate the two.
-
Merged same topic.
-
Hi,
I've been trying to get traffic shaping working on the SG-1000 since finding out that the NIC drivers do not support ALTQ. It's been mentioned on these forums that this can be worked around using VLANs (for example: https://forum.pfsense.org/index.php?topic=122798.0). I've managed to get the following setup running:
SG-1000 ISP <--PPPoE--> | WAN LAN | <--VLAN--> Switch <--> LANThe PPPoE and the LAN_VLAN adaptors show up in the Traffic Shaper Interfaces list and I am able to go through the traffic_shaper_wizard_multi_all.xml wizard no problems. However when the rules go to be loaded this error message is given:
There were error(s) loading the rules: pfctl: cpsw1_vlan10: driver does not support altq - The line in question reads [0]To see whether this was port specific or not, I then reconfigured my network in the following way:
SG-1000 Internet <--> Switch <--VLAN--> | WAN LAN | <--VLAN--> Switch <--> LANBut I get a near identical error message:
There were error(s) loading the rules: pfctl: cpsw0_vlan20: driver does not support altq - The line in question reads [0]I'm guessing that the rules for cpws0 are just executed first, hence the different message.
Is this a bug? Or some subtle setting I'm missing when using VLANs? Or contrary to some of the forum posts do VLANs just not support ALTQ?
I'm currently running: 2.4.0.b.20170129.1734
Cheers
EDIT:
Just been browsing the 2.4 tickets and found a ticket with similar symptoms:
https://redmine.pfsense.org/issues/7066The ESXi driver was having the same issue and was fixed by changing multiqueue support that is baked in to FreeBSD 11 apparently.
The SG-4860 VLAN also doesn't work with the shaper due to this altq incompatibility.
I'm surprised Netgate/Rubicon whatever they're called these days hasn't prioritised getting this right on their own hardware!?
-
The ESXi driver was having the same issue and was fixed by changing multiqueue support that is baked in to FreeBSD 11 apparently.
The SG-4860 VLAN also doesn't work with the shaper due to this altq incompatibility.
I'm surprised Netgate/Rubicon whatever they're called these days hasn't prioritised getting this right on their own hardware!?
Different issue I think. VMXNET3 nics in ESXi always had support in ALTQ. The nic driver in the SG1000 doesn't have a driver that supports ALTQ yet. Refer to the second post in this thread.
The cpsw NICs in the SG-1000 do not support ALTQ shaping currently. No ETA on that.
You could use VLAN tagged interfaces, as those do support ALTQ, but it's a little more to setup on the firewall and switch.
-
Missing skills i would suggest, but i am biased :).
-
no pun intended… sure :)
Jimp just brought this to my attention today.
Please, let's open an issue to properly keep all this information.
Thanks.
-
Please, let's open an issue to properly keep all this information.
Thanks.
Done: https://redmine.pfsense.org/issues/7199
-
no pun intended… sure :)
Jimp just brought this to my attention today.
Please, let's open an issue to properly keep all this information.
Thanks.
Nothing personal loos but just above your paygrade, really!
Keep until the next one.
