From: Eric Dumazet <eric.dumazet@gmail.com>
To: Fernando Gont <fernando@gont.com.ar>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: VPN traffic leaks in IPv6/IPv4 dual-stack networks/hosts
Date: Tue, 27 Nov 2012 08:04:12 -0800 [thread overview]
Message-ID: <1354032252.14302.37.camel@edumazet-glaptop> (raw)
In-Reply-To: <50B4D43A.7030208@gont.com.ar>
On Tue, 2012-11-27 at 11:54 -0300, Fernando Gont wrote:
> Folks,
>
> FYI. This is might affect Linux users employing e.g. OpenVPN:
> <http://tools.ietf.org/html/draft-gont-opsec-vpn-leakages>.
>
> For a project such as OpenVPN, a (portable) fix might be non-trivial.
> However, I guess Linux might hook some iptables rules when establishing
> the VPN tunnel, such that e.g. all v6 traffic is filtered (yes, this is
> certainly not the most desirable fix, but still probably better than
> having your supposedly-secured traffic being sent in the clear).
>
> P.S.: Not sure if this is the right list to send this note. Please
> advice of a more appropriate one and/or feel free to forward this note
> if deemed appropriate...
This seems a user space issue to me.
accept_ra on linux is set to 1, meaning that as soon as forwarding is
enabled, RA are ignored.
next prev parent reply other threads:[~2012-11-27 16:04 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 [this message]
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
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=1354032252.14302.37.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=fernando@gont.com.ar \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox