Adding support for "on commit", "on expire", and "on release" statements in DHCPv6
  • Updated on 26 Sep 2018
  • 1 minute to read
  • Contributors
  • Print
  • Share
  • Dark
    Light

Adding support for "on commit", "on expire", and "on release" statements in DHCPv6

  • Print
  • Share
  • Dark
    Light

Question:

How do I use the new on_commit, on_expiry, on_release statements for DHCPv6?

Answer:

These statements function in DHCPv6 pretty much the same as they do in DHCPv4, allowing you to specify actions to be taken when the matching event happens to the lease. They can be placed in any valid scope, such as the global scope or subnet statements.

# Global instances, should be used if we don't have anything better
on commit { log(info, concat("global commit: ", option dhcp6.client-id)); }
on expiry { log(info, concat("global expiry: ", option dhcp6.client-id)); }
on release { log(info, concat("global release: ", option dhcp6.client-id)); }
Was this article helpful?