public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Datty <datty.wtb@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Traffic shaping - downstream data
Date: Tue, 12 Jun 2012 21:43:18 +0100	[thread overview]
Message-ID: <CAG+b7UWsMvf9WUEYCnTaMAd5hCJa3u5kAKnyfAHHNhdqajcPqw@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiDzi7WpeUEvGQW_wZ2juXSQph8jSooabE9U50tu1AgtTQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]

On Tue, Jun 12, 2012 at 5:05 PM, Michael Mol <mikemol@gmail.com> wrote:

> On Tue, Jun 12, 2012 at 11:06 AM, Michael Mol <mikemol@gmail.com> wrote:
> > On Tue, Jun 12, 2012 at 9:37 AM, Datty <datty.wtb@gmail.com> wrote:
> >> On Tue, Jun 12, 2012 at 2:21 PM, Michael Mol <mikemol@gmail.com> wrote:
> >>> On Jun 12, 2012 8:59 AM, "Datty" <datty.wtb@gmail.com> wrote:
> >
> > [snip]
> >
> >>> More detail later...but make sure your vpn link is not TCP. UDP, fine,
> >>> IP-IP, fine, but not TCP. TCP transport for a VPN tunnel leads to ugly
> >>> traffic problems.
> >
> >> Ah it is TCP at the moment. Not something I could change too easily
> either.
> >> Is it possible to work around or is it not worth fighting with?
> >
> > If all of these cases are true:
> >
> > * You only have TCP traffic going over that VPN
> > * You don't have any latency-sensitive traffic going over that VPN (no
> > VOIP, no interactive terminal sessions and you won't pull your hair
> > out over 10s or more round-trips slowing down page loads)
> > * You don't have large bulk data transfers going over that VPN (my
> > best example of personal experience here was trying to locally sync my
> > work-related IMAP mailbox)
> >
> > ...then it's not worth fighting with.
>
> I could stand to be more precise and concise:
> If you're going to use a TCP transport for VPN:
> * You need to not mix TCP and UDP traffic
> * You need to not have latency-sensitive traffic.
>
> In practice, you'll almost always have some UDP traffic; that's how
> DNS generally operates. And even where DNS uses TCP, it's still
> latency-sensitive.
>
> So I can be even more concise:
> If you're going to use a TCP transport for VPN, you must avoid having
> TCP traffic over that VPN link.
>
> --
> :wq
>

Thank you for that very thorough explanation, I had no idea there was a
problem with using TCP, I figured the error correction would help it be
more stable than just throwing data at it and hoping it got there. Somehow
I've avoided the majority of the issues you've mentioned up to now, but
then again generally my connection is very slow so maybe I'm just not
feeling the effects. My ping however is around 40ms higher over the VPN
link so I'm guessing that may be a sign.

I'll set up a second vpn tunnel using UDP to test it out, my resistance to
changing the main one is purely down to the fact that I have around 30
clients, probably half of which would reach for antiseptic if I mentioned
TCP and I don't fancy having to drive 200+ miles to each of them to change
it for them.

I'll give it a shot tomorrow and report back on how it gets on. Regarding
the tc rules I mentioned, do they look alright? I'm not 100% on how it all
goes together still and would appreciate a prod in the right direction.

Thanks again

Oliver

[-- Attachment #2: Type: text/html, Size: 3730 bytes --]

  reply	other threads:[~2012-06-12 20:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 15:27 [gentoo-user] Traffic shaping - downstream data Datty
2012-06-12  8:58 ` J. Roeleveld
2012-06-12 12:54   ` Datty
2012-06-12 13:21     ` Michael Mol
2012-06-12 13:37       ` Datty
2012-06-12 15:06         ` Michael Mol
2012-06-12 16:05           ` Michael Mol
2012-06-12 20:43             ` Datty [this message]
2012-06-12 20:57               ` Michael Mol

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=CAG+b7UWsMvf9WUEYCnTaMAd5hCJa3u5kAKnyfAHHNhdqajcPqw@mail.gmail.com \
    --to=datty.wtb@gmail.com \
    --cc=gentoo-user@lists.gentoo.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