All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory G Carter <gcarter@aesgi.com>
To: netfilter@lists.netfilter.org
Subject: Re: How would this help my LAN / network
Date: Fri, 07 Oct 2005 11:45:25 -0500	[thread overview]
Message-ID: <4346A625.6020002@aesgi.com> (raw)
In-Reply-To: <20051007162420.D0AB269B0D@smtp.sterenborg.info>

Upstream providers such as my ISP here (Time Warner Cable) hardly 
support ECN, I would be surprised if they did.

For example, the crappy Zyxel cable modems they put out here don't 
support ECN notification, so the first thing they do when they overflow 
due to high amounts of traffic is simple shut down, most of them just crash.

I have to put rate limiting policies on all my routers connected to 
these modems otherwise they simply die when you try and push too much 
data through them.

I remember when Time Warner was using ubr9xx routers from Cisco, which 
were excellent, but much more expensive of course than the Zyxel.

If somone like Time Warner can't do ECN, I would hardly expect them to 
do traffic prioritization....Oooo....complicated.

:-)

-gc

Rob Sterenborg wrote:

>>>I just came across one of the threads on the LARTC.
>>>In the thread it had this.
>>>
>>>So my question is, for the following rules, would these increase my
>>>browsing / traffic, and if so, how.
>>>
>>>      
>>>
>>Small packets and control pachets should have priority
>>because they carry intrractive traffic.
>>    
>>
>
>Is it true that the upstream (ISP) routers have to support TOS for this
>to work ?
>
>
>Gr,
>Rob
>
>
>  
>



  parent reply	other threads:[~2005-10-07 16:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 14:30 How would this help my LAN / network Brent Clark
2005-10-07 15:16 ` Sorin Panca
2005-10-07 16:08   ` Brent Clark
2005-10-07 16:21   ` Rob Sterenborg
2005-10-07 16:40     ` Sorin Panca
2005-10-07 16:45     ` Gregory G Carter [this message]
2005-10-07 17:12       ` John A. Sullivan III
2005-10-07 17:36         ` Sorin Panca
2005-10-07 16:36   ` Brent Clark
2005-10-07 17:21     ` Sorin Panca

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=4346A625.6020002@aesgi.com \
    --to=gcarter@aesgi.com \
    --cc=netfilter@lists.netfilter.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.