1.x: Add optional provisioning of ipv4 delegated prefix IPs #57
Comments
jblosser
added a commit
to jblosser/amazon-ec2-net-utils
that referenced
this issue
Jun 11, 2022
…prefix if the ifcfg option 'EC2PROVISIONPFXIPS' is set. The option defaults to 'no' for back-compat with current behavior. This uses ipcalc(1) to determine start and stop addresses of the range, which is already included in the initscripts package. Addresses amazonlinux#57
|
This will be included in an upcoming 1.7.0 release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When support for prefix delegation was added to 1.x, it was limited to updating routing rules, with the comment "Assignment of individual addresses within the prefix is out of scope for this package, and would instead be handled by a local IPAM system. A typical such system might provision IP addresses for use by locally running containers, etc."
The problem is that if we are using prefixes on e.g. an ec2 iptables NAT instance and provisioning IPs from the delegated range locally, they are removed whenever the ec2net functions run, multiple times an hour. It would be preferable if there was an option to have at least ipv4 addresses inside delegated prefixes detected and managed like other secondary addresses are.
PR incoming.
The text was updated successfully, but these errors were encountered: