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

User defined whitelist filter #315

Open
LeeSmet opened this issue Jul 3, 2024 · 4 comments
Open

User defined whitelist filter #315

LeeSmet opened this issue Jul 3, 2024 · 4 comments
Labels
type_feature New feature or request

Comments

@LeeSmet
Copy link
Contributor

LeeSmet commented Jul 3, 2024

File based whitelist filter which specified allowed remotes (subnet/ip/pub key), which can talk to the local node. Ideally this includes src and dst port as well. By default, non listed addresses cause the packet to get dropped.

@LeeSmet LeeSmet added the type_feature New feature or request label Jul 3, 2024
@flokli
Copy link
Contributor

flokli commented Jul 5, 2024

Isn't this something that can already be solved on the nftables/iptables layer?

@iwanbk
Copy link
Member

iwanbk commented Jul 5, 2024

Isn't this something that can already be solved on the nftables/iptables layer?

maybe to make it work on different OS?

@flokli
Copy link
Contributor

flokli commented Jul 5, 2024

Probably, though there's some small distinctions here. Are we talking about networking traffic destined to the local node, messages in general, forwarding, …

@LeeSmet
Copy link
Contributor Author

LeeSmet commented Jul 10, 2024

This would be for packets destined to the local node yes. Essentially it would sit just before the tun interface for incoming packets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type_feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants