From: Stephen Hemminger <shemminger@osdl.org>
To: Ritesh Taank <taankr@aston.ac.uk>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Packet Corruption Support
Date: Wed, 16 Aug 2006 15:59:58 -0700 [thread overview]
Message-ID: <20060816155958.2598bdff@localhost.localdomain> (raw)
In-Reply-To: <44E3A132.7090302@aston.ac.uk>
On Wed, 16 Aug 2006 23:50:26 +0100
Ritesh Taank <taankr@aston.ac.uk> wrote:
> Hi there,
>
> I am currently using netem that has been packaged with my linux kernel
> 2.6.17 (as part of the Knoppix 5.0.1 Boot CD), and the 'corrupt'
> parameter is not being recognised as a valid argument.
>
> Having read many posts online, it appears that the Packet Corruption
> feature should be supported from kernel versions 2.6.16 onwards.
>
> So I was wondering why my version does not support the corrupt feature?
>
> Are there any kernel versions out there that do support it?
>
> I was wondering if there was a way to patch my existing kernel do enable
> the corruption feature?
>
> Any help/guidance is much appreciate.
>
> Thanks in advance too.
>
> Ritesh
It was introduced with this change set.
Author: Stephen Hemminger <shemminger@osdl.org> 2005-12-21 19:03:44
Committer: David S. Miller <davem@sunset.davemloft.net> 2006-01-03 13:11:05
Parent: aa8751667dcd757dd9a711b51140adf181501c44 ([PKT_SCHED]: sch_netem: correctly order packets to be sent simultaneously)
Child: 6d037a26f08711a222ed0d3d12b09e93eed7d3e8 ([PKT_SCHED]: Qdisc drop operation is optional)
[PKT_SCHED] netem: packet corruption option
Here is a new feature for netem in 2.6.16. It adds the ability to
randomly corrupt packets with netem. A version was done by
Hagen Paul Pfeifer, but I redid it to handle the cases of backwards
compatibility with netlink interface and presence of hardware checksum
offload. It is useful for testing hardware offload in devices.
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
More likely the version if iproute2 utilities included with Knoppix is not
up to date and doesn't understand the command line option.
prev parent reply other threads:[~2006-08-16 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 22:50 Packet Corruption Support Ritesh Taank
2006-08-16 22:54 ` Rick Jones
2006-08-16 22:59 ` Stephen Hemminger [this message]
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=20060816155958.2598bdff@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=netdev@vger.kernel.org \
--cc=taankr@aston.ac.uk \
/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