Project

General

Profile

Actions
Copy link

Feature #1979

closed
JP MM

Allow user-defined rules to utilize built-in system aliases

Feature #1979: Allow user-defined rules to utilize built-in system aliases

Added by Jim Pingle almost 15 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Marcos M
Category:
Aliases / Tables
Target version:
2.8.0
Start date:
10/25/2011
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
24.11
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.

Files

Download all files
clipboard-202410122022-iudky.png (237 KB) clipboard-202410122022-iudky.png Danilo Zrenjanin, 10/12/2024 06:22 PM
clipboard-202410130957-wlooi.png (58.8 KB) clipboard-202410130957-wlooi.png dylan mendez, 10/13/2024 03:57 PM

Related issues 2 (0 open — 2 closed)

Has duplicate Feature #15774: Add user-accessible system aliasesDuplicate

Actions
Precedes Feature #15776: System Aliases for various reserved networksResolvedMarcos M

Actions

J- Updated by JD - about 14 years ago Actions
Copy link
 #1

Indeed, this would be really helpful.

J- Updated by JD - over 13 years ago Actions
Copy link
 #2

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?

CB Updated by Chris Buechler over 13 years ago Actions
Copy link
 #3

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

JP Updated by Jim Pingle over 13 years ago Actions
Copy link
 #4

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.

EL Updated by Ermal Luçi over 13 years ago Actions
Copy link
 #5

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.

JP Updated by Jim Pingle about 7 years ago Actions
Copy link
 #6

  • Category set to Rules / NAT
  • Assignee set to Jim Pingle

JP Updated by Jim Pingle about 7 years ago Actions
Copy link
 #7

  • Category changed from Rules / NAT to Aliases / Tables

JP Updated by Jim Pingle almost 2 years ago Actions
Copy link
 #8

  • Has duplicate Feature #15774: Add user-accessible system aliases added

MM Updated by Marcos M almost 2 years ago Actions
Copy link
 #9

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:52e512c0555d9f5a91732907e524364358d3f70c.

MM Updated by Marcos M almost 2 years ago Actions
Copy link
 #10

  • Subject changed from Add some default read-only system aliases to Add user-accessible read-only system aliases
  • Assignee changed from Jim Pingle to Marcos M
  • Target version changed from Future to 2.8.0
  • Plus Target Version set to 24.11

The current system aliases such as bogons can now be used in the GUI. Additional ones (such as the given examples) can be considered/added separately.

The system aliases are listed under Firewall > Aliases > All.

JP Updated by Jim Pingle almost 2 years ago Actions
Copy link
 #11

  • Precedes Feature #15776: System Aliases for various reserved networks added

JP Updated by Jim Pingle almost 2 years ago Actions
Copy link
 #12

  • Subject changed from Add user-accessible read-only system aliases to Allow user-defined rules to utilize built-in system aliases

I moved the additional new system alias definition part to a new issue: #15776

DZ Updated by Danilo Zrenjanin almost 2 years ago Actions
Copy link
 #13

Tested against:

24.11-ALPHA (amd64)
built on Sat Oct 12 15:22:00 UTC 2024
FreeBSD 15.0-CURRENT

When I started typing 'bogons,' the bogons alias was available. However, hovering the alias in the rule doesn't show the list of networks as it does with other aliases.

Please check.

MM Updated by Marcos M almost 2 years ago Actions
Copy link
 #14

That issue along with some others from other feedback has been fixed for the next build.

DM Updated by dylan mendez almost 2 years ago Actions
Copy link
 #15

This looks good on the latest build.

JP Updated by Jim Pingle almost 2 years ago Actions
Copy link
 #16

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom