Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Antonio, I certainly don’t disagree with you. However I think I’ve taken up enough bandwidth over this topic on Openvpn-devel. Thank you all. Marvin > On Apr 1, 2018, at 7:20 PM, Antonio Quartulli wrote: > >> On 02/04/18 10:12, Marvin Adeff wrote: >> Even on the internet

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

On 02/04/18 10:12, Marvin Adeff wrote: > Even on the internet I can tell country, ISP etc. Very useful for security > ACLs etc. Unless I’m completely mistaken, I don’t believe this is easily done > in ipv6. mostly because at this very moment Tunnel Brokers are widely used and they act as a

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Gert, Without invalidating the reason for your frustration, I am breathing a sigh of relief. As a complete aside, in some ways ipv4 is actually more useful to me in my work. In a private network I can tell where in the network the traffic is coming from. Even on the internet I can tell

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Hi, On Sun, Apr 01, 2018 at 12:21:53PM -0700, Marvin Adeff wrote: > I had not considered the extra work and code required to maintain both > versions. But I get it now. Here is the unfortunate position this puts us in: [..] Well, that part of my e-mail was a bit of frustration speaking - I've

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Ok, I’ll only discard the irate part ;-] I had not considered the extra work and code required to maintain both versions. But I get it now. Here is the unfortunate position this puts us in: We use OpenVPN for connection from 1000’s of devices located at customer facilities back to us. These

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Hi, On Sun, Apr 01, 2018 at 11:19:57AM -0700, Marvin Adeff wrote: > Think of us poor mail list lurkers. Practically gave this one a heart attack! > Not having seen that private reply, I hope that means I can discard the > long-ass (and quite irate) reply I was working on? Please share! >

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Think of us poor mail list lurkers. Practically gave this one a heart attack! Not having seen that private reply, I hope that means I can discard the long-ass (and quite irate) reply I was working on? Marvin (Sent from an ipv4 address) > On Apr 1, 2018, at 8:52 AM, Jonathan K. Bullard

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Hi, On Sun, Apr 1, 2018 at 11:34 AM, Gert Doering wrote: > Hi, > > On Sun, Apr 01, 2018 at 10:19:37AM -0400, Selva Nair wrote: >> On Sun, Apr 1, 2018 at 2:30 AM, Gert Doering wrote: >> >> > As discussed in trac #208 and on IRC with Antonio, OpenVPN 2.5

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Hi, On Sun, Apr 01, 2018 at 10:19:37AM -0400, Selva Nair wrote: > On Sun, Apr 1, 2018 at 2:30 AM, Gert Doering wrote: > > > As discussed in trac #208 and on IRC with Antonio, OpenVPN 2.5 will > > be IPv6-only. Removal of IPv4-related code and options will dramatically > >

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Hi, On Sun, Apr 1, 2018 at 2:30 AM, Gert Doering wrote: > As discussed in trac #208 and on IRC with Antonio, OpenVPN 2.5 will > be IPv6-only. Removal of IPv4-related code and options will dramatically > reduce code complexity, confusing options, bugs and user questions. >

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Hello, Jonathan K. Bullard, on dim. 01 avril 2018 06:17:55 -0400, wrote: > Either way, can anyone give an approximate release date for 2.5, so we > can have a time frame for the change? (Even a "not before" date would > be very helpful in evaluating the impact of these proposed changes.) I guess

Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options.

Hi, On Sun, Apr 1, 2018 at 2:30 AM, Gert Doering wrote: > As discussed in trac #208 and on IRC with Antonio, OpenVPN 2.5 will > be IPv6-only. Removal of IPv4-related code and options will dramatically > reduce code complexity, confusing options, bugs and user questions. >