Re: [PF] bug in port range.

2012-01-04 Thread Henning Brauer
* Patrick Lamaiziere patf...@davenulle.org [2012-01-03 19:00]: Well because for me 80:82 is (80, 81, 82) and 82:80 the same items and so the same range. but it is NOT the same. I'd claim your expectations is strange ;) So what is the meaning for PF of the range 82:80? If this is a non sense,

[PF] bug in port range.

2012-01-03 Thread Patrick Lamaiziere
Hello, happy new year. I think there is a off-by-one error in Packet Filter port ranges, for example with an exclude boundary range : port1 port2 PF or pfctl does not check that port1 = port2 and if port1 port2 the port range is not correct. For example 82 80 is not the same as 80 82 (but

Re: [PF] bug in port range.

2012-01-03 Thread Henning Brauer
* Patrick Lamaiziere patf...@davenulle.org [2012-01-03 17:45]: I think there is a off-by-one error in Packet Filter port ranges, for example with an exclude boundary range : port1 port2 nope. Ports and ranges of ports are specified using these operators: :

Re: [PF] bug in port range.

2012-01-03 Thread Russell Garrison
For those of us playing the CS home game. Is this an example of left-to right evaluation? My thought on this was that the value 81 isn't greater than 82 and isn't less than 80, so the rule doesn't match.

Re: [PF] bug in port range.

2012-01-03 Thread Patrick Lamaiziere
Le Tue, 3 Jan 2012 17:54:18 +0100, Henning Brauer lists-open...@bsws.de a icrit : Hello, * Patrick Lamaiziere patf...@davenulle.org [2012-01-03 17:45]: I think there is a off-by-one error in Packet Filter port ranges, for example with an exclude boundary range : port1 port2 nope.