All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dawid Kuroczko <qnex@atlantis.ssw.krakow.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Intelligent P2P detection
Date: Wed, 26 Mar 2003 21:37:09 +0000	[thread overview]
Message-ID: <marc-lartc-104871538718154@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104857984213566@msgid-missing>

On Tue, 25 Mar 2003, Luman wrote:

> I need this solution not only to prioritizing the traffic (prioritizing
> can be achieve in other way) but also to selection the Internet link. I
> want to NAT this low quality data for some specific address in order to
> send it over cheaper link. 

I do not know if it might help you, but here's my "temporary hack quality"
solution.

Assumptions:
  Determine and mark 'good traffic' -- i.e. smtp, ftp, http, ssh, etc.,
  everything which uses well known ports.  Probably most people do it
  anyway, at least to some level.

  All what is left are P2P connections and some other misc connections.
  A bit unfair for other protocol using non-standard ports, like Instant
  Messenger style-software, and lots of other stuff.  So here we introduce
  a trick.  IMs and other low bandwidth traffic will use small packets
  ( < 512 or even < 256), P2P will use maximum MTA available (usually
  1500, but I've seen some using 576 packets, hence i treat > 512 as P2P).

  Probably you've notices that I mention round numbers, as 512 or 1024,
  that's because I use u32 for marking packets.  How I do it, we leave
  as an exercise to the reader. ;-)))

  Regards,
    Dawid
-- 
  ..................        ``The essence of real creativity is a certain
 : *Dawid Kuroczko* `.         playfulness, a flitting from idea to idea
 : q n e x@knm.org.pl :     without getting bogged down by fixated demands.''
 `....................'  Sherkaner Underhill, A Deepness in the Sky, V. Vinge

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

  parent reply	other threads:[~2003-03-26 21:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  8:08 [LARTC] Intelligent P2P detection Luman
2003-03-25 10:21 ` Kim Jensen
2003-03-25 10:53 ` Luman
2003-03-25 12:20 ` Kim Jensen
2003-03-25 12:24 ` Luman
2003-03-25 12:30 ` Luman
2003-03-25 12:44 ` Matthias Weingart
2003-03-25 12:51 ` Robert Kryczało
2003-03-25 12:56 ` Luman
2003-03-25 13:05 ` Robert Kryczało
2003-03-25 15:27 ` Robert Kryczało
2003-03-26 21:37 ` Dawid Kuroczko [this message]
2003-03-26 21:50 ` Dawid Kuroczko
2003-03-27  9:24 ` Luman
2003-03-27  9:35 ` Luman
2003-03-27 10:16 ` Gordan Bobic
2003-03-27 15:20 ` Robert Kryczalo
2003-03-27 15:32 ` Robert Kryczało
2003-03-27 16:04 ` Gordan Bobic
2003-03-27 16:38 ` Robert Kryczało
2003-03-27 16:43 ` Gordan Bobic
2003-03-27 20:15 ` Matthias Weingart
2003-03-27 21:34 ` Arvid Stüwe
2003-03-28  8:14 ` Robert Kryczało
2003-03-31 12:10 ` Szymon Miotk
2003-03-31 12:32 ` Patrick McHardy

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-104871538718154@msgid-missing \
    --to=qnex@atlantis.ssw.krakow.pl \
    --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.