Expected behavior:
using correct config to connect kcptun via ipv6
Actual behavior:
ipv6 address format lost a [], need to add [] when using ipv6 address.
currently, remoteaddr was configured by add IP address directly to kcptun config, thats works fine when using ipv4, but doesn't work in ipv6, because kcptun require add [], like [2001:19f0:7001:15ac:5300:00ff:fe61:6f48:6a89] when using ipv6 address.
I copy the kcpclient from the ShadowsocksX-NG package folder and test it with a custom json config file, only adding [] in ipv6 address and it works fine.
Steps to reproduce:
connect to a ssserver via ipv6.
kcptun_client.log
log with no [] in current version, ipv6 won't work.(the ipv6 address in the log is a fork one )
System and Shadowsocksx-NG version:
Expected behavior: using correct config to connect kcptun via ipv6
Actual behavior:
ipv6 address format lost a
[]
, need to add[]
when using ipv6 address.currently,
remoteaddr
was configured by add IP address directly to kcptun config, thats works fine when using ipv4, but doesn't work in ipv6, because kcptun require add[]
, like[2001:19f0:7001:15ac:5300:00ff:fe61:6f48:6a89]
when using ipv6 address.I copy the kcpclient from the ShadowsocksX-NG package folder and test it with a custom json config file, only adding
[]
in ipv6 address and it works fine.Steps to reproduce:
connect to a ssserver via ipv6.
kcptun_client.log
log with no
[]
in current version, ipv6 won't work.(the ipv6 address in the log is a fork one )log with
[]
in ipv6 address, works. note the last line tell us the connection is established.