Skip to content
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

Implement ECS address override feature #1168

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

edmonds
Copy link
Contributor

@edmonds edmonds commented Oct 29, 2024

This commit implements an EDNS Client Subnet address override feature. It is controlled by two newly introduced config options client-subnet-address-override-ipv4 and client-subnet-address-override-ipv6. If set, when a query is initiated by Unbound using the ECS option, the override address value specified in the config will be substituted and used instead of the original value calculated from the client's actual source address.

This can be useful in certain situations where the original ECS address value doesn't make sense. E.g., it's generally not useful to send ECS queries to nameservers on the Internet using RFC 1918 subnet address values. Or it may be helpful to spoof the ECS address value to a nearby subnet if an ECS-enabled nameserver has incorrect geolocation data for the real subnet value.

This commit does not include the re-generated flex/bison output files due to the changes to the .lex/.y files. Those changes should be added as a followup if this patch is merged.

This commit implements an EDNS Client Subnet address
override feature. It is controlled by two newly introduced
config options `client-subnet-address-override-ipv4` and
`client-subnet-address-override-ipv6`. If set, when a query is initiated
by Unbound using the ECS option, the override address value specified
in the config will be substituted and used instead of the original value
calculated from the client's actual source address.

This can be useful in certain situations where the original ECS address
value doesn't make sense. E.g., it's generally not useful to send ECS
queries to nameservers on the Internet using RFC 1918 subnet address
values. Or it may be helpful to spoof the ECS address value to a nearby
subnet if an ECS-enabled nameserver has incorrect geolocation data for
the real subnet value.

This commit does not include the re-generated flex/bison output files
due to the changes to the .lex/.y files. Those changes should be added
as a followup if this patch is merged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant