All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Patch to allow for the ATM "cell tax"
Date: Sun, 05 Mar 2006 19:27:05 +0000	[thread overview]
Message-ID: <440B3B89.8070703@dsl.pipex.com> (raw)
In-Reply-To: <1141284603.10264.168.camel@ras.pc.brisbane.lube>

gentoo@databit7.com wrote:
> 
> On netBSD setting the MTU also seems to set the MRU, is this the case 
> here to? should people have thier DSLAMs configured for the same MTU?

It doesn't set MRU - you can still receive a larger than MTU packet.

I guess what you mean is MSS, if so yes Linux and Windows TCP also 
choose what tcp MSS to advertise by looking at the MTU on the interface. 
This means you get the tweak both ways. If you can't change each LAN PC 
then you can do it with Linux iptables set mss, you can make it 
aysymmetric and have min limits this way aswell.

The DSLAM is at the exchange. Doing it on the router by setting MTUs can 
cause problems and isn't as good as doing each client/clamping. If you 
set the LAN facing interface of the router to less than the clients all 
the websites/networks that set DF and don't respond to ICMP frag needed 
  will expose their brokenness.

FWIW the only time I see MRU is when I log on (pppoa) to my dsl 
connection. The other end asks for 32725 so the MTU on my ppp0 gets set 
to 32725 - it's lucky I can't really use it and tc doesn't pick up on 
it, though the mtu bit of the atm/dsl hack I use hardcodes it.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-03-05 19:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02  7:30 [LARTC] Patch to allow for the ATM "cell tax" Russell Stuart
2006-03-02 13:37 ` Markus Schulz
2006-03-02 13:51 ` Markus Schulz
2006-03-02 15:49 ` Andy Furniss
2006-03-02 19:54 ` Adam James
2006-03-02 21:35 ` Andy Furniss
2006-03-02 22:18 ` Russell Stuart
2006-03-02 22:23 ` Stephen Hemminger
2006-03-02 22:45 ` Jason Boxman
2006-03-02 23:44 ` Russell Stuart
2006-03-03  0:27 ` Jason Boxman
2006-03-03  0:43 ` Russell Stuart
2006-03-03  1:23 ` Markus Schulz
2006-03-03  1:49 ` Markus Schulz
2006-03-03  1:54 ` Russell Stuart
2006-03-03  2:23 ` Markus Schulz
2006-03-03  2:27 ` gentoo
2006-03-03 13:43 ` Andreas Hasenack
2006-03-03 16:18 ` Jason Boxman
2006-03-03 16:45 ` Andreas Hasenack
2006-03-03 18:45 ` Jason Boxman
2006-03-03 19:34 ` Andreas Hasenack
2006-03-05 19:27 ` Andy Furniss [this message]
2006-03-06 17:26 ` Jesper Dangaard Brouer
2006-03-13 18:09 ` Jason Boxman
2006-03-14  0:34 ` Russell Stuart
2006-03-14  0:49 ` Jason Boxman
2006-03-14  1:26 ` Russell Stuart
2006-03-14  2:10 ` Adam James
2006-03-14 13:14 ` Andy Furniss
2006-03-14 13:25 ` Andy Furniss
2006-03-14 23:28 ` Russell Stuart
2006-03-15  0:29 ` Andy Furniss
2006-12-06 18:59 ` Taylor, Grant

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=440B3B89.8070703@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.