Maple Add IPv6 outbound support

Currently Maple does not support IPv6 address, please add IPv6 support, which is very useful in CERNET.

目前Maple不支持IPv6地址，请添加对IPv6的支持，这在教育网中很有用。

Apr 05 '21 10:04 ghost

AFAIK Leaf does not support IPv6 yet, see https://github.com/eycorsican/leaf/issues/13#issuecomment-723417867 . Maple could not implement it without Leaf supporting it first. Besides, neither iLeaf nor aleaf provides an IPv6 address for local VPN interface. May I know if Leaf itself works in your network environment? If so, please provide more details about your use cases in that network environment. Otherwise, please consider reporting a feature request to Leaf.

Apr 05 '21 12:04 bdbai

See https://github.com/eycorsican/leaf/issues/126

Apr 14 '21 13:04 ghost

It seems that IPv6 support in Leaf is ready and merged into Maple. @waynon Could you test out the main branch to see if IPv6 works? Unfortunately I have no access to IPv6 network.

May 16 '21 06:05 bdbai

I am going to close this issue since IPv6 support is already merged. Please let me know in case any related problems still exist.

May 17 '21 10:05 bdbai

IPv6 address is still not supported, both in official release 0.3.0 and my custom build.

May 18 '21 13:05 ghost

Please reopen the issue.

May 18 '21 13:05 ghost

IPv6 address is still not supported, both in official release 0.3.0 and my custom build.

How did you find that IPv6 does not work? Please explain what you have done if possible.

May 18 '21 13:05 bdbai

IPv4 config that is working:

[General]
# Log are for debug only
loglevel = error
# Do not remove tun-fd option
tun-fd = 233
dns-server = 223.5.5.5, 114.114.114.114

[Proxy]
VMess = vmess, 107.173.87.xxx, xxx, username=xxxxxxxx

[Proxy Group]
Fallback = VMess, interval=600, timeout=5

[Rule]
FINAL, Fallback

IPv6 config that is not working:

[General]
# Log are for debug only
loglevel = error
# Do not remove tun-fd option
tun-fd = 233
dns-server = 223.5.5.5, 114.114.114.114

[Proxy]
VMess = vmess, 2001:470:1f04:316::2, xxx, username=xxxxxxxx

[Proxy Group]
Fallback = VMess, interval=600, timeout=5

[Rule]
FINAL, Fallback

The only difference is the IP address. It's working in Leaf (proxy mode).

Logs:

