-
-
Notifications
You must be signed in to change notification settings - Fork 309
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
launch firecracker and forward all traffic to it #64
Comments
if you're ok with having the VM always running, you could put some code in the VM that just sleeps your app until it gets a request. Otherwise this gets a lot harder to do in a stable way, I assume it takes 10+sec for the VM to launch, so all your initial traffic is going to time out by time the VM is up and running. |
would it still timeout with Firecracker's MicroVM startup time of 125ms? |
even better, may it is possible to get IP of the newly launched MicroVM and tell wireguard client to re-connect directly to the wireguard running in MicroVM, bypassing a shared wireguard instance. Could this work? |
@pirate thank you for your guide!!
I am trying to figure out the following scenario, which Fly.io describes, but never described in a way that can be implemented:
Why Boringtun? Because Windscribe released changes to add a script on client connect:
https://blog.windscribe.com/introducing-wireguard-76a1670700a6
https://github.com/Windscribe/boringtun
The text was updated successfully, but these errors were encountered: