Actions
Bug #7465
closedFirewall rules fail if using a /19 in an alias as destination
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Unknown
Target version:
-
Start date:
04/12/2017
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.1
Affected Architecture:
Description
Having a new phone system here so added in a /19 network into an alias and created the firewall rule so source internal destination alias any / any
IP's in the far end of the range were not functioning from the firewall logs.
Removed the alias and just used the network address (/19) and all appears fine.
Happened on old 2.2 firmware and latest 2.3.1 as updated to see if it resolved the issue
Updated by Jim Pingle about 8 years ago
- Status changed from New to Rejected
I can't reproduce this. There is nothing special about a /19 in a network alias. It works fine as a source and as a destination.
Actions