Date: Wed, 20 Aug 2025 22:46:41 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 288982] carp(4) conflicts with handbook Message-ID: <bug-288982-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288982 Bug ID: 288982 Summary: carp(4) conflicts with handbook Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: bugs@FreeBSD.org Reporter: pprocacci@gmail.com CC: doc@FreeBSD.org carp(4) shows VIPs being added to interfaces w/ a mask of /24. The online documentation shows them as /32's. (https://docs-archive.freebsd.org/doc/14.3-RELEASE/usr/local/share/doc/freebsd/en/books/handbook/advanced-networking/index.html#carp) Earlier documentation made the distinction for both cases: https://docs-archive.freebsd.org/doc/13.0-RELEASE/usr/local/share/doc/freebsd/en/books/handbook/carp.html What the heck is correct here? Is there a case for both scenarios? These scenarios should be detailed. For the record, I was using /32's without issue, but in my latest build started using whatever mask was associated with the network as per carp(4). Since doing so, the BACKUP carp instance has been sourcing from the VIP which is causing all sorts of trouble; the main one being return packets aren't returned to me and instead being returned to the PRIMARY. This is expected as I'm considered a BACKUP. The unexpected part is that it's sourcing from the VIP to start off with. I'd wager this is a documentation error in carp(4), but without knowing the cases with anything other than a /32 is needed I can't say that for sure. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-288982-227>