At the moment what you can do is choose a /31.
I created a couple of issues which should make this use case possible:
https://github.com/openwisp/openwisp-controller/issues/842
https://github.com/openwisp/openwisp-controller/issues/843
I hope this is better than nothing.
F.
On Thu, 14 Mar 2024
Actually same idea came to my mind . But i abandoned it as it populates
with a lot of subnets and makes managing them a mess. Instead of avoiding
mistakes one may create mistake due to too many subnets generated (one per
ip per device) son 20 devices allready 20 subnets.
And yes it cannot crea
You can try instructing the rule to create very small subnets (eg: /32 or
/31) and get 1 IP.
I remember there was an issue with subnets sized /32 which would not allow
to get 1 IP but I don't remember if this bug is still there.
Let me know if you try and if the bug is still there we should open an
On Tuesday, March 12, 2024 at 3:29:48 PM UTC+2 f.capoano wrote:
The help text tries to explain this:
"indicates how many addresses will be created for each subnet."
So if you have 2 subnets, you will get 1 ip for each subnet, so you get a
total of 2 IP addresses reserved for each device.
Y
The help text tries to explain this:
"indicates how many addresses will be created for each subnet."
So if you have 2 subnets, you will get 1 ip for each subnet, so you get a
total of 2 IP addresses reserved for each device.
We currently have 2 built-in subnet division rules:
1. device: the ru
