On Fri, 2017-11-03 at 21:38 +0100, Fabian Zimmermann wrote: > Hi, > > on your website you write: > > -- > At the time of writing much of the configuration for Legacy IP > addressing and routes is understood and implemented. IPv6 is not yet > implemented, and test reports from someone with an IPv6-capable server > would be greatly appreciated. > -- > > well, I would be pleased to help you. We use an Ipv6 enabled Juniper VPN > and currently there is no solution to get IPv6 at Linux. Mac&Win is working > like a charm. > > Just tell me, what I can do. Oh, that's a coincidence; I was just talking to someone else about this the other day *and* they were offering to set up a test server for me. It actually ends up being a new protocol ? it's no longer the old Network Connect protocol that I already support in OpenConnect. That's a relatively non-trivial coding task, but we do understand the protocol and it's a lot saner than the existing Network Connect is. It's mostly EAP-based for authentication. Are you up for that? I'd be happy to share my understanding of the protocol and give pointers... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4938 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20171103/1a933d0f/attachment.bin>
