Allow extended alias inputs #3890
Allow extended alias inputs #3890

Currently if you enter a space-separated list of subnets in the IP address box when entering an alias, the code reports that the data is invalid. But it does actually expand the list of subnets into multiple rows, and enters the various subnet CIDRs into the CIDR column for the user. The user can press Save a second time and the data is now valid so the code saves it happily. This is rather odd, as reported in redmine #3890.
Also, if you input an IP range (e.g. 192.168.20.0-192.168.20.30) plus description and in the 2nd row put some other subnet and description, the range is correctly expanded, but the description only appears against the 1st subnet of the range. The description from the 2nd row ends up as the description against the 2nd subnet of the range, and the rest of the descriptions are blank. i.e. the descriptions do not get copied and pushed down as the IP ranges are expanded.
This change fixes all that stuff by first parsing the posted data and expanding any IP ranges and/or space-separated lists, building arrays that have all their entries lined up:
$input_addresses[]
$input_address_subnet[]
$final_address_details[]
which are then validated.

This is for master (2.2) branch. Actually it was not too difficult to integrate.
NewEraCracker/pfsense,pfsense/pfsense,brunostein/pfsense,phil-davis/pfsense,ch1c4um/pfsense,BlackstarGroup/pfsense,dennypage/pfsense,BlackstarGroup/pfsense,NewEraCracker/pfsense,brunostein/pfsense,NewEraCracker/pfsense,pfsense/pfsense,pfsense/pfsense,jxmx/pfsense,dennypage/pfsense,ch1c4um/pfsense,dennypage/pfsense,NewEraCracker/pfsense,ptorsten/pfsense,brunostein/pfsense,dennypage/pfsense,pfsense/pfsense,NOYB/pfsense,NOYB/pfsense,jxmx/pfsense,jxmx/pfsense,ptorsten/pfsense,ch1c4um/pfsense,phil-davis/pfsense,BlackstarGroup/pfsense,NOYB/pfsense,phil-davis/pfsense,BlackstarGroup/pfsense,ch1c4um/pfsense,phil-davis/pfsense,ptorsten/pfsense