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

AllowedIps: Use ip_network_table instead of homegrown trie impl #184

Merged
merged 1 commit into from
Jul 21, 2021

Conversation

agrover
Copy link
Collaborator

@agrover agrover commented Jul 6, 2021

ip_network_table crate is exactly what we need so use it instead of
own trie impl. Big code/complexity reduction. Keep all unit tests.

This in turn uses ip_network and treebitmap crates, these both
look good too. (wireguard-rs also uses these, fwiw.)

Make small changes to rest of code as needed. AllowedIps interface is
mostly the same but I couldn't resist a few tweaks.

ip_network_table crate is exactly what we need so use it instead of
own trie impl. Big code/complexity reduction. Keep all unit tests.

This in turn uses ip_network and treemap crates, these both
look good too. (wireguard-rs also uses these, fwiw.)

Make small changes to rest of code as needed. AllowedIps interface is
mostly the same but I couldn't resist a few tweaks.
@agrover agrover changed the title Use ip_network_table instead of homegrown trie impl AllowedIps: Use ip_network_table instead of homegrown trie impl Jul 6, 2021
@Bren2010 Bren2010 merged commit e04a7da into cloudflare:master Jul 21, 2021
@agrover agrover deleted the redo-allowedips branch November 23, 2021 00:02
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.

2 participants