Map static IPv4 address onto an exe VM
Right now VMs share IPv4 addresses behind a TLS and SSH proxy. This is part of making individual VMs cheap enough: IPv4 addresses are too expensive. However there are plenty of valid uses for a VM that needs a dedicated static IPv4 address. Add support for it.
3 Comments
What about mapping V6 as a middle ground for some use cases?
yes and you can shimmy an ipv4 client's ssh connection into an ipv6-only vm tennant thanks to
sshpiper(it's so nice seeing all this come together by experts- the author of sshpiper is in this same github org- software (I'm thankful for)) . Really nice also is by mapping V6 clients, if IPv6 only connection comes in, it has less hops to traverse if one wanted to allow that.Some old (2021) research notes using
sshpiper,gobetweenand various other projects to achieve ipv4 to ipv6 layer 4 proxying loadbalancing supporting ssh.https://docs.google.com/document/d/1aTL5bBjwEL1lsrrtUkwTfxLYt4qp0_q7Hgr2Oqy1ENc/edit?usp=sharing
Upvote. I need this support. My use case is for self-hosting Livekit which use webRTC and needs static IP. WebRTC is a common protocol for Voice AI. I'm deploying it on Linode right now, but I want to migrate it to exe.dev once it has static IP support.