RTNETLINK回答:没有这样的文件或目录
当我运行这个 cmd 时:
tc qdisc add dev eth0 root red limit 51200000 min 128000 max 512000 avpkt 1024 burst 200 ecn probability 0.5
我得到
RTNETLINK answers: No such file or directory
我已经为 netfilters
配置了内核,以及 menuconfig
中的所有网络选项。
我不明白为什么会出现这个错误。我正在使用 iproute2-2.6.23
和 Fedora 8。
这在我的笔记本电脑上工作正常,但在我的台式电脑上却不行?
When I run this cmd:
tc qdisc add dev eth0 root red limit 51200000 min 128000 max 512000 avpkt 1024 burst 200 ecn probability 0.5
i get
RTNETLINK answers: No such file or directory
I have configured the kernel for netfilters
, and all the networking options in menuconfig
.
I don't understand why this error occurs. I'm using iproute2-2.6.23
and Fedora 8.
This was working fine on my laptop, but not on my Desktop PC?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
该错误可能是由于 Linux 内核缺乏对流量控制的支持。
以下是文档的摘录,其中列出了在 Linux 中正确运行流量控制功能所需的内核编译选项:
来源:流量控制 HOWTO - 内核要求
The error could be due to a lack of support for traffic control in Linux kernel.
Here is an excerpt from documentation that lists kernel compilation options needed for proper operation of traffic control functionality in Linux:
Source: Traffic Control HOWTO - Kernel requirements
在我的系统上,您的命令会自动加载
sch_red
模块。这个问题相当古老,因此在现代系统上,如果您有所需的模块,自动加载应该可以正常工作。通过运行检查是否错过了内核模块:如果没有打印任何内容,则重试运行 tc 命令并查看是否有帮助。
如果没有,请确保您已在内核中编译了
CONFIG_NET_SCH_RED
(随机早期检测)。 更多信息请参见内核文档。On my system your command autoloads the
sch_red
module. The question is rather old so on a modern system the autoloading should work fine if you have the required module. Check if you miss the kernel module by running:If it prints nothing, then retry running
tc
command and see if it helps.If not, ensure you have
CONFIG_NET_SCH_RED
(Random Early Detection) compiled in your kernel. More info at kernel documentation.我在一个不包含通常的预构建模块阵列的系统上编译(树内)ralink wifi驱动程序后得到了这个。模块已加载,接口也在那里,但无法设置:(
是的,
wlanB
是正确的。)最终发现系统还缺少常见的固件数组 在/lib/firmware
中。此问题已通过apt installfirmware-ralink
修复。I got this one after compiling the (in-tree) ralink wifi drivers on a system that did not include the usual array of pre-built modules. The modules loaded and the interface was there, but could not be set up:
(Yes,
wlanB
is correct.) Eventually figured out the system was also missing the usual array of firmware in/lib/firmware
. This was fixed withapt install firmware-ralink
.