Project

General

Profile

Feature #11225

Change Host Alias range when it is made from CIDR

Added by Constantine Kormashev about 2 months ago. Updated about 2 months ago.

Status:
Rejected
Priority:
Very Low
Assignee:
-
Category:
Aliases / Tables
Target version:
-
Start date:
01/06/2021
Due date:
% Done:

0%

Estimated time:

Description

Now if I make an Alias using CIDR like 192.168.1.*2*/30 it makes 4 entries which starts from 1st host in the given range:
192.168.1.0
192.168.1.1
192.168.1.2
192.168.1.3

But probably this is different from expected and the better would be to start entries from host defined in range e.g. example above will give us:
192.168.1.2
192.168.1.3

It might seem not important if we use a short network but if I would like to add 260 hosts from 192.168.0/23 it would be much easy and safer to write 192.168.0.250/23 than using a range 192.168.0.250-192.168.1.255 for this goal.

History

#1 Updated by Jim Pingle about 2 months ago

  • Status changed from New to Rejected

The alias doesn't know or care how it's used. It covers the entire subnet. There is no concept for network ID/broadcast when used for NAT, routing, etc. Also can be used as a shortcut for making a range inside a larger actual subnet.

This would change the behavior in counter-intuitive ways and make people do extra work/math to get the more common result.

If you don't want those addresses in the alias for a given purpose, it's easier to remove them after the range is created.

Also available in: Atom PDF