[37m[2021-05-18 23:25:32][[37mDEBUG[0m[37m] added udp session 192.168.3.1:58004 -> 198.18.0.2:443 (1)[0m
[90m[2021-05-18 23:25:32][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:32][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:58004 -> www.facebook.com:443[0m
[90m[2021-05-18 23:25:32][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:32][[37mDEBUG[0m[37m] dispatch udp 192.168.3.1:58004 -> www.facebook.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
线程 0x6f9c 已退出，返回值为 0 (0x0)。
[37m[2021-05-18 23:25:34][[37mDEBUG[0m[37m] added udp session 192.168.3.1:52063 -> 239.255.255.250:1900 (1)[0m
[90m[2021-05-18 23:25:34][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:34][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:52063 -> 239.255.255.250:1900[0m
[90m[2021-05-18 23:25:34][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:34][[37mDEBUG[0m[37m] dispatch udp 192.168.3.1:52063 -> 239.255.255.250:1900 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:34][[90mTRACE[0m[90m] netstack tcp new 192.168.3.1:56203[0m
[90m[2021-05-18 23:25:34][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:34][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:56203 -> heartbeat.dm.origin.com:80[0m
[90m[2021-05-18 23:25:34][[90mTRACE[0m[90m] active proxied tcp connections +1: 1[0m
[90m[2021-05-18 23:25:34][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:34][[37mDEBUG[0m[37m] dispatch tcp 192.168.3.1:56203 -> heartbeat.dm.origin.com:80 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:34][[90mTRACE[0m[90m] netstack tcp shutdown 192.168.3.1:56203[0m
[90m[2021-05-18 23:25:34][[90mTRACE[0m[90m] active proxied tcp connections -1: 0[0m
[90m[2021-05-18 23:25:34][[90mTRACE[0m[90m] netstack tcp drop 192.168.3.1:56203[0m
[37m[2021-05-18 23:25:37][[37mDEBUG[0m[37m] added udp session 192.168.3.1:52063 -> 239.255.255.250:1900 (1)[0m
[90m[2021-05-18 23:25:37][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:37][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:52063 -> 239.255.255.250:1900[0m
[90m[2021-05-18 23:25:37][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:37][[37mDEBUG[0m[37m] dispatch udp 192.168.3.1:52063 -> 239.255.255.250:1900 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:38][[90mTRACE[0m[90m] netstack tcp new 192.168.3.1:56205[0m
[90m[2021-05-18 23:25:38][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:38][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:56205 -> api.github.com:443[0m
[90m[2021-05-18 23:25:38][[90mTRACE[0m[90m] active proxied tcp connections +1: 1[0m
[90m[2021-05-18 23:25:38][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:38][[37mDEBUG[0m[37m] dispatch tcp 192.168.3.1:56205 -> api.github.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:38][[90mTRACE[0m[90m] netstack tcp shutdown 192.168.3.1:56205[0m
[90m[2021-05-18 23:25:38][[90mTRACE[0m[90m] active proxied tcp connections -1: 0[0m
[90m[2021-05-18 23:25:38][[90mTRACE[0m[90m] netstack tcp drop 192.168.3.1:56205[0m
[90m[2021-05-18 23:25:39][[90mTRACE[0m[90m] netstack tcp new 192.168.3.1:56206[0m
[90m[2021-05-18 23:25:39][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:39][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:56206 -> heartbeat.dm.origin.com:80[0m
[90m[2021-05-18 23:25:39][[90mTRACE[0m[90m] active proxied tcp connections +1: 1[0m
[90m[2021-05-18 23:25:39][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:39][[37mDEBUG[0m[37m] dispatch tcp 192.168.3.1:56206 -> heartbeat.dm.origin.com:80 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:39][[90mTRACE[0m[90m] netstack tcp shutdown 192.168.3.1:56206[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] active proxied tcp connections -1: 0[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] netstack tcp drop 192.168.3.1:56206[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] added udp session 192.168.3.1:58004 -> 198.18.0.2:443 (1)[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:58004 -> www.facebook.com:443[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] dispatch udp 192.168.3.1:58004 -> www.facebook.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] allocate 198.18.0.14 for clients4.google.com[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] netstack tcp new 192.168.3.1:56207[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:56207 -> clients4.google.com:443[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] active proxied tcp connections +1: 1[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] dispatch tcp 192.168.3.1:56207 -> clients4.google.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] netstack tcp shutdown 192.168.3.1:56207[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] active proxied tcp connections -1: 0[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] netstack tcp drop 192.168.3.1:56207[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] netstack tcp new 192.168.3.1:56208[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:56208 -> clients4.google.com:443[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] active proxied tcp connections +1: 1[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] dispatch tcp 192.168.3.1:56208 -> clients4.google.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] netstack tcp shutdown 192.168.3.1:56208[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] active proxied tcp connections -1: 0[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] netstack tcp drop 192.168.3.1:56208[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] allocate 198.18.0.15 for beacons4.gvt2.com[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] added udp session 192.168.3.1:63366 -> 198.18.0.15:443 (1)[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:63366 -> beacons4.gvt2.com:443[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] dispatch udp 192.168.3.1:63366 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] added udp session 192.168.3.1:63366 -> 198.18.0.15:443 (1)[0m
[90m[2021-05-18 23:25:40][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:40][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:63366 -> beacons4.gvt2.com:443[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] dispatch udp 192.168.3.1:63366 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp new 192.168.3.1:56210[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:56210 -> beacons4.gvt2.com:443[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] active proxied tcp connections +1: 1[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] dispatch tcp 192.168.3.1:56210 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp shutdown 192.168.3.1:56210[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] active proxied tcp connections -1: 0[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp drop 192.168.3.1:56210[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp new 192.168.3.1:56211[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp new 192.168.3.1:56212[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:56212 -> beacons4.gvt2.com:443[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:56211 -> beacons4.gvt2.com:443[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] active proxied tcp connections +1: 1[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] active proxied tcp connections +1: 2[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] dispatch tcp 192.168.3.1:56212 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] dispatch tcp 192.168.3.1:56211 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp shutdown 192.168.3.1:56212[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] active proxied tcp connections -1: 1[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp shutdown 192.168.3.1:56211[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] active proxied tcp connections -1: 0[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp drop 192.168.3.1:56212[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp drop 192.168.3.1:56211[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp new 192.168.3.1:56213[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:56213 -> beacons4.gvt2.com:443[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] active proxied tcp connections +1: 1[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] dispatch tcp 192.168.3.1:56213 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp shutdown 192.168.3.1:56213[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] active proxied tcp connections -1: 0[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] added udp session 192.168.3.1:63366 -> 198.18.0.15:443 (1)[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] netstack tcp drop 192.168.3.1:56213[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:63366 -> beacons4.gvt2.com:443[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] dispatch udp 192.168.3.1:63366 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] added udp session 192.168.3.1:52063 -> 239.255.255.250:1900 (2)[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:52063 -> 239.255.255.250:1900[0m
[90m[2021-05-18 23:25:41][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:41][[37mDEBUG[0m[37m] dispatch udp 192.168.3.1:52063 -> 239.255.255.250:1900 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m
[37m[2021-05-18 23:25:42][[37mDEBUG[0m[37m] added udp session 192.168.3.1:63366 -> 198.18.0.15:443 (1)[0m
[90m[2021-05-18 23:25:42][[90mTRACE[0m[90m] pick route failed: no matching rules[0m
[37m[2021-05-18 23:25:42][[37mDEBUG[0m[37m] picked default route [VMess] for 192.168.3.1:63366 -> beacons4.gvt2.com:443[0m
[90m[2021-05-18 23:25:42][[90mTRACE[0m[90m] socket bind 172.23.101.158:0[0m
[37m[2021-05-18 23:25:42][[37mDEBUG[0m[37m] dispatch udp 192.168.3.1:63366 -> beacons4.gvt2.com:443 to [VMess] failed: all attempts failed, last error: The system detected an invalid pointer address in attempting to use a pointer argument in a call. (os error 10014)[0m

May 18 '21 15:05 ghost

Added in v0.9.0.

Apr 01 '23 10:04 bdbai