From: david@lang.hm
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] VPN technology in a bufferbloated universe is doomed
Date: Tue, 6 Dec 2011 11:29:51 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1112061122310.11705@asgard.lang.hm> (raw)
In-Reply-To: <CAA93jw4rVde1zfK5zxEvU-yc_6WQ3z2efkqwScc1rXSxAPydgA@mail.gmail.com>
On Tue, 6 Dec 2011, Dave Taht wrote:
> Last puppy to shoot today...
>
> I have adaquately proven to myself at least, that VPN technologies in
> a bufferbloated universe, are doomed.
>
> VPN streams over UDP cannot compete with GSO and TSO offloads without
> some form of fair queuing and AQM that works.
>
> Encapsulating TCP over TCP merely compounds the problem.
>
> I wouldn't mind writing a paper demonstrating this fully, but in the
> meantime I feel that pursuing vpn technologies as part of cerowrt is a
> waste of time.
I saw papers documenting this over a decade ago. they ween't academic
papers, they were writups from VPN/tunneling tools explaining why
tunneling across SSH wasn't a good idea. I am amazed at how many people
find this a new idea, it needs a lot more publicity.
> Additionally, no matter how hard people try, things like ipsec have
> mysterious failure modes, and the additional protocols are frequently
> blocked by institutions and end user devices.
>
> Things like openvpn tend to work better than ipsec, but as I note
> above, fail to compete effectively.
>
> We have helped find and fix multiple problems in encapsulation over
> the past year, but until we achieve our primary goals as an
> organization - fixing bufferbloat - I strongly feel
> that vpns are a doomed technology.
I think this falls into the same category as IPv6.
Don't concentrate on this right now. Leave it as a supoorted function in
Cerowrt, because people trying to use these devices may want to use it,
but you can't solve the problems here, so don't try (at least until you
have the basics working)
David Lang
prev parent reply other threads:[~2011-12-06 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 17:37 Dave Taht
2011-12-06 19:29 ` david [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1112061122310.11705@asgard.lang.hm \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cerowrt@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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