diff options
author | Bernhard Schmidt <berni@debian.org> | 2020-08-15 21:29:54 +0200 |
---|---|---|
committer | Bernhard Schmidt <berni@debian.org> | 2020-08-15 21:29:54 +0200 |
commit | 7c229d538824cb679351220ad8911f7b2daa7c23 (patch) | |
tree | 5c4d64b60da9018c7db3a9335a9787d326beade3 /TODO.IPv6 | |
parent | d3986a312f5fbcfd0e78e6b147eef419fb4e5f54 (diff) | |
parent | 1079962e4c06f88a54e50d997c1b7e84303d30b4 (diff) |
Update upstream source from tag 'upstream/2.5_beta1'
Update to upstream version '2.5~beta1'
with Debian dir d53f9a482ac24eb491a294b26c24bb1d87afad24
Diffstat (limited to 'TODO.IPv6')
-rw-r--r-- | TODO.IPv6 | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -21,7 +21,7 @@ TODO for IPv6 payload support 4.) do "ifconfig tun0 inet6 unplumb" or "ifconfig tun0 destroy" for Solaris, *BSD, ... at program termination time, to clean up leftovers - (unless tunnel persistance is desired). + (unless tunnel persistence is desired). For Solaris, only the "ipv6 tun0" is affected, for the *BSDs all tun0 stay around. @@ -47,7 +47,7 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 4b.) verify this - on FreeBSD, tun0 is auto-destroyed if created by opening /dev/tun (and lingers if created by "ifconfig tun0 create") - -> use for persistant tunnels on not-linux? + -> use for persistent tunnels on not-linux? * 2012-06-10 tun interface behaviour is documented in "man tun(4)" @@ -201,7 +201,7 @@ TODO for IPv6 transport support downstream. - Still done by flags, seems clean enough. - o implement comparison for mapped addesses: server in dual stack + o implement comparison for mapped addresses: server in dual stack listening IPv6 must permit incoming streams from allowed IPv4 peer, currently you need to pass eg: --remote ffff::1.2.3.4 - OpenVPN will compare all address of a remote |