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

Security Group todos: #1470

Open
2 of 4 tasks
nerdalert opened this issue Sep 28, 2023 · 0 comments
Open
2 of 4 tasks

Security Group todos: #1470

nerdalert opened this issue Sep 28, 2023 · 0 comments

Comments

@nerdalert
Copy link
Member

nerdalert commented Sep 28, 2023

Add SecGroup issues here please:

  • ALL ICMP currently only allows icmpv4. Probably should break it into ALL ICMPv4 and ALL ICMPv6 respectively.
  • Address family mixing will get fairly complicated. For early going keeping address families separated might make the most sense even though there is some support by making the protocol families explicit. An example is permit that passes validation but bombs in the datapath is add rule inet nexodus nexodus-inbound meta nfproto ipv4 ip saddr 0200::/8 udp dport 123-456 iifname wg0 counter accept" failed: exit status 1. Some scenarios can handle both but some can't due to the user space tool api not capable of being agnostic 😵
  • The following isn't getting instantiated in the data path: [{"from_port":123,"ip_protocol":"ipv4","ip_ranges":["100.64.0.0/10"],"to_port":456}]. tcp works but ipv6 || ipv4 are missing. Add e2e with the fix.
  • Add three new e2e rule tests for all scenarios, starting with 1. [Protocol, *, *] 2. [Protocol, Port, ] 3. [Protocol, Port, IP_Ranges]. [, *, *] is already tested. Skip the actual connection attempts for now since it will get a bit redundant, just make sure a 422 isn't returned.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant