From: "GoMi" <gomiuk@hotmail.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] No way to shape my traffic with p2ps
Date: Fri, 16 May 2003 16:23:22 +0000 [thread overview]
Message-ID: <marc-lartc-105310235809609@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105309619201489@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Basically there is no solution to stop these? Is that what you are saying? Do other p2p programs produce these short SYN packages, or just KaZaa? I am studying the traffic in my lan with tcpdump and i get lots of packages like this coming to my inner interface :
19:14:50.866190 XXX.XXX.XXX.XXX.1101 > YYY.YYY.YYY.YYY.80: . ack 14594 win 64240 (DF)
Being XXX my internal users and YYY external public addresses
What are those? Response to ack packages right?
I also have lots of
19:19:26.676651 YYY.YYY.YYY.YYY.80 > XXX.XXX.XXX.XXX.4078: . 10220:11680(1460) ack 1 win 17121 (DF)
Is it posible that kazaa uses ACK packages to send data? Because these packages are comming to my lan with the MTUç
- -----Mensaje original-----
De: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] En nombre de David Boreham
Enviado el: viernes, 16 de mayo de 2003 18:24
Para: lartc@mailman.ds9a.nl
Asunto: Re: [LARTC] No way to shape my traffic with p2ps
> P2P tools receive many small packets from everywhere. Those many
> packets clog the connection and need to be throttled BEFORE they cross
> the bottleneck of your uplink. (I'm aware that's not really possible
> on a standard DSL connection)
I did say that he needs to rate-limit SYN segments.
Those inbound packets are generated in response to an outbound SYN. Stop the SYN and you stop the inbound traffic.
He's NAT'ing, so there are no inbound connections to worry about.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0
iQA/AwUBPsUQen7diNnrrZKsEQIFYwCgrkfbFNnnPgcnYdjBZq+OF062BOYAoJdG
DVPhhHhfynSKz0HuD44GdkPE
=K0xm
-----END PGP SIGNATURE-----
_______________________________________________
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-05-16 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 14:40 [LARTC] No way to shape my traffic with p2ps GoMi .
2003-05-16 14:57 ` David Boreham
2003-05-16 15:05 ` Arvid Stüwe
2003-05-16 15:20 ` David Boreham
2003-05-16 16:23 ` GoMi [this message]
2003-05-16 17:46 ` Stef Coene
2003-05-17 17:26 ` Ricardo Jorge da Fonseca Marques Ferreira
2003-05-17 23:23 ` Ricardo Jorge da Fonseca Marques Ferreira
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-105310235809609@msgid-missing \
--to=gomiuk@hotmail.com \
--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.