HFSC errors, dedicated wizard, defaults.



  • error:

    There were error(s) loading the rules: /tmp/rules.debug:46: errors in queue definition - The line in question reads [46]: queue qInternet on em1 bandwidth 48000Kb hfsc ( ecn , linkshare 48000Kb , upperlimit 48000Kb ) { qACK, qP2P, qGames, qOthersHigh, qOthersLow }
    

    log:

    grep -A2 -e '^ *queue' -e 'altq' /tmp/rules.debug
     altq on em0 hfsc bandwidth 18000Kb queue {  qInternet  }
     queue qInternet on em0 bandwidth 18000Kb hfsc (  ecn  , linkshare 18000Kb  , upperlimit 18000Kb  )  {  qACK,  qOthersDefault,  qP2P,  qGames,  qOthersHigh,  qOthersLow  }
     queue qACK on em0 bandwidth 17% hfsc (  ecn  , linkshare 17%  )
     queue qOthersDefault on em0 bandwidth 8.5% hfsc (  ecn  )
     queue qP2P on em0 bandwidth 15% hfsc (  ecn  , default  , linkshare 15%  , upperlimit 15%  )
     queue qGames on em0 bandwidth 17% hfsc (  ecn  , linkshare 17%  )
     queue qOthersHigh on em0 bandwidth 8.5% hfsc (  ecn  , linkshare 8.5%  )
     queue qOthersLow on em0 bandwidth 4.25% hfsc (  ecn  , linkshare 4.25%  )
    
     altq on em1 hfsc queue {  qInternet  }
     queue qInternet on em1 bandwidth 48000Kb hfsc (  ecn  , linkshare 48000Kb  , upperlimit 48000Kb  )  {  qACK,  qP2P,  qGames,  qOthersHigh,  qOthersLow  }
     queue qACK on em1 bandwidth 17% hfsc (  ecn  , linkshare 17%  )
     queue qP2P on em1 bandwidth 15% qlimit 500 hfsc (  ecn  , default  , linkshare 15%  , upperlimit 15%  )
     queue qGames on em1 bandwidth 17% hfsc (  ecn  , linkshare 17%  )
     queue qOthersHigh on em1 bandwidth 8.5% hfsc (  ecn  , linkshare 8.5%  )
     queue qOthersLow on em1 bandwidth 4.25% hfsc (  ecn  , linkshare 4.25%  )
    

    how to reproduce:

    1. so I installed the 2.3 beta pfSense-memstick-2.3-BETA-amd64-latest and updated from the dashboard.

    2. I then went to Firewall \ Traffic shaper \ Wizards

    3. next Dedicated Links wizard

    page1: 1 wan interface
    **page2:**both local and wan interface hfsc upload set to 18000 Kbit/s download set to 48000 Kbit/s, CLICK NEXT
    **page3:**left Voip unchecked, CLICK NEXT
    **page4:**left Penalty Box unchecked, CLICK NEXT
    **page5:**check "Lower priority of Peer-to-Peer traffic" checkbox, check p2pCatchAll checkbox and set bandwidth to 15%, CLICK NEXT
    **page6:**check "Prioritize network gaming traffic" check BattleNET & World of Warcraft checkboxes, CLICK NEXT
    **page7:**check Other networking protocols for Raise or lower other Applications, set Web HTTP to Higher priority, CLICK NEXT
    CLICK FINISH
    after rules reload, reboot pfsense and you will see the errors.

    This was done right after a clean install with more or less default settings without adjusting anything after running the wizard. Also I had this issue on 2.2.6, before that I was running 2.1.5 so I am not sure where the issue was first introduced.

    My friend is running 2.2.6 and said they do not have the issue, but they installed from upgrade rather than a clean install… so I wonder if that might be related, I might try a clean 2.2 install and then update to something later, rather than clean installing the latest. (however I am not sure this would solve the issue either, I will report back after trying it.)



  • Just clean installed 2.2.4 and followed the same procedure, no errors after reboot.

    EDIT, so the 2.2.4 install did not have errors, but after updating 2.2.4 to the 2.3 snapshot using the update files, it still had the issue (does not appear to matter if you clean install or update)

    I am not sure what else to test or report, if you need any more information from me to track this down I would be happy to help. for the moment I will stay on 2.2.4 or older, because I use the hfsc traffic shaper.



  • I really like the new 2.3 Interface, and it seems to be performing great too. So I tried the CBQ instead of the HFSC, and it didn't give me any errors like the HFSC was.



  • This is the root issue.
    https://redmine.pfsense.org/issues/5721



  • @cmb:

    This is the root issue.
    https://redmine.pfsense.org/issues/5721

    Comes down to bad hardware/drivers?



  • @Harvy66:

    Comes down to bad hardware/drivers?

    Doesn't necessarily appear to, affects a wide range of things.


Log in to reply