Not exactly full featured packet aggregation.

What it does it joins two packets together into one bigger. If you have 14 100 bytes packets (which is avg over regular networks) it will join each two of them into one 200 bytes packet and send it through as 7 packets. Real packet aggregation implementation joins all 14 of these packets into one 1400 bytes packet and sends it as one bigger instead of 7 smaller.

This makes huge impact under heavy load.

Regards,
Leszek


Lonnie Nunweiler wrote:
I'm not sure I understand the question.  The Atheros card already does
packet aggregation and compression.  We have tested with and without
the features and it does make a difference, with the better numbers
once the features are enabled.

We would not be planning on adding this for Ethernet.

Lonnie

On 8/17/06, Paul Hendry <[EMAIL PROTECTED]> wrote:
So with this MTU increase is there any chance of packet aggregation so we
can make use of it?

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Lonnie Nunweiler
Sent: 17 August 2006 07:24
To: WISPA General List
Subject: Re: [WISPA] Routerboard 532 and NStreme2

Tom,

The new V3 release has been posted and you can set MTU to very high
values if your cards support jumbo frames.  Our WAR board, with its
very advanced Intel Ethernet can do 16K for the MTU.  Most other cards
have limits in the 2K to 4K range.

We also have released the first x86 PC Architecture version and the
updated x86 WRAP version.  They  have the same features as the WAR
version.

I'm not sure if we mentioned it but the x86 version has a free mode
that is no longer a 24 hour trial.  It saves settings and everything
works, except of course the advanced features that we use to add
value.  You can use it for fairly advance routing (quagga has ospf and
rip) for free.

We'll require a paid license for wireless, policy or source routing,
bandwidth control and our firewall scripting.  We are pretty sure that
more than 11 MBytes/sec in Turbo mode on a power machine will meet
with approval.  Device bonding will be coming fairly soon and it will
allow simple hdx bonding, fdx bonding and failover bonding.

We use the Linux 2.6 kernel and we have been able to get this image to
well under 8 MB and average ram use on bootup is about 16 MB.  It took
a long time to get here and we have to thank everybody for being
patient.  Some of you wrote us off and figured that V3 would never
reach the light of day, so I hope you take a look at what this new
release can do.

Lonnie



On 8/15/06, Tom DeReggi <[EMAIL PROTECTED]> wrote:
> Lonnie,
>
> When you get that feature solved / added, please let me know, or make a
> public announcement.
> If you let me know, I'll do a bunch of talk for you persoanlly, to promote
> the feature.
> Thanks.
>
> Tom DeReggi
> RapidDSL & Wireless, Inc
> IntAirNet- Fixed Wireless Broadband
>
>
> ----- Original Message -----
> From: "Lonnie Nunweiler" <[EMAIL PROTECTED]>
> To: "WISPA General List" <wireless@wispa.org>
> Sent: Monday, August 14, 2006 8:37 PM
> Subject: Re: [WISPA] Routerboard 532 and NStreme2
>
>
> > It will just be easier to support an insane MTU size so that people
> > can go and do whatever they want.  I can imagine people doing some
> > vlan in vlan and then running the whole works over a tunnel, and each
> > one adds tags and headers to the actual 1500 byte payload.
> >
> > Lonnie
> >
> > On 8/14/06, Tom DeReggi <[EMAIL PROTECTED]> wrote:
> >> Lonnie,
> >>
> >> I just wrote to you off list, before seeing your onlist response.
> >>
> >> >V3 has support for a fully transparent
> >> > client bridge when it talks to an appropriately configured V3 AP
> >> > system.
> >>
> >> That is good news!
> >>
> >> > License Fee after 1 year.
> >>
> >> The policy you explained, is fair and reasonable.
> >>
> >> > We are currently working on a custom MTU size interface for every
> >> > device to be able to handle whatever you want for MTU size.
> >>
> >> Great.  To be more clear... Its easy for people (like me) to get
confused
> >> between IP versus Ethernet headers. In our VLAN applications, its the
> >> Ethernet packet that needs to be supported above 1500bytes (for
addition
> >> of
> >> VLAN to Ethernet header), we'd rarely ever need to increase IP packet
MTU
> >> above 1500 MTU. (although I see applications for IPSEC if larger MTU
> >> allowed
> >> or possibly for passing MPLS).
> >>
> >> Tom DeReggi
> >> RapidDSL & Wireless, Inc
> >> IntAirNet- Fixed Wireless Broadband
> >>
> > --
> > Lonnie Nunweiler
> > Valemount Networks Corporation
> > http://www.star-os.com/
> > --
> > WISPA Wireless List: wireless@wispa.org
> >
> > Subscribe/Unsubscribe:
> > http://lists.wispa.org/mailman/listinfo/wireless
> >
> > Archives: http://lists.wispa.org/pipermail/wireless/
>
> --
> WISPA Wireless List: wireless@wispa.org
>
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
>
> Archives: http://lists.wispa.org/pipermail/wireless/
>


--
Lonnie Nunweiler
Valemount Networks Corporation
http://www.star-os.com/
--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.1/421 - Release Date: 16/08/2006


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.1/421 - Release Date: 16/08/2006


--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/



--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to