Re: [pfSense] Lost limiter config after upgrade

2016-01-11 Thread Steve Yates 
Steve Yates wrote on Tue, Dec 15 2015 at 5:04 pm:
>   Per that bug report (https://redmine.pfsense.org/issues/4326), it 
> sounds like it's only an issue
> if NAT is being used, correct?  They work if NAT is not in use?

To follow up I set up a limiter on our data center router, for one IP 
doing an rsync backup to our office.  No NAT.  No issues yet after a week or 
two.  I didn't use the wizard, though I started it a few times to try to see 
what it was doing.  I just wanted the limiter.  The time of day scheduling is 
great for long running rsyncs since I drop the bandwidth down during the day.

Ugo Bellavance wrote on Tue, Dec 15 2015 at 11:02 pm:
> I had one of 28 mbps and 3 children to set the weight.  Before, it
> prevented traffic from going over 28 mbps.  Now I had to lower the
> partent limiter to 26 because it looks like some traffic goes over the
> 26 mbps.

A couple ideas based on what I read about setting up limiters...

1) did you create two limiters, one for upload and one for download?
2) in the limiter settings, did you pick a Mask setting or leave at None?  Mask 
will create multiple pipes, one per IP address.

I haven't watched the traffic graph that closely to see if it ever goes 
over a little bit.  If you're saying you set it to 28 and sometimes see 35 
Mbps, I am not seeing that.

--

Steve Yates
ITS, Inc.


___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Lost limiter config after upgrade

2015-12-16 Thread Ugo Bellavance 

On 15-12-13 08:29 PM, ED Fochler 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?


I made some tests and changes and I think it's working now.  However, it 
seems to be working differently than before.


I had one of 28 mbps and 3 children to set the weight.  Before, it 
prevented traffic from going over 28 mbps.  Now I had to lower the 
partent limiter to 26 because it looks like some traffic goes over the 
26 mbps.


Thanks,



___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Lost limiter config after upgrade

2015-12-16 Thread WebDawg 
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  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  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
>> 
>> 
>>
>> On Sun, Dec 13, 2015 at 5:29 PM, ED Fochler 
>> 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  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  tags have
>>> changed during the upgrade.  It looked like ?1 and ?2 and now it looks like
>>> labels.  Also, the  tag seem to include more stuff now.

 It was 28 and now it looks like
  
  
  28
  Mb
  none
  
  


 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

Re: [pfSense] Lost limiter config after upgrade

2015-12-16 Thread Steve Yates 
Chris L wrote on Tue, Dec 15 2015 at 1:32 am:

> 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.

Per that bug report (https://redmine.pfsense.org/issues/4326), it 
sounds like it's only an issue if NAT is being used, correct?  They work if NAT 
is not in use?

--

Steve Yates
ITS, Inc.



___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Lost limiter config after upgrade

2015-12-16 Thread ED Fochler 
That bug sounds awful.  I’m not seeing that problem at all.  

My limiter is a fair sharing style limiter, srcLimit limited by source address, 
 dstLimit limited by destination address.  I’m applying it to all traffic 
inbound to internal interfaces with a floating rule (MATCH) for any traffic not 
destined for another internal LAN, any protocol, IPv4.  srcLimit on the 
inbound, dstLimit on the outbound.  2.2.4 and 2.2.5 have been working as 
expected for me on a net6501.

Good luck Ugo.

ED.

> On 2015, Dec 14, at 11:26 AM, Ryan Clough  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
> 
> 
> 
> On Sun, Dec 13, 2015 at 5:29 PM, ED Fochler 
> 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  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  tags have
>> changed during the upgrade.  It looked like ?1 and ?2 and now it looks like
>> labels.  Also, the  tag seem to include more stuff now.
>>> 
>>> It was 28 and now it looks like
>>>  
>>>  
>>>  28
>>>  Mb
>>>  none
>>>  
>>>  
>>> 
>>> 
>>> 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

Re: [pfSense] Lost limiter config after upgrade

2015-12-15 Thread Chris L 
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  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
> 
> 
> 
> On Sun, Dec 13, 2015 at 5:29 PM, ED Fochler 
> 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  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  tags have
>> changed during the upgrade.  It looked like ?1 and ?2 and now it looks like
>> labels.  Also, the  tag seem to include more stuff now.
>>> 
>>> It was 28 and now it looks like
>>>  
>>>  
>>>  28
>>>  Mb
>>>  none
>>>  
>>>  
>>> 
>>> 
>>> 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

Re: [pfSense] Lost limiter config after upgrade

2015-12-14 Thread Ryan Clough 
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



On Sun, Dec 13, 2015 at 5:29 PM, ED Fochler 
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  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  tags have
> changed during the upgrade.  It looked like ?1 and ?2 and now it looks like
> labels.  Also, the  tag seem to include more stuff now.
> >
> > It was 28 and now it looks like
> >   
> >   
> >   28
> >   Mb
> >   none
> >   
> >   
> >
> >
> > 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

Re: [pfSense] Lost limiter config after upgrade

2015-12-14 Thread ED Fochler 
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  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  tags have changed 
> during the upgrade.  It looked like ?1 and ?2 and now it looks like labels.  
> Also, the  tag seem to include more stuff now.
> 
> It was 28 and now it looks like
>   
>   
>   28
>   Mb
>   none
>   
>   
> 
> 
> 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

[pfSense] Lost limiter config after upgrade

2015-12-13 Thread Ugo Bellavance 

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  tags have 
changed during the upgrade.  It looked like ?1 and ?2 and now it looks 
like labels.  Also, the  tag seem to include more stuff now.


It was 28 and now it looks like


28
Mb
none




Thanks,

Ugo

___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold