From: "Defekt" <defekt@liquid-nexus.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Traffic shaping and MTU/MSS
Date: Mon, 24 Nov 2003 07:35:13 +0000 [thread overview]
Message-ID: <marc-lartc-106966386410469@msgid-missing> (raw)
Hi,
I'm using traffic shaping on my home 1.5M/256K ADSL connection. The problem
I'm running into is even when I'm shaping upload traffic (web server/p2p
etc...) I run into latency issues with online gaming. This is of course due
to the 256Kb upload and the 1492 MTU (PPPoE) which means a single large
packet will take up to 40ms to transfer.
What I would like to do is reduce the MSS for low priority traffic using
ipchains based on a fwmark value. Is it possible to do this?
Appreciate any other suggestions to solve this problem.
Thanks.
Marc
--
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-11-24 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 7:35 Defekt [this message]
2003-11-24 23:48 ` [LARTC] Traffic shaping and MTU/MSS Damion de Soto
2003-11-26 11:56 ` Andy Furniss
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-106966386410469@msgid-missing \
--to=defekt@liquid-nexus.net \
--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