References: <20180401063058.23913-1-gert@...1296...> <20180401153422.GE69387@...1296...> <20180401183928.GH69387@...1296...> <9FAA40DB-C459-47AF-92B3-B02FD769886E@...277...> <20180401193456.GI69387@...1296...> <8EB0586C-A6D5-48D8-AC4A-35A0836F3197@...277...> From: Antonio Quartulli Message-ID: Date: Mon, 2 Apr 2018 10:20:47 +0800 MIME-Version: 1.0 In-Reply-To: <8EB0586C-A6D5-48D8-AC4A-35A0836F3197@...277...> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="klmyVIqHcxWh1yWtVpxVmgpChRjIg7bLz" Subject: Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: openvpn-devel@lists.sourceforge.net This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --klmyVIqHcxWh1yWtVpxVmgpChRjIg7bLz Content-Type: multipart/mixed; boundary="TJR03TgVmchC3vxGz6ILwky8hLXYrKtNJ"; protected-headers="v1" From: Antonio Quartulli To: openvpn-devel@lists.sourceforge.net Message-ID: Subject: Re: [Openvpn-devel] [PATCH] Depreciate IPv4-related options. References: <20180401063058.23913-1-gert@...1296...> <20180401153422.GE69387@...1296...> <20180401183928.GH69387@...1296...> <9FAA40DB-C459-47AF-92B3-B02FD769886E@...277...> <20180401193456.GI69387@...1296...> <8EB0586C-A6D5-48D8-AC4A-35A0836F3197@...277...> In-Reply-To: <8EB0586C-A6D5-48D8-AC4A-35A0836F3197@...277...> --TJR03TgVmchC3vxGz6ILwky8hLXYrKtNJ Content-Language: en-US Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 02/04/18 10:12, Marvin Adeff wrote: > Even on the internet I can tell country, ISP etc. Very useful for securit= y ACLs etc. Unless I=E2=80=99m completely mistaken, I don=E2=80=99t believe= this is easily done in ipv6.=20 mostly because at this very moment Tunnel Brokers are widely used and they act as a "proxy", effectively covering the real location of the client host. Many websites just show you (client) as connecting from the country where your Tunnel Broker is located. When using native IPv6 this problem does not exists anymore. Therefore, the proper way to get over this "limitation" (even though I don't think is a real problem, but this is of course my perspective) is to speed up the transition and move everybody over native IPv6 (which is something we can't achieve if we continue to be "afraid" of using IPv6 in our everyday life). Cheers, --=20 Antonio Quartulli --TJR03TgVmchC3vxGz6ILwky8hLXYrKtNJ-- --klmyVIqHcxWh1yWtVpxVmgpChRjIg7bLz Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEERdCuyFSHc3WdqS4EB6U8WA7yzXQFAlrBk4YACgkQB6U8WA7y zXRmIhAAofogTuoRIwCHypvVGhTkBnbfXZHcrehhQmcc0xOxan4CpPiWO2RPpCB6 8jOWAFkFwzpLO+DVH7gKOLyTeYgIepiTqaaX48a7ec9xl5/OQeeZ8RAAh3FKS9H6 XAbEGoUuCWQC96c3yZXePTnHfdAM97Z0HKSrqqamkzWCTmF+8fH5uEMyT8NT2dHc 6lbk8CrTeoiOWLWn0enRl43e2RCITGam/qmSLMDJL/uSaNy7M2b0KhPmCAZms2WT Itl6CJQJKlKy16fyDpkaVIJSKLKOnnYfT21uX8BnzztIpjf1oXySMUDPLamY+4Sa BcPFJECLh9jAeLuiwMMG5iaGBD5G3NhvvawKD48qBdBES2xty2kWs0RFHZy/aWaR XnHxgqEvE+GHQknRC3cnVZhmGaUDTfWmsl/z+6yUclswyPfwhY7x5Y8TynlQqVaa rGteggv1NCbVikNcxYCEipRxDTzIJmg0YGA/pLliEaGWmq5LDeqQzdoswtl7YxbL DgDmiNvjXlta+xJ8ohT56ve9P/VHLKdj6mRaU38XXrTlFD40Tdt6M0szHrHM+7Ab WzxjnWqZtWUfKrSvOKv3u3psc6Z5H33MpIIR+feTFFlyBm6yXrAOWfzINurMDweG LDRXgrEUN1Jjizq00Mq/6+xQdMCvd37RPMhDQRvbhnjqhPRmOzc= =O1ia -----END PGP SIGNATURE----- --klmyVIqHcxWh1yWtVpxVmgpChRjIg7bLz--