-
**Describe the bug**
Prometheus exporter TCP ports (20201, 20202) are enabled by default on Ops Agent, which causes problems for users wanting to bind to those ports for other purposes, or reduce n…
-
With [QUIC](https://en.wikipedia.org/wiki/QUIC) becoming a thing, it's reasonable that soon services that traditionally operated over TCP will start operating over UDP. Think `HTTP/3` and `gRPC`.
I…
-
The command has the following syntax
`forwarder port-forward [] [][...`
and allows for copying TCP connections to forwarder.
-
**Is your feature request related to a problem? Please describe.**
I cannot configure Vault CR to create a service available under port 443 pointing to the pod API on a different port.
Vault per d…
-
**What is missing?**
The k8ssandra-operator defined in the helm chart binds three TCP ports but only one of those ports (the webhook) is defined in the deployment's pod spec.
**Why do we need it?**…
-
I tried to start caddy with `servers { protocols h3 }` in global settings. However, caddy seems still trying to bind to tcp port.
My Caddyfile is something like this:
```
{
debug
servers {
p…
ha-ku updated
9 months ago
-
I wonder if it's possible to share the outbound 443 port with other services by using something like L4 proxy with SNI (Let's say HAProxy)? Does Cloak respect `proxy-protocol` headers? I think neither…
-
IPv4 TCP&UDP both work. IPv6 only works with TCP.
Here's the log:
```
INFO(tun2socks): UDP/IPv6: from device 95 bytes
ERROR(BDatagram): bind failed
ERROR(SocksUdpClient): Failed to bind the UDP…
-
### Detailed Description of the Problem
I'm using HAProxy with some LUA code which performs body rewrites on HTML, I'm following the pattern described here which uses httpclient to send to a frontend…
-
In `NioAsyncServerSocket.bind(SocketAddress, int)` the channel socket is bound with `serverSocketChannel.bind(localAddress, backlog)` which binds the socket exclusively to `localAddress`. If the serve…