From: Jesper Kold-Hansen <candyman@cs.auc.dk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to determine tcp rate & classifying packet info
Date: Wed, 22 Jan 2003 09:33:19 +0000 [thread overview]
Message-ID: <marc-lartc-104322807811085@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104318194301024@msgid-missing>
Well red the doc on the cues. I know on the HTB que, there is a rate and a
coil setting. The rate is the rate at wich the packegges are sendt in
kbyte, and the coil is a burst funktion, so if you set the coil and the rate at
the same speed you vil get a specifik rate that your packagges are send.
But it is not easy to controle the actual rate, because when you set a
rate, you actualle drop tcp packagges, the the protocol will slow down by
it self.
Look at the Advanced Routing howto.
CandyMan
On Tue, 21 Jan 2003, ganesh palwe wrote:
>
> > >hello everybody
> >>
> > >need help
> >>
> >> how should i control the tcp rate, is it possible?
>
>
> >It's possible
> >www.lartc.org
> >www.docum.org
>
> > >also,
> >>
> > >suppose i have 2 database tables :
> >>
> > >1) one for online accounting &
> >>
> > >2) one for online sales updating
> >>
> > >now both of these transactions which will update my SQL server
> databse will
> > >be on the same port number
> >>
> >> how can i classify these packets so that i can give high bandwidth &
> >> highest prio to type 2 packets.
> >What if you the iptables helper that can match packet with a string in it?
>
> > I think the select is unique so you can see the difference. Once you can
> >recognise the packets, you can mark them with iptables. That mark can
> >be
> >used to put the packets in differenct classes so you can configure
> >different
> >rates for the packets.
> >But this will suck if you select statement is too big for one packet.
> >
> >Stef
> >
> --
>
>
> still needing help !
> i m very sorry to say that i hardly have got any useful stuff regarding controlling tcp rate, rather packeteer information was good (TCP Rate Control - by Shrikrishna Karandikar).
> what i want to do is everytime i want to establish a connection with any server(say X-server ) on the basis that X should send me data at agreed upon rate, the rate should not increase beyond that value.
> can i implement it? if yes where can i find information?
>
> Ok,next was
> for classifying packet by making use of marking
> what if i m using u32 classifier instead of fw.
> is there utility with u32 to mark packets.
> also,
> what i think is that, classifiers will come into the picture after the connection establishment, so how could they differentiate 2 different type applications for same service?
> 10x in advance
> ganesh.
>
>
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now
_______________________________________________
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-01-22 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 20:43 [LARTC] how to determine tcp rate & classifying packet info ganesh palwe
2003-01-21 21:44 ` Stef Coene
2003-01-22 1:07 ` ganesh palwe
2003-01-22 9:33 ` Jesper Kold-Hansen [this message]
2003-01-22 17:11 ` Stef Coene
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-104322807811085@msgid-missing \
--to=candyman@cs.auc.dk \
--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