I just tried a limiter through the wizard and it killed all traffic out the wan. Just talked to someone on #pfsense @freenode and they had the same issue.
On Tue, Dec 15, 2015 at 1:32 AM, Chris L <c...@viptalk.net> wrote: > Yeah there’s a difference between the upgrade fails and the upgraded system > just doesn’t work with limiters. > > It seems either traffic just doesn’t flow or limiters don’t limit. > > I am really looking forward to this being fixed. Until then, 2.1.5 rules the > roost. > > It’s a pretty sad state. > >> On Dec 14, 2015, at 8:26 AM, Ryan Clough <ryan.clo...@dsic.com> wrote: >> >> Might also depend on how the limiters are being used and how the rest of >> the router is configured. I have been up against this bug for at least six >> months: >> https://redmine.pfsense.org/issues/4326 >> >> ___________________________________________ >> ¯\_(ツ)_/¯ >> Ryan Clough >> Information Systems >> Decision Sciences International Corporation >> <http://www.decisionsciencescorp.com/> >> <http://www.decisionsciencescorp.com/> >> >> On Sun, Dec 13, 2015 at 5:29 PM, ED Fochler <soek...@liquidbinary.com> >> wrote: >> >>> Limiters work on 2.2.4, I’m using them. But I didn’t upgrade, I created >>> the limiters on 2.2.4. Are you asking if limiters work? Or are you just >>> noting that they don’t cleanly upgrade? If you create them through the GUI >>> and link them in with the firewall rules, do they work now? >>> >>> ED. >>> >>>> On 2015, Dec 12, at 1:43 PM, Ugo Bellavance <u...@lubik.ca> wrote: >>>> >>>> Hi, >>>> >>>> We upgraded from 2.0.1-RELEASE to 2.2.4-RELEASE and the limiter that >>> worked on 2.0.1 stopped working. This limiter (and sub-limiters) is >>> located on an inside interface and its role is to limit the traffic that >>> can come in. This firewall is at a remote site and we replicate backups >>> there. We use this limiter because the bandwidth at the remote site is >>> higher than at our main site. Using this limiter avoids saturating our >>> main site's WAN link and cause slowdowns. >>>> >>>> Looking at the config diffs, it looks like the <dnpipe> tags have >>> changed during the upgrade. It looked like ?1 and ?2 and now it looks like >>> labels. Also, the <bandwidth> tag seem to include more stuff now. >>>> >>>> It was <bandwidth>28</bandwidth> and now it looks like >>>> <bandwidth> >>>> <item> >>>> <bw>28</bw> >>>> <bwscale>Mb</bwscale> >>>> <bwsched>none</bwsched> >>>> </item> >>>> </bandwidth> >>>> >>>> >>>> Thanks, >>>> >>>> Ugo >>>> >>>> _______________________________________________ >>>> pfSense mailing list >>>> https://lists.pfsense.org/mailman/listinfo/list >>>> Support the project with Gold! https://pfsense.org/gold >>> >>> _______________________________________________ >>> pfSense mailing list >>> https://lists.pfsense.org/mailman/listinfo/list >>> Support the project with Gold! https://pfsense.org/gold >>> >> >> -- >> This email and its contents are confidential. If you are not the intended >> recipient, please do not disclose or use the information within this email >> or its attachments. If you have received this email in error, please report >> the error to the sender by return email and delete this communication from >> your records. >> _______________________________________________ >> pfSense mailing list >> https://lists.pfsense.org/mailman/listinfo/list >> Support the project with Gold! https://pfsense.org/gold > > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
