Project

General

Profile

Actions

Bug #6322

closed

Flexible Alias Entry Input is not available

Added by Phillip Davis over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Start date:
05/05/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3
Affected Architecture:

Description

In 2.2.* it was possible to enter various strings into the "address" field of an alias detail line. The data would be parsed on submit and expanded out into the necessary individual IP addresses and subnets. This worked for both host and network types. The help text in 2.3 still indicates that these things are acceptable.
e.g.
172.30.1.0/24 192.168.3.4-192.168.4.1 172.50.0.0/16
would be accepted in an network alias and get expanded out into a bunch of individual subnets.

192.168.1.1-192.168.1.10
in a host alias would expand into 10 entries

192.168.1.4/30
in a host alias would expand into 4 entries - .4 .5 .6 .7

The code to parse and expand this type of entry still exists and works in 2.3. But the front-end validation is preventing the user from even entering strings like that.

Enhance the patterns for host and network address field entries so they allow these types of input.

It has been mentioned in the forum a couple of times and is easy enough to do:
https://forum.pfsense.org/index.php?topic=111361.0

Actions #2

Updated by Chris Buechler over 5 years ago

  • Status changed from New to Feedback

merged, thanks Phil!

Actions #3

Updated by Phillip Davis over 5 years ago

  • % Done changed from 0 to 100
Actions #4

Updated by Chris Buechler over 5 years ago

  • Status changed from Feedback to Resolved

works, thanks Phil!

Actions

Also available in: Atom PDF