Bug 110999 - carp(4) should document unsupported interface types
Summary: carp(4) should document unsupported interface types
Status: Open
Alias: None
Product: Documentation
Classification: Unclassified
Component: Manual Pages (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-29 08:00 UTC by tom
Modified: 2018-04-11 20:41 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tom 2007-03-29 08:00:10 UTC
I just spent a few hours trying to figure out why I couldn't get CARP
to work on an if_bridge interface before discovering "%s: carp is not
supported for this interface type\n" in the source and finding out that
if I had set the sysctl net.inet.carp.log > 1, i would have seen an error
message when I tried to ifconfig  the carp interface.

Ideally, I would like to see CARP supported on bridge interfaces, but
failing that, i would like to see the man page for CARP list the
interface types that are not supported, or not completely supported. It
would also be nice if the failure diagnostic output appeared at the
default logging level and not just the higher one.

Fix: 

N/A
How-To-Repeat: N/A
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2007-03-29 09:13:02 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-doc

Reclassify.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:43 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped