-
# Feature Request
The built-in `sst.aws.Vpc` component is very appealing with support for ec2 nat, bastion, and `sst tunnel`. However, I'm looking for it to be a bit more flexible, particularly wit…
-
@SgtPooki @achingbrain @MarcoPolo
**Describe the bug**
Certain valid CIDR ranges for both IPv4 and IPv6 addresses cause a `SyntaxError` when processed by the `multiaddr` library.
**To Reprod…
-
I was using cidr-tools before. Looks the like the IPv4 exclude is working the same (yes it's much faster as mentionned) but I think the IPv6 exclude is broken. Because for me it creates a huge number …
-
### Check for previous/existing GitHub issues/module proposals
- [x] I have checked for previous/existing GitHub issues/module proposals.
### Check this module doesn't already exist in the module in…
-
### Description
The older `aws_security_group` ingress and egress blocks used to allow us to specify multiple both ipv4 and ipv6 cidr_blocks in the one config, and they accepted arrays with multipl…
-
IP ranges like 39.96.0.0/13 are presented in [aliyun-cidr-ipv4.txt](https://github.com/axpwx/IP-Data/blob/master/provider/aliyun-cidr-ipv4.txt) but not in [all-cidr-ipv4.txt](https://github.com/axpwx/…
-
This problem was found while looking for a workaround for issue #1, as I just wanted to one-time copy the list to my npm config.
The function "ip_range_to_cidr" is transforming any IP range to a 1 …
-
```
$ cidr merge "10.0.0.0/8" --exclude "192.168.2.0/24, 10.4.0.0/16" --exclude "10.6.0.0/16" "192.168.0.0/16"
10.0.0.0/14
10.5.0.0/16
10.7.0.0/16
10.8.0.0/13
10.16.0.0/12
10.32.0.0/11
10.6…
-
*Description*:
Last week Envoy just released support for trusted CIDR blocks when processing X-Forwarded-For headers.
It would be really useful to have a default configuration mode called "cloudfl…
-
**Description:**
We propose adding a CIDR (Classless Inter-Domain Routing) function to OpenSearch's Piped Processing Language (PPL) to provide built-in IP address range matching capabilities. This fe…