Repository navigation
Replies: 4 comments 4 replies
|
Wow, thank you for reaching out and using uncloud! Yes, there is definitely an interest in L4 ingress. Please see a corresponding issue: #108. You could probably also see this TODO: I haven't thought much about this feature yet and I can think about it and share my thoughts in the next few days. In the meantime, can you please share a bit more details on your decision of not using the host network. I thought that actually might be a good idea to not need to recreate caddy containers when a new port needs to be proxied. Or maybe bind a fixed range of ports upfront and then ip/nftables to map the required ports to a random available one. |
|
Hey @xenolf One question, I thought SNI or specifically ESNI was replaced with ECH. I think caddy supports ECH which seems to be the secure approach to achieve SNI. Not sure if this helps ECH |
|
+1 — another concrete L4 use case: exposing RDP (3389/TCP) for Today we expose it with So a vote for plain TCP/UDP passthrough (no SNI required) as a first-class case alongside the SNI/ |
|
put this link in the issue as well, but the above is (easily) doable now with Uncloud, https://miek.nl/2026/april/25/uncloud-l4/ |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
first of all thank you very much for this project - I am really enjoying using it for a personal project of mine.
For my project I require TLS passthrough for mTLS as well as UDP passthrough for a service and I went ahead to implement this feature for myself. My question would be if you would be open to accepting a contribution for this feature or if it is still off in the distance for you and you would like to focus on different features 😄
In general the architectural decisions were:
I just wanted to gauge interest if I put in the effort to polish it up for a pull request or keep it to myself.
Thank you!
All reactions