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
| ||
|
Message-ID: <CAKwN9=C-_F-8GQ7yMO6wVR1Ukw3gCBYOzxxDRRLU9b-u9P1v-Q@mail.gmail.com> Date: Mon, 15 May 2017 14:35:26 -0700 From: Ihar Hrachyshka <ihrachys@...hat.com> To: Julian Anastasov <ja@....bg> Cc: "David S. Miller" <davem@...emloft.net>, He Chunhui <hchunhui@...l.ustc.edu.cn>, netdev@...r.kernel.org Subject: Re: [PATCH] neighbour: update neigh timestamps iff update is effective On Mon, May 15, 2017 at 1:05 PM, Julian Anastasov <ja@....bg> wrote: > > It seems arp_accept value currently has influence on > the locktime for GARP requests. My understanding is that > locktime is used to ignore replies from proxy_arp > routers while the requested IP is present on the LAN > and replies immediately. IMHO, GARP requests should not > depend on locktime, even when arp_accept=0. For example: Yes, I believe so. I actually thought about introducing the patch that does just that: forcing override on garp, but then I was thinking, maybe there is some reason to still apply locktime rules to garps; f.e. if you have multiple nodes carrying the ip address and located on the same segment, maybe you want to pick the first that replies to you (in theory, it may be the node that is less loaded, or closer to us; but then, it's so fragile even if that was the intent...) Do you want me to post the patch, or will you cover it? Ihar
Powered by blists - more mailing lists