Clarifiy unexpected Packet private CIDR behaviour

[DGollings]

Attempts to address or at least mitigate issue #159

[rata]

Can you please update the PR title to be more representative of what the change does? :)

[rata]

Also, please update the commit titles to reflect the changes, (not just the unsuful gihub default of "Update ", squash them if possible :)

[DGollings]

Also, please update the commit titles to reflect the changes, (not just the unsuful gihub default of "Update ", squash them if possible :)

I'm more of a 'never rewrite (git) history' type of guy, so never bothered to learn how to either rename a commit or squash it, could you point me to the FM and I'll figure it out :)

[rata]

@DGollings no worries, just add a different commit then and I can squash on merge :)

[DGollings]

Quite the discussion: https://softwareengineering.stackexchange.com/questions/263164/why-squash-git-commits-for-pull-requests

I can see the pro/cons, but trunk based development ftw (?)

done, ish, removed what I think was a duplicate Note:
(edit: although I agree my original commit message was useless)

[rata]

LGTM, thanks again! :-)