Network Map doesn't properly deal with nested networks

[cluther]

The Network Map has a problem in the way it deals with nested subnets. It will often pick a network that isn't the most specific one available. This appears to be due to it using the IpNetwork.findNet method instead of IpNetwork.getNet.

Example Network Structure:

10.0.0.0/8

10.1.0.0/16

10.1.1.0/24

10.1.1.0/27
10.1.1.32/27

In this scenario, the network map will always show the 10.1.1.0/24 instead of the proper 10.1.1.0/27 that actually contains the devices.

[cluther]

Proposed patch

[cluther]

(In [9734]) * Fixes #3485: Use most specific network match on network map. Reviewed by jstevens.

[jstevens]

(In [9772]) refs #3485
patching r9734 to the 2.2.x branch

[cluther]

This is already fixed in 2.2.4. Not sure why the milestone was moved to blue crab.