Date: Thu, 28 Feb 2019 12:27:54 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236105] carp MASTER/MASTER status when adding or removing carp IP addresses Message-ID: <bug-236105-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236105 Bug ID: 236105 Summary: carp MASTER/MASTER status when adding or removing carp IP addresses Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: vegeta@tuxpowered.net I'm not sure how much of a bug this is, rather a feature request for special cases.=20 carp HMAC is calculated using a hash of carp IP addresses for a given VHID. This means that if two routes are configured with different carp IP address= es, verifying signatures will fail and routers will ignore carp annoucements fr= om eachother resulting in MASTER/MASTER operation. However I understand this is a feature for enforcing configuration check, t= here are cases when this is a bad idea: on some routers I have carp addresses reconfigured tens of times a day. As it is impossible to configure both rou= ters exactly at the same time, there is often a difference big enough to triger MASTER/MASTER operation which is then soon resolved. I value network stabil= ity more than configuration check enforced on me and if configuration was wrong, things s would break anyway and I would be notified by other means. Please see https://github.com/innogames/freebsd/commit/a1b1ff410c0f532b67660c86593ef7b= da2398be8 for my first attempt. It still lacks sysctl value set hook, so works fine o= nly after carp addresses are configured. If you like the idea and believe it co= uld be merged into kernel, I will add a set hook recalculating HMAC and post the patch here. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236105-227>