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.

Sign up for GitHub

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

Jump to bottom

support all protocol numbers #812

Open
Tracked by #555
olasaadi99 opened this issue Aug 18, 2024 · 3 comments
Open
Tracked by #555

support all protocol numbers #812

olasaadi99 opened this issue Aug 18, 2024 · 3 comments
Assignees
@olasaadi99
Labels
aws
Milestone
v0.8

Comments

@olasaadi99
Copy link
Contributor

No description provided.

@olasaadi99 olasaadi99 mentioned this issue Aug 18, 2024
Closed
5 tasks
@olasaadi99 olasaadi99 self-assigned this Aug 18, 2024
@zivnevo zivnevo added the aws label Aug 19, 2024
@zivnevo zivnevo added this to the v0.7 milestone Aug 19, 2024
@olasaadi99
Copy link
Contributor Author

support https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml protocol numbers for aws sg and nacl

@zivnevo
Copy link
Member

zivnevo commented Sep 17, 2024

Should also check if in IBM VPCs, setting protocols to all allows protocols which are not TCP, UDP or ICMP.

@zivnevo
Copy link
Member

zivnevo commented Sep 19, 2024

Made an experiment with live VPCs (thanks @kyorav), sending SCTP traffic when "all" protocols are allowed in both NACLs and SGs.
Conclusions:

  1. In AWS: SCTP traffic is allowed to flow - SCTP connections can be established.
  2. In IBM Cloud: Attempts to make SCTP connection timed out.

So indeed, the two clouds interpret "all" protocols differently.

@zivnevo zivnevo modified the milestones: v0.7, v0.8 Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olasaadi99 olasaadi99

Labels
aws
Projects
None yet
Milestone
v0.8
Development

No branches or pull requests
2 participants
@zivnevo @olasaadi99