From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] BW using CBQ/tc for VPN Ipsec i/f?
Date: Mon, 07 Apr 2003 18:08:17 +0000 [thread overview]
Message-ID: <marc-lartc-104973908511120@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104970718408779@msgid-missing>
On Monday 07 April 2003 13:41, Srikanth wrote:
> How about, if i shall use tc / iproute2 ?
cbq.init uses tc But it makes configuring tc more easy because you can use
simple config files.
Stef
>
> Srikanth.
>
> hare ram wrote:
> >if you are using the cbq.init script yes it works
> >
> >hare
> >----- Original Message -----
>
> From: "Srikanth" <srikanth_w@naturesoft.net>
>
> >To: <lartc@mailman.ds9a.nl>
> >Sent: Monday, April 07, 2003 2:45 PM
> >Subject: [LARTC] BW using CBQ/tc for VPN Ipsec i/f?
> >
> >>Hi all,
> >>
> >>I want to allocate bandwidth for ipsec interface using CBQ/tc.
> >>Suppose the conf. file is like this,
> >>
> >>DEVICE=ipsec0,10Mbit,1Mbit
> >>RATE\x128Kbit
> >>WEIGHT\x10Kbit
> >>PRIO=5
> >>RULE\x192.128.1.0/24
> >>
> >>Does it work
> >>or
> >>What else options need to be taken care like ipsec packets/protocol/port
> >># etc.?
> >>C'd anybody suggest please?
> >>
> >>regds,
> >>Srikanth.
> >>
> >>
> >>_______________________________________________
> >>LARTC mailing list / LARTC@mailman.ds9a.nl
> >>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-07 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 9:27 [LARTC] BW using CBQ/tc for VPN Ipsec i/f? Srikanth
2003-04-07 11:53 ` Srikanth
2003-04-07 18:08 ` Stef Coene [this message]
2003-04-08 9:36 ` Srikanth
2003-04-08 22:39 ` Jose Luis Domingo Lopez
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=marc-lartc-104973908511120@msgid-missing \
--to=stef.coene@docum.org \
--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.