-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interface-ID missing in A10-NSP DHCPv6 Relay Reply - RFC6221 #300
Comments
Please verify the following fix: |
Hi @GIC-de, sadly this doesn't fix the issue:
I see the Interface-ID inside the I've used the following config for testing:
|
When stepping through with the debugger, the interface-id is correctly set on Edit 1: Edit 2:
|
Please verify the solution here: |
Describe the bug
According to RFC6221, the DHCPv6 Relay Reply packet must contain the interface-id received by in relay-forw. https://datatracker.ietf.org/doc/html/rfc6221#section-5.3.2
However, when BNG Blaster acts as an A10-NSP with DHCPv6 NA/PD enabled, the relay-reply doesn't contain the interface-id. This triggers undefined behavior in access-nodes, like dropping the response or not decapsulating the relay-reply.
I think it's related to this code here, where the interface-id is not copied to the outer dhcpv6.
https://github.com/rtbrick/bngblaster/blob/main/code/bngblaster/src/bbl_a10nsp.c#L485
To Reproduce
Version (
bngblaster -v
):Add any other context about the problem here.ON configuration:
Demo config from here, where BNGBlaster also acts an LDRA: #164
The text was updated successfully, but these errors were encountered: