Is it possible to assign, say a
/24 (and so on) IP6 (or IP4) to a single Fly app?
I presume that using IP4 may be charged per IP per mo, while IP6 would be free…?
If assigning subnets isn’t supported currently, does Fly intend to in near future?
We’ve thought about building this, at least for IPv6. What are you trying to do?
Vend those addresses out to downstream clients, as a way to ID traffic coming from them, and apply whatever policies as set by them. The appeal is, such a mechanism would be protocol agnostic… I realise that today fly only supports TCP (over 4 and 6) and UDP (over 4) transports.
The usecase I have for IPv6 UDP (not solvable with IPv4) is transparently proxying TCP/UDP connections.
For ex, our DNS resolver always answers with our app’s fly IPs for all DNS requests from our clients. That is, say example.com from client-A gets 2a09:8080:1::abcd, while example.com from client-B gets 2a09:8080:1::1234 (assuming both of those IPv6 are assigned to our fly app).
Then, when a UDP/TCP request from client-A hits 2a09:8280:1::abcd, the fly app (reading from the mapping set by th…