Search Results for "ips"

...Crowdsec shouldn't, and didn't crash any production so far we know, but some features might be missing or undergo evolutions. IP Blocklists are limited to very-safe-to-ban IPs only (~5% of the global database so far, will grow soon). A modern behavior detection system, written in Go. It stacks on Fail2ban's philosophy, but uses Grok patterns & YAML grammar to analyse logs, a modern decoupled approach (detect here, remedy there) for Cloud/Containers/VM based infrastructures. Once detected you can remedy threats with various bouncers (block, 403, Captchas, etc.) and blocked IPs are shared among all users to further improve their security. ...

...Weron allows developers to create scalable mesh or point-to-point networks for applications like remote desktop, Kubernetes access, or collaborative tools—all without requiring public IPs or complicated port forwarding.

...Every machine in the network runs NetBird Agent (or Client) that manages WireGuard. Every agent connects to Management Service that holds network state, manages peer IPs, and distributes network updates to agents (peers). NetBird agent uses WebRTC ICE implemented in pion/ice library to discover connection candidates when establishing a peer-to-peer connection between machines.

...Launch kubelet with network plugins set to cni (--network-plugin=cni), the cni directories configured (--cni-config-dir and --cni-bin-dir) and node ip set to the primary IPv4 address of the primary ENI for the instance (--node-ip=$(curl http://169.254.169.254/latest/meta-data/local-ipv4)). It is also recommended that you set --max-pods equal to (the number of ENIs for the instance type × (the number of IPs per ENI - 1)) + 2; for details, see vpc_ip_resource_limit.go. Setting --max-pods will prevent scheduling that exceeds the IP address resources available to the kubelet. The Amazon VPC CNI plugin for Kubernetes supports a number of configuration options, which are set through environment variables. The following environment variables are available, and all of them are optional.

...Association rules between dns and ipset. dns cache support. Custom dns record. IPSet management (linux kernel version >= 2.6.32). Add ip/cidrs from rule files on startup. Add resolved ips for domains from rule files by dns forwarding server. Serve HTTP and socks5 on the same port. Periodical availability checking for the forwarder.