[ipv6-wg] IPv6 Only Network at RIPE 67
- Previous message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
- Next message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tassos Chatzithomaoglou
achatz at forthnetgroup.gr
Wed Oct 16 14:58:08 CEST 2013
Just to clarify my initial statement, when i said the F5 vpn/ssl client doesn't work, i meant it doesn't work for an ipv4 destination, so it's probably a thing with nat64 and ssl. I don't know if this is the case with openvpn too. -- Tassos On 16/10/2013 3:44 μμ, Gert Doering wrote: > Hi, > > On Wed, Oct 16, 2013 at 01:30:30PM +0200, Jen Linkova wrote: >> Oh yes, we can add OpenVPN to the list of things which are broken but >> I have not looked closely.. > Just a small update on that: OpenVPN can be a bit confusing at times - > there is "OpenVPN the open source project, which is a *cli* program, > which should work over IPv6 transport just fine since version 2.3.0" and > "OpenVPN bundled with a GUI, hiding the cli program somewhere in the > back". > > On MacOS, there's at least 3 different versions of the Gui - Tunnelblick > (open source, comes with openvpn core 2.2 and 2.3 "inside", selectable > using options), and "OpenVPN connect", which is the commercially backed > client... which is nicely packaging everything, and, unfortunately, > hiding the logs somewhere so I couldn't find out yet why it's misbehaving. > > ... will get the answer for you :-) > > (On Android, both clients - OpenVPN for Android and OpenVPN Connect - > *should* work fine from the IPv6-only network... - same for OpenVPN > on iOS. If not, I'd like to hear more about it :-) ) > > Gert Doering > -- OpenVPN wrangler
- Previous message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
- Next message (by thread): [ipv6-wg] IPv6 Only Network at RIPE 67
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]