From: Alexander Samad <alex@samad.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Classful Queuing
Date: Tue, 12 Oct 2004 01:16:54 +0000 [thread overview]
Message-ID: <20041012011653.GQ522@samad.com.au> (raw)
In-Reply-To: <20041012010156.GY16095@cerberus>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
Hi
I think what you need to look for is marking of packets with netfilter -
let it classify and then used tc to place the properly marked packets
into the proper queue
Because you can mark in the PREROUTING table in mangle before it is enc
Alex
On Mon, Oct 11, 2004 at 07:01:57PM -0600, Jamin W. Collins wrote:
> OK, I'm stumped. I've read through most of the LARTC HOWTO and have yet
> to find a basis for what I need to accomplish.
>
> I have a Linux box that controls access to and from the Internet at my
> workplace. We have a number of remote employees that connect via PPTP
> and IPSEC to the office's internal network. Some of these remote
> employees are currently using SIP phones. The problem is occasionally
> the available bandwidth becomes consumed and the VoIP calls (obviously)
> suffer because of this.
>
> Configuration:
> eth0 - connected to the internal office
> eth1 - connected to the internet
> pppX - incoming on eth1 connection
> ipsec0 - incoming on eth1 connection
>
> My question, how can I set classful htb queuing up so that it's rules
> encompass all traffic on eth1 (including that to and from the ipsec and
> ppp connections) while reserving bandwidth for and prioritizing the SIP
> traffic?
>
> In looking through chapter 9 it appears that all the configurations
> apply to a specific interface, and thus would only get eth1 for example.
> While the traffic on the ppp and ipsec connections would arrive on the
> eth1 interface only after being placed on their specific interfaces and
> encrypted, thus most likely missing proper classification and
> prioritization.
>
> Am I over thinking this problem or missing something?
>
> I'll happily provide any clarification or additional information needed.
>
> --
> Jamin W. Collins
>
> It has always been Debian's philosophy in the past to stick to what
> makes sense, regardless of what crack the rest of the universe is
> smoking. -- Andrew Suffield
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-12 1:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 1:01 [LARTC] Classful Queuing Jamin W. Collins
2004-10-12 1:16 ` Alexander Samad [this message]
2004-10-12 1:31 ` Jamin W. Collins
2004-10-12 3:04 ` Alexander Samad
2004-10-12 3:46 ` rsenykoff
2004-10-12 6:25 ` Robert Felber
2004-10-12 7:05 ` Alexander Samad
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=20041012011653.GQ522@samad.com.au \
--to=alex@samad.com.au \
--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 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.