Laine Stump 3f06ae4171 network: validate network NAT range
This patch modifies virSocketAddrGetRange() to function properly when
the containing network/prefix of the address range isn't known, for
example in the case of the NAT range of a virtual network (since it is
a range of addresses on the *host*, not within the network itself). We
then take advantage of this new functionality to validate the NAT
range of a virtual network.

Extra test cases are also added to verify that virSocketAddrGetRange()
works properly in both positive and negative cases when the network
pointer is NULL.

This is the *real* fix for:

https://bugzilla.redhat.com/show_bug.cgi?id=985653

Commits 1e334a and 48e8b9 had earlier been pushed as fixes for that
bug, but I had neglected to read the report carefully, so instead of
fixing validation for the NAT range, I had fixed validation for the
DHCP range. sigh.

(cherry picked from commit a6f9af8292b6462e509892b3a16acbcaaef61e4e)
2015-09-21 20:17:58 -04:00
..
2014-09-03 09:36:13 -06:00
2015-05-21 18:13:18 +02:00
2015-04-23 17:08:48 -04:00
2015-04-23 17:08:48 -04:00
2015-06-25 09:11:15 +02:00
2015-04-23 17:08:48 -04:00
2015-04-27 16:03:31 +02:00
2014-09-04 15:18:43 -06:00
2015-05-21 18:13:18 +02:00
2015-05-04 15:01:27 +02:00
2015-04-23 17:08:48 -04:00
2014-11-25 08:47:12 -07:00
2015-04-14 19:33:02 +02:00
2015-04-14 19:33:02 +02:00
2014-04-08 11:15:55 +01:00
2015-04-23 17:08:48 -04:00
2015-04-23 17:08:48 -04:00
2015-04-23 17:08:48 -04:00