You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since isc-dhcp44-server-4.4.2_1 supports the feature to configure IP pool outside of a directly connected subnet, it would be possible to have the feature in OPNsense as well?
In order to enable the functionality we just need to add an empty pool for the directly connected subnet:
Then it'll be possible to create IP pools for other networks.
Since after the change OPNsense's DHCPv4 will be handling different pool leases, I think it would be needed to reorganize the leases page and divide them in each configured subnet.
Also, if it would be possible to add to the lease counter the total IP configured in a pool (i.e. 5/100) instead of just displaying (5) it would be awesome.
Thank you for your hard work!
tofaz
The text was updated successfully, but these errors were encountered:
Hi all,
Since isc-dhcp44-server-4.4.2_1 supports the feature to configure IP pool outside of a directly connected subnet, it would be possible to have the feature in OPNsense as well?
In order to enable the functionality we just need to add an empty pool for the directly connected subnet:
subnet XXX.XXX.XXX.XXX netmask XXX.XXX.XXX.XXX {
}
Then it'll be possible to create IP pools for other networks.
Since after the change OPNsense's DHCPv4 will be handling different pool leases, I think it would be needed to reorganize the leases page and divide them in each configured subnet.
Also, if it would be possible to add to the lease counter the total IP configured in a pool (i.e. 5/100) instead of just displaying (5) it would be awesome.
Thank you for your hard work!
tofaz
The text was updated successfully, but these errors were encountered: