Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Fwd: [PATCH] ag71xx: Added support for baby-jumbo packets.
Date: Fri, 22 Jun 2012 21:41:38 +0100	[thread overview]
Message-ID: <4FE4D882.50308@gmail.com> (raw)
In-Reply-To: <1340395875.353911244@apps.rackspace.com>

On 22/06/12 21:11, dpreed@reed.com wrote:
> Good step.  Why not allow 9K byte jumbos when one's packets traverse a path that is internal to the local area, and all the 1 GigE links support 9K?
>

All the posts I could see claim that the System-on-Chip NIC (Atheros 
AR7161) cannot handle packets greater than 1540 octets, so routing 9k 
packets from wired->wireless or wired->WAN would not be an option.  If I 
understood Dave's previous post correctly, though, the built-in switch 
allows jumbo packets, so wired->wired internal traffic should work fine 
with 9K packets already.

The only issue with that setup is that with mismatched MTUs, it might be 
impossible to communicate with the router and the 9k-friendly nodes at 
the same time.  Thankfully, on Linux at least, you can set per-route 
MTUs (http://lartc.org/howto/lartc.cookbook.mtu-discovery.html), so it 
might be possible to exploit that to do what you want.  Maybe something 
like this would work?

ip route add default via 172.30.42.1 mtu 1500
ip route add 172.30.42.1/32 dev eth0 mtu 1500
ip route add 172.30.42.1/27 dev eth0 mtu 9000

-- 
Robert Bradley

  reply	other threads:[~2012-06-22 20:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA=Zby5dVYjQNbbwMcHQc7qKSSHnYTAonjRJYG1d6zdqPsZ0Rg@mail.gmail.com>
2012-06-22 19:12 ` Robert Bradley
2012-06-22 20:11   ` dpreed
2012-06-22 20:41     ` Robert Bradley [this message]
2012-06-23 19:29       ` dpreed
2012-06-23 20:10         ` Dave Taht
2012-06-23 21:47         ` Robert Bradley
2012-06-23 22:33           ` dpreed

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FE4D882.50308@gmail.com \
    --to=robert.bradley1@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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