Notification following wizard - possible feature change in wizard



  • Didn't want to reply in https://forum.pfsense.org/index.php?topic=104900.0 for what is (on the face of it) a very similar error, just in case this isn't mostly the same thing.

    After running the wizard to get a config, I'm immediately getting a notification:-

    "There were error(s) loading the rules: /tmp/rules.debug.129: errors in queue definition - The line in question reads [129]: queue qInternet on em0 bandwidth 15728.64Kb hfsc ( ecn , linkshare 15728.64Kb , upperlimit 15728.64Kb ){ qACK, qP2P, qVOIP }]"

    Now, on the assumption that the same initial "fix" Nullity suggested in the above linked thread holds true (delete the upperlimit from qInternet as it's superficially redundant), why is the wizard applying this limiter at all?

    (We have a 30Mbps pipe dynamically shared between up and down, so 15Mbps 50/50 split in the traffic shaper made most sense to me)



  • With the usage of qInternet, I think upper-limit is intended to act like the rate-limit applied to the actual interface in a multi-WAN (or multi-LAN?) situation. I dunno if it really makes a difference or if it really is unneeded.

    Your error seems different, since you did not exceed the interface's bitrate with the queue's bitrate (afaict).



  • The wizard applied the same value to both qInternet and the interface, and removing upperlimit has "fixed" the notification (a very small annoyance only).



  • @PantsManUK:

    The wizard applied the same value to both qInternet and the interface, and removing upperlimit has "fixed" the notification (a very small annoyance only).

    Oh. Well, that seems like an obvious candidate for the bug-tracker.

    I wonder if it is already fixed in 2.3.



  • "15728.64Kb" seems like a very precise bandwidth setting. Maybe the interface isn't set to this precision and qInternet is technically greater than the interface, eve if slightly slow. /guessing



  • Tiny bit "digging up the dead", but after a few days of no notifications, I started getting a notification for almost the exact same reason on the same rule (following a reboot - been ignoring it for a while due to other work getting in my way).

    So, this morning I started looking through all the rules and realised that qInternet on WAN (which in theory matches qInternet on LAN), was in fact subtly different: rather than the bandwidth limits being expressed in Kbit/s, they were in Mbit/s. I've now swapped LAN qInternet over to Mbit units and will find out if that has fixed it next time it restarts.



  • @PantsManUK:

    Tiny bit "digging up the dead", but after a few days of no notifications, I started getting a notification for almost the exact same reason on the same rule (following a reboot - been ignoring it for a while due to other work getting in my way).

    So, this morning I started looking through all the rules and realised that qInternet on WAN (which in theory matches qInternet on LAN), was in fact subtly different: rather than the bandwidth limits being expressed in Kbit/s, they were in Mbit/s. I've now swapped LAN qInternet over to Mbit units and will find out if that has fixed it next time it restarts.

    Forgive my ignorance, but why does qInternet exist on the WAN? (multi-WAN?)



  • Can't really answer this Nullity, other than to say I only have two wizards available - "Multi Lan/Wan" and "Dedicated Links". Reading the draft book I guessed I didn't want to use "Dedicated Links"  ;D



  • likely same issue as in https://redmine.pfsense.org/issues/5721


Log in to reply