From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to determine tcp rate & classifying packet info
Date: Tue, 21 Jan 2003 21:44:51 +0000 [thread overview]
Message-ID: <marc-lartc-104318554006351@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104318194301024@msgid-missing>
On Tuesday 21 January 2003 21:43, 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
--
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-01-21 21:44 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 [this message]
2003-01-22 1:07 ` ganesh palwe
2003-01-22 9:33 ` Jesper Kold-Hansen
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-104318554006351@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox