All of lore.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 17:14:02 -0300	[thread overview]
Message-ID: <50B6708A.8020701@gont.com.ar> (raw)
In-Reply-To: <alpine.LNX.2.01.1211282102240.11155@nerf07.vanv.qr>

On 11/28/2012 05:06 PM, Jan Engelhardt wrote:
>> 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.
> 
> Well, what I am saying is that a server may not
> be conveying "all", but only "0.0.0.0/0".

In such scenarios, doing nothing about IPv6 would be an oversight/error,
since IPv4 and IPv6 do not operate isolated from each other.

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 20:14 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
2012-11-28 20:06     ` Jan Engelhardt
2012-11-28 20:14       ` Fernando Gont [this message]
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=50B6708A.8020701@gont.com.ar \
    --to=fernando@gont.com.ar \
    --cc=jengelh@inai.de \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.