Project

General

Profile

Actions
Copy link

Bug #7665

closed

Host range validation for Aliases is not strict enough

Added by Re Load almost 9 years ago. Updated 26 days ago.

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

0%

Estimated time:
Plus Target Version:
Release Notes:
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

Actions
Copy link
 #1

Updated by Jim Pingle almost 7 years ago

  • Category changed from Web Interface to Rules / NAT
Actions
Copy link
 #2

Updated by Jim Pingle almost 7 years ago

  • Category changed from Rules / NAT to Aliases / Tables
Actions
Copy link
 #3

Updated by Bryan Allen 26 days ago

  • Status changed from New to Resolved

Attempted this on 26.03 and the set the aliases to block 192.168.1.0/24 on a 192.168.0.0/16 network and then set a manual ip for a device as 192.168.1.10 and it is being blocked as expected. Deleting the rule automatically restores internet to the device as expected. Looks like this was fixed with in updated versions.

Actions
Copy link

Also available in: Atom PDF