2 years ago
Some applications just do not support IPv6. It would be great to enable these for private networking for example by auto forwarding a IPv4 port to an IPv6 port
2 Replies
2 years ago
☝️ +1 to this.
Although I absolutely love using IPv6, and a world where it only exists.
There are some services that just aren't IPv6 ready yet and may exhibit some odd behaviour.
For example:
Graph Node does look to support IPv6, but some weird things seem to be happening.
Working through with the Railway team to see if we can solve the IPv6 issues specific to my use cases.
But, an IPv4 option should be available within a project, even if it's opt-in to encourage the use of IPv6.
I don't think anything would need to change other than internal networking between services within a project, external networking (HTTP / TCP proxying can remain the same in theory).
2 years ago
+1 for this ... we need to have support for both while the entire web world transitions