Replies: 1 comment
-
It's not a high priority right now, just because there's a workaround of running two innernet networks (so two interfaces), which I've done in the past with success. You might also be able to define your innernet CIDR as an IPv4-mapped-IPv6 range, and possibly trick IPv4 applications into running successfully on that stack, but I haven't experimented with that myself. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello there~
I'm trying to use innernet to create my kubernetes edge-cluster, then I found that I can't create an interface with both ipv4 and ipv6 enabled, the
innernet-server
saidyour network CIDR should be in the RFC1918 IPv4 (10/8, 172.16/12, or 192.168/16), or RFC4193 IPv6 (fd00::/8) ranges.
.So is dualstack on the roadmap?
Beta Was this translation helpful? Give feedback.
All reactions