Project

General

Profile

Bug #7665

Host range validation for Aliases is not strict enough

Added by Re Load over 2 years ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Aliases / Tables
Target version:
-
Start date:
06/28/2017
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:
All

Description

Steps to reproduce:

1. Enter an invalid host range for an IP alias, such as 192.168.1.1-10, and click Save.

The host range will be accepted, but does not function as one might expect. In fact, the syntax is invalid and only the first host in the range will be matched by this alias.

Desired behaviour:

The host range should be rejected by the form validation. The correct syntax for the example above would be 192.168.1.1-192.168.1.10

History

#1 Updated by Jim Pingle 3 months ago

  • Category changed from Web Interface to Rules / NAT

#2 Updated by Jim Pingle 3 months ago

  • Category changed from Rules / NAT to Aliases / Tables

Also available in: Atom PDF