I have a use case where we have a 21-bit block of IP addresses (4,096) that
we cannot further subnet. The router is maintained by another
organization, and we already have hundreds of devices using this network,
mostly statically assigned. We currently block off ranges in a spreadsheet
for each customer, and they maintain their own IP Addresses.
We now want to implement a Foreman server to manage the IP addressing, and
would like to limit the range of available IPs for each customer.
My first stab at this was to create multiple subnets, but all with the same
Network address using "Internal DB" as the IPAM, and the only difference
between each subnet created was the "Start|End of IP Range" and the
organization to which the subnet is assigned. I quickly realized this
won't work because as soon as I created my second subnet, I received the
following error on the Network Address field:* "has already been taken"*
What Suggestions are out there for my use case? Basically, having multiple
customers on one subnet, and masking the "available IPs" for each
organization.
> If there is no existing feature or workaround, how viable is this as a
> feature request to foreman?
Can you formalize the feature request in a redmine ticket?
I think we cannot make the network field non-unique, because we use
network+netmask to determine which subnet belongs to an individual IP
address. There are many usecases where we need that, Discovery comes to
my mind first.
There could be a way of extending range of a subnet into subranges.
These could be either defined separately or assigned per
organization/location. Or there could be some kind of evaluation
function (definable by user) that would give for org/loc pair a valid
range. That's maybe too complicated for users, but easier to implement
Hopefully I'm not asking for too much, and if anyone else thinks this would
be useful, please vote it up on redmine. Thanks!
···
On Thursday, May 21, 2015 at 10:48:57 AM UTC-5, Lukas Zapletal wrote:
>
> > If there is no existing feature or workaround, how viable is this as a
> > feature request to foreman?
>
> Can you formalize the feature request in a redmine ticket?
>
>
>
···
On Monday, June 29, 2015 at 4:07:50 PM UTC-5, lawre wrote:
>
> I have created a redmine ticket
> http://projects.theforeman.org/issues/10949
>
> Hopefully I'm not asking for too much, and if anyone else thinks this
> would be useful, please vote it up on redmine. Thanks!
>
> On Thursday, May 21, 2015 at 10:48:57 AM UTC-5, Lukas Zapletal wrote:
>>
>> > If there is no existing feature or workaround, how viable is this as a
>> > feature request to foreman?
>>
>> Can you formalize the feature request in a redmine ticket?
>>
>>
>>