# Edge tunnel router does not support ipv6 **URL:** \ **Category:** Tunneler Apps\ **Created:** [March 25, 2025, 5:29am UTC](https://openziti.discourse.group/t/edge-tunnel-router-does-not-support-ipv6/4239 "2025-03-25T05:29:09Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [March 25, 2025, 5:29am UTC](https://openziti.discourse.group/t/edge-tunnel-router-does-not-support-ipv6/4239/1 "2025-03-25T05:29:09Z")
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" ---
**Author:** ![scareything](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/scareything/32/106_2.png) [@scareything](https://openziti.discourse.group/u/scareything)\ **Post date:** [March 25, 2025, 10:21am UTC](https://openziti.discourse.group/t/edge-tunnel-router-does-not-support-ipv6/4239/2 "2025-03-25T10:21:57Z")
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 ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [March 31, 2025, 1:06am UTC](https://openziti.discourse.group/t/edge-tunnel-router-does-not-support-ipv6/4239/3 "2025-03-31T01:06:43Z")
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 ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/2X/1/10a97f566e8205b79fff001abfe322516c35b34a.png) ---
**Author:** ![tbrtje](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/tbrtje/32/3350_2.png) [@tbrtje](https://openziti.discourse.group/u/tbrtje)\ **Post date:** [April 6, 2025, 12:49pm UTC](https://openziti.discourse.group/t/edge-tunnel-router-does-not-support-ipv6/4239/4 "2025-04-06T12:49:33Z")
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? ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [April 6, 2025, 2:31pm UTC](https://openziti.discourse.group/t/edge-tunnel-router-does-not-support-ipv6/4239/5 "2025-04-06T14:31:03Z")
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? > > > Hi there, > when trying to setup a router to listen to ipv6-traffic the router fai…ls to start with the following error message. > > I've tried setting up single ipv6-addresses, but they also result in the same error message. > Removing the braces also does not help. > > FATAL ziti/router.(\*Router).startXlinkListeners: error creating Xlink listener (error loading listener configuration (error parsing 'bind' address in listener config (address (tls:\[::\]:3022) not parsed))) ---
**Author:** ![McGonagall666](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@McGonagall666](https://openziti.discourse.group/u/McGonagall666)\ **Post date:** [April 8, 2025, 1:51am UTC](https://openziti.discourse.group/t/edge-tunnel-router-does-not-support-ipv6/4239/6 "2025-04-08T01:51:00Z")
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