3 ms·

I'm not sure it can? My interpretation of what's been suggested is basically an ip you can port forward, as if you had a public ip. For example, let's say you

I'm not sure it can? My interpretation of what's been suggested is basically an ip you can port forward, as if you had a public ip. For example, let's say you want to run a minecraft server for your friends from your home. You use this hypothetical service to get an ip you can use, and tunnel the needed ports in to your network (and ultimately, your minecraft server). This couldn't be provided with a single ip, since at best that would limit you to selling off individual ports. The product becomes worthwhile if each customer has their own ip.

semi 3y ago
You can still do it off of one IP but it becomes more expensive as you now have to understand the protocol, and to route based on the handshake. For tls1.2, that's usually routing based on server name identifier in the ClientHello and you can do it pretty trivially For Minecraft.. you would probably need to write your own proxying logic. But as long as the protocol includes some info on what it's trying to connect to you could still do it. Alternatively you could do it like the old quakeworld spectator proxies and just write a custom Minecraft server people connect to that then presents a menu in game to pick a server that it then connects to.
- Libcat99 3y ago
  It's a very different product then. The fixed ip product more or less lets a user use it for anything they could with their own static ip. The single ip product only allows the end user to use protocols for which you have built forwarding logic. For some, like sip or http, this would be simple, but for others you would need a much higher understanding of the application protocol. One is a geeks Swiss army ip, the other is "now you can self host one of these 5 services, some or which might stop working if the application makes breaking changes."
- icedchai 3y ago
  That's a layer 7 proxy/router and would require a lot of application specific logic. If you want a static IP for your home network, you want it routed directly.

semi 3y ago

You can still do it off of one IP but it becomes more expensive as you now have to understand the protocol, and to route based on the handshake. For tls1.2, that's usually routing based on server name identifier in the ClientHello and you can do it pretty trivially For Minecraft.. you would probably need to write your own proxying logic. But as long as the protocol includes some info on what it's trying to connect to you could still do it. Alternatively you could do it like the old quakeworld spectator proxies and just write a custom Minecraft server people connect to that then presents a menu in game to pick a server that it then connects to.

Libcat99 3y ago
It's a very different product then. The fixed ip product more or less lets a user use it for anything they could with their own static ip. The single ip product only allows the end user to use protocols for which you have built forwarding logic. For some, like sip or http, this would be simple, but for others you would need a much higher understanding of the application protocol. One is a geeks Swiss army ip, the other is "now you can self host one of these 5 services, some or which might stop working if the application makes breaking changes."
icedchai 3y ago
That's a layer 7 proxy/router and would require a lot of application specific logic. If you want a static IP for your home network, you want it routed directly.