Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "lartc@manchotnetworks.net" <lartc@manchotnetworks.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] interesting expert problem - shaping over VPN
Date: Sun, 26 Sep 2004 13:26:41 +0000	[thread overview]
Message-ID: <1096205201.6964.1.camel@drs0> (raw)
In-Reply-To: <200409171357.i8HDvISi001092@pog.tecnopolis.ca>

whoops,

oh yea -- ipsec and that whole eth0 thingy :-/   no wakeup on sundays.

are you running your tunnel exclusively for voice, or are there other
protocols as well ( i.e. contention).

cheers

c


On Sun, 2004-09-26 at 11:36, Trevor Cordes wrote:
> On 26 Sep, lartc@manchotnetworks.net wrote:
> > hi trevor,
> > 
> > perhaps others can chime in on their experiences and configs that have
> > shown promise for voip.
> 
> OK, I'll keep watching/posting.
> 
> > i would think that you would want to egress on both interfaces to insure
> > that the packets you want pass first. i thought that you had both
> > already.
> 
> I have egress on ipsec0 and ppp0 but not eth0.  It's actually 3
> interfaces total, which is why I hate PPPoE... it's so over complicated.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-09-26 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17 13:57 [LARTC] interesting expert problem - shaping over VPN lartc
2004-09-24  7:26 ` lartc
2004-09-26 13:26 ` lartc [this message]
2004-12-03 17:31 ` lartc

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=1096205201.6964.1.camel@drs0 \
    --to=lartc@manchotnetworks.net \
    --cc=lartc@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