netdev - Re: Enable netem in my Linux box

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 May 2007 14:00:40 -0400
From:	Koon Wah Yick <kyick@...atel-lucent.com>
To:	Stephen Hemminger <shemminger@...ux-foundation.org>
CC:	Koon Wah Yick <kyick@...atel-lucent.com>, netdev@...r.kernel.org,
	"Yick, Koon Wah (Koon)" <kyick@...ail.ho.lucent.com>
Subject: Re: Enable netem in my Linux box

Stephen:

Thank you, I got it.  I try the same command again with "add" and "change" they
all work.(no error)  But when I start my Network Emulator, how can I stop it.
Do I have to delete any file I create when doing "add"?  If yes, where is it?

Koon-Wah.

On 5/10/2007 12:57 PM, Stephen Hemminger wrote:
> On Thu, 10 May 2007 12:09:46 -0400
> Koon Wah Yick <kyick@...atel-lucent.com> wrote:
> 
> 
>>Stephen:
>>
>>Thank you for your response, I type in modinfo sch_netem
>>
>>Here is what I got:
>>
>>filename: /lib/modules/2.6.11-1.1369_FC4/kernel/net/sched/sch_netem.ko
>>license: GPL
>>vermagic: 2.6.11-1.l369_FC 686 REGPARM 4KSTACKS gcc-4.0
>>depends:
>>srcversion: BD4563861423428FF0D5918
>>
>>when I try the following "tc" command with netem
>>
>>
>>>tc qdisc change dev eth0 root netem loss 0.1%
>>
>>I got the error message
>>RTNETLINK answers: No such file or directory.
>>
> 
> 
> You want to use 'add' not 'change'.
> The examples on the linux-net page are sequential, so the first one uses 'add'.
> Later examples, then use change to alter parameters


-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html