All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Van Dolson <rayvd@digitalpath.net>
To: linux-ppp@vger.kernel.org
Subject: PPP Encapsulated in GRE with IP Precedence headers
Date: Thu, 30 Jun 2005 05:14:24 +0000	[thread overview]
Message-ID: <20050630051424.GA13477@digitalpath.net> (raw)

Background:
We are using Poptop + PPP/MPPE and are running some VoIP applications
over this and want to "prioritize" the voice traffic.  This is easily
done in a non-tunnelled environment because the voice protocol we are
using (RTP) sets the "Expedite Immediately" flag in the DSCP headers of
the IP packet.  Cisco routers and iptables/tc can be made to flag on
this and do the "right" thing (ie: prioritize).

However, when Poptop encapsulates the PPP frames into GRE, it does not
put any sort of DSCP flags in the corresponding GRE IP packets.  We are
hoping to have Poptop/pptpclient modified to unpack the PPP frame it
receives, examine the IP packet within and copy any DSCP flags into the
GRE IP packet.  Thus if the IP packet in question was RTP, the
resulting GRE packet would have the High Precedence DSCP flag set.

The question is, does PPP go haywire if packets start arriving out of
order as a result of this?  Would we end up being worse-off than if we
didn't do this at all?  I can see how a GRE-only tunnel would handle
this just fine, but the added layer of PPP makes me think any sort of
re-ordering of the GRE packets would break the PPP connection.

Thoughts?  Flames?

-- 
Ray Van Dolson
Linux/Unix Systems Administrator
Digital Path, Inc.

             reply	other threads:[~2005-06-30  5:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30  5:14 Ray Van Dolson [this message]
2005-06-30 13:27 ` PPP Encapsulated in GRE with IP Precedence headers James Carlson
2005-06-30 15:25 ` Ray Van Dolson
2005-06-30 15:36 ` James Carlson

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=20050630051424.GA13477@digitalpath.net \
    --to=rayvd@digitalpath.net \
    --cc=linux-ppp@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.