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

Restrictions on ingress CIDR for unknown ports #216

Closed
SteveL1 opened this issue Feb 19, 2020 · 10 comments
Closed

Restrictions on ingress CIDR for unknown ports #216

SteveL1 opened this issue Feb 19, 2020 · 10 comments
Labels
accepted Feature Request has been accepted and will be incorporated soon. enhancement waiting for confirmation Workaround/Fix applied, waiting for confirmation

Comments

@SteveL1
Copy link

SteveL1 commented Feb 19, 2020

Hi,

I'm trying to create a scenario that passes a security group that has a /0 ingress for known ports (eg 80/443) but fails if any other port has a range of less than /8.

is that possible to do?

@eerkunt
Copy link
Member

eerkunt commented Feb 19, 2020

Hi Steve,

This is not specific to a network right ? It is just the netmask, as I understand ?

So you are not looking for 10.0.0.0/8 (or any other /8 network) but specifically any network with /8 cidr ?

@SteveL1
Copy link
Author

SteveL1 commented Feb 19, 2020

Hi,

A specific network would be nice but for now just looking at netmask would be great.

Thanks :)

@eerkunt
Copy link
Member

eerkunt commented Feb 19, 2020

Ok then, that requires a new step :) I will change this issue as a Feature Request and implement it as soon as possible. I think this is a good idea.

Currently you can achieve this for a specific network, but just pure netmask is not supported till it is implemented :)

Few more days please :)

@eerkunt eerkunt added accepted Feature Request has been accepted and will be incorporated soon. enhancement labels Feb 19, 2020
@SteveL1
Copy link
Author

SteveL1 commented Feb 19, 2020

That's great, thanks for replying so quickly.

I was looking at using regex - something like

Then it must not have tcp protocol and port 0-65535 for "^([0-9]{1,3}\.){3}[0-9]{1,3}(\/([0-9]|[1-2][0-9]|3[0-2]))?$" regex

But I couldn't get it working. Also, I don't know how to get both parts (for the known and unknown ports) to work as one feature.

thanks :)

@eerkunt
Copy link
Member

eerkunt commented Feb 19, 2020

Unfortunately regex are not supported on that step, but that is another good idea ! :)

@SteveL1
Copy link
Author

SteveL1 commented Mar 23, 2020

Hi, I wonder if you've had a chance to look at this at all just yet?

Thanks
Steve

@eerkunt
Copy link
Member

eerkunt commented Mar 24, 2020

Hi @SteveL1 ,

It has been quite hectic days for the last few weeks. Apologies for the delay. :( I am planning to have a look to all issues around the end of this week.

@SteveL1
Copy link
Author

SteveL1 commented Mar 31, 2020

Hi,

I think those of us that are fortunate to still be working seem to be busier than before lockdown!!!

Appreciate your time looking at this :)

Thanks
Steve

@eerkunt
Copy link
Member

eerkunt commented Apr 13, 2020

Added this functionality within 894a36c. Will release today.

@eerkunt eerkunt added the waiting for confirmation Workaround/Fix applied, waiting for confirmation label Apr 13, 2020
@eerkunt
Copy link
Member

eerkunt commented Mar 9, 2021

Closing the issue since we think it is fixed and there is no response so far.

Please do not hesitate to create a new one if the problem still occurs.

@eerkunt eerkunt closed this as completed Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Feature Request has been accepted and will be incorporated soon. enhancement waiting for confirmation Workaround/Fix applied, waiting for confirmation
Projects
None yet
Development

No branches or pull requests

2 participants