Project

General

Profile

Actions

Feature #1979

open

Add some default read-only system aliases

Added by Jim Pingle over 12 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Aliases / Tables
Target version:
Start date:
10/25/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

It would be useful to have some stock aliases that come by default which are not editable by users. These aliases would be somewhat of an extension to the choices we already have for things like "xxx Subnet" and "xxx Address".

Some ideas:
  • Local Networks
  • ipv4_private (or perhaps rfc1918) - 192.168.0.0/16, 10.0.0.0/8, and 172.16.0.0/12
  • ipv6_linklocal - fe80::/10
  • ipv6_private - fc00::/7
  • ipv6_multicast - ff00::/8

Having those available would save users from having to look them up, hardcode them, or make their own aliases for the same values on every system.

Actions #1

Updated by JD - over 11 years ago

Indeed, this would be really helpful.

Actions #2

Updated by JD - about 11 years ago

I'd like to push things a bit since this would really help a lot.

Jim P wrote:

Some ideas:
  • Local Networks

I'm using this one but keeping track with additions/deletions of network segments is a pain.

  • ipv4_private (or perhaps rfc1918) - 192.168.0.0/16, 10.0.0.0/8, and 172.16.0.0/12
  • ipv6_linklocal - fe80::/10
  • ipv6_private - fc00::/7
  • ipv6_multicast - ff00::/8

How about a set of aliases covering ports as well?

Having those available would save users from having to look them up, hardcode them, or make their own aliases for the same values on every system.

Any idea when somebody might have time to implement this?

Actions #3

Updated by Chris Buechler about 11 years ago

as with anything else - when someone's willing to pay for it, or someone does it and submits a merge request.

Actions #4

Updated by Jim Pingle about 11 years ago

Not sure we'd need much in the way of port aliases. We already have a ton of ports in the drop-down list on firewall and NAT rules.
I'd rather pull info from /etc/services into there before I'd want to pre-create port aliases.

And like Chris said, it will happen when funding appears or code appears. It's a nice to have feature but not critical.

Actions #5

Updated by Ermal Luçi about 11 years ago

IIrc you already can use the names of a port in /etc/services wherever a port is asked.
So instead of typing 80 you can type http and so on.

I made the changes quite some time ago to support this, unless it has been broken moving on with changes it should work.

Actions #6

Updated by Jim Pingle over 4 years ago

  • Category set to Rules / NAT
  • Assignee set to Jim Pingle
Actions #7

Updated by Jim Pingle over 4 years ago

  • Category changed from Rules / NAT to Aliases / Tables
Actions

Also available in: Atom PDF