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
Is your feature request related to a problem? Please describe.
We CNAAS-NMS has an option for configuring dhcp_relays. because (for example) Juniper has a different config tree for dhcpv6 we have to 'detect' in Jinja if a dhcp relay is ipv4 or ipv6. This makes the jinja2 templates hacky and ugly.
Describe the solution you'd like
Thats why It would be prettier tot just include an option dhcpv6_relays as a list of ipv6 addresses
Describe alternatives you've considered
The alternative is to solve it in jinja2 templates. But that can become hacky and cumbersome....at least for a Juniper
Additional context
None
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We CNAAS-NMS has an option for configuring dhcp_relays. because (for example) Juniper has a different config tree for dhcpv6 we have to 'detect' in Jinja if a dhcp relay is ipv4 or ipv6. This makes the jinja2 templates hacky and ugly.
Describe the solution you'd like
Thats why It would be prettier tot just include an option dhcpv6_relays as a list of ipv6 addresses
Describe alternatives you've considered
The alternative is to solve it in jinja2 templates. But that can become hacky and cumbersome....at least for a Juniper
Additional context
None
The text was updated successfully, but these errors were encountered: