Port ranges - restricting opening and closing ranges

[Gustavo Niemeyer]

How many port ranges are typically made available? One.. Two? Sounds like a
trivial problem.

In terms of concurrency, there are issues either way. Someone can open a
port while it is being closed, and whether that works or not depends purely
on timing.

gustavo @ http://niemeyer.net
On Aug 6, 2014 9:41 AM, "roger peppe" <roger.peppe at canonical.com> wrote:

> On 5 August 2014 19:34, Gustavo Niemeyer <gustavo at niemeyer.net> wrote:
> > On Tue, Aug 5, 2014 at 4:18 PM, roger peppe <rogpeppe at gmail.com> wrote:
> >> close ports 80-110 -> error (mismatched port range?)
> >
> > I'd expect ports to be closed here, and also on 0-65536.
>
> I'm not sure. An advantage of requiring that exactly the
> same ports must be closed as were opened, you can use the port range
> as a key, which makes for a very simple (and trivially concurrent-safe)
> implementation in a mongo collection.
>
> I'd suggest that this compromise is worth it. We could always make an
> initial
> special case for 0-65535 too, if desired.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140806/7bb6219a/attachment.html>