It seems that the DHCP-server in technitium/dns-server currently doesnt support to give out leases based on option82 information.
Option82 is handy to have a semi-static dynamic network.
As in the client will be using DHCP to request IP-information but based on physical location whatever client that is connected to lets say switch 4 interface 9 will always get the same reply/lease.
The magic is perfomed by a DHCP-relay along the road to inject CircuitID and RemoteID.
This way you can have static assignment without involving DUID/MAC-address and having to maintain a static lease file (that needs to get synced among DHCP-servers in a cluster). Actually with a fully option82 network there is no need for a lease file at all (which gives fewer writes to the storage).
Perhaps this could be implemented by expanding the use of "Reserved Leases"?
It seems that the DHCP-server in technitium/dns-server currently doesnt support to give out leases based on option82 information.
Option82 is handy to have a semi-static dynamic network.
As in the client will be using DHCP to request IP-information but based on physical location whatever client that is connected to lets say switch 4 interface 9 will always get the same reply/lease.
The magic is perfomed by a DHCP-relay along the road to inject CircuitID and RemoteID.
This way you can have static assignment without involving DUID/MAC-address and having to maintain a static lease file (that needs to get synced among DHCP-servers in a cluster). Actually with a fully option82 network there is no need for a lease file at all (which gives fewer writes to the storage).
Perhaps this could be implemented by expanding the use of "Reserved Leases"?