I have an ipv6 virtual machine. I start two tunnel routers, one as dial and one as bind. When I access the service's intercept ipv6 address, it prompts "Couldn't connect to server". If the service host is ipv6, it prompts "too many colons in address"
Hi,
Which tunnelers are you running on each end of the connection? Can you share your service configuration and tunneler logs that show your connection attempts?
Thanks
I'm very sorry, the network has been down recently and has not been repaired yet. I drew a picture. I will send you the log when the network is repaired. ip is just an example
Hi there,
I am also facing the issue of setting up an ipv6-based edge router, but I cannot even start the router, when i configure it to listen on tls:[::]:port.
Have you been able to resolve your issues?
Hi @tbrtje, welcome to the community and to OpenZiti. I commented on your GitHub issue about this. Short of it is the tls:0.0.0.0:3022 format will listen on both ipv4 and ipv6, but will at least allow you to start the router. Hopefully that's good enough for now?
I think our problem is different. I checked the log and found that the ipv6 address intercepted by intercept cannot be added to iptables. When I check iptables -t mangle -L -v -n, I can see that the ipv4 address cannot see the ipv6 address. The ipv6 address should use ip6tables, but ziti does not seem to be adapted.
I guess the problem of "too many colons in address" is that there is no distinction between ipv4 and ipv6 somewhere, and ipv6 should add