public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Fernando Gont <fernando@gont•com.ar>
To: Jan Engelhardt <jengelh@inai•de>
Cc: netdev <netdev@vger•kernel.org>
Subject: Re: VPN traffic leaks in IPv6/IPv4 dual-stack networks/hosts
Date: Wed, 28 Nov 2012 16:57:21 -0300	[thread overview]
Message-ID: <50B66CA1.5050907@gont.com.ar> (raw)
In-Reply-To: <alpine.LNX.2.01.1211271703530.8184@nerf07.vanv.qr>

On 11/27/2012 01:10 PM, Jan Engelhardt wrote:
>> For a project such as OpenVPN, a (portable) fix might be non-trivial.
> 
> If the VPN server does not even advertise to-be-secured IPv6 prefixes, 
> any client-side fix is questionable. 

If the VPN is supposed to secure all traffic, and the VPN just fails to
support v6, then for me, it's questionable to have your traffic leak out
the VPN just because of that lack of IPv6 support.

But YMMV, of couse.

Cheers,
-- 
Fernando Gont
e-mail: fernando@gont•com.ar || fgont@si6networks•com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1

  reply	other threads:[~2012-11-28 19:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 14:54 VPN traffic leaks in IPv6/IPv4 dual-stack networks/hosts Fernando Gont
2012-11-27 16:04 ` Eric Dumazet
2012-11-27 16:07   ` Fernando Gont
2012-11-27 16:22     ` Michal Kubeček
2012-11-27 16:10 ` Jan Engelhardt
2012-11-28 19:57   ` Fernando Gont [this message]
2012-11-28 20:06     ` Jan Engelhardt
2012-11-28 20:14       ` Fernando Gont
2012-11-28 21:37         ` Jan Engelhardt
2012-11-29  2:29           ` Fernando Gont
2012-11-29  3:15             ` Jan Engelhardt
2012-11-29  4:38               ` Fernando Gont

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50B66CA1.5050907@gont.com.ar \
    --to=fernando@gont$(echo .)com.ar \
    --cc=jengelh@inai$(echo .)de \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox