Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's RFC9686 that adds address registration mechanism to DHCPv6. It defines two DHCPv6 messages (ADDR-REG-INFORM and ADDR-REG-REPLY) and one DHCPv6 option (ADDR-REG-ENABLE). Covering those is what this PR does.
This includes new UTs. The tests on master currently fail on unrelated changes (test/scapy/layers/dcerpc.uts). So I ran just the DHCPv6 tests (python3 UTscapy.py -t test/scapy/layers/dhcp6.uts -F) and they all passed. This includes several new ones that were added.
This should have no impact on other libs.
Tox/Flake8 says the code is clean.
There are LOTS of pylint warnings in the dhcp6.py file, but AFAICT none related to my new code.
Haven't contributed in ages, so apologies if missed anything. Will gladly update with whatever is needed.
I've squashed the commits.