为什么arp ignore / annouce默认情况下不启用 [英] Why arp ignore/annouce are not enable by default

查看:150
本文介绍了为什么arp ignore / annouce默认情况下不启用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个具体的问题需要一个答案的经验:



为什么arp_ignore / arp_announce默认情况下不启用linux安装(例如debian)有没有具体原因?



从错误的网络接口接收arp答案的兴趣?



感谢您的帮助。 / p>

请问,

解决方案

这不是Debian具体的,默认是从Linux。



检查 https:/ /bugzilla.redhat.com/show_bug.cgi?id=168960 以及 David的回应Miller


此行为与Linux IPV4堆栈遵守
一致,基于主机的IPV4地址模型而不是基于界面的
模型,这几乎是你要求的。



两个寻址模型都由RFC描述,并且完全是
有效。



这不应该改变,不是一个错误。如果你想要不同的
行为,你可以调整可调参数,但是不要
使它们适合所有人作为默认值。


请参阅 RFC 1122,3.3.4.2多重要求要求(强ES模型,弱ES模型)。


I have a specific question which need experience for an answer:

Why arp_ignore / arp_announce are not enable by default on linux installation (debian for example) is there a specific reason ?

Which interest to receive arp answer from wrong network interfaces ?

Thanks for your help.

Regards,

解决方案

That's not Debian specific, the default is from Linux.

Check https://bugzilla.redhat.com/show_bug.cgi?id=168960 and the response from David Miller:

This behavior is consistent with the Linux IPV4 stack's adherence to the host based model of IPV4 address instead of the interface based model which is pretty much what you are asking for.

Both addressing models are described by the RFCs and are completely valid.

This should not be changed and is not a bug. If you want different behavior, the tunables are there for you to tweak, but that does not make them right for everyone as a default.

See RFC 1122, 3.3.4.2 Multihoming Requirements (Strong ES model, Weak ES model).

这篇关于为什么arp ignore / annouce默认情况下不启用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