Exciting stuff; totally missed the log sysctl.
The netstat(8) reveals some interesting info about a persistent failover
condition:
$ netstat -sp carp
carp:
7731906 packets received (IPv4)
0 packets received (IPv6)
0 packets discarded for bad interface
I'm building -current right now. I'm looking forward to improvements
between vlan(4) and carp(4) post 3.7.
I'm curious: Are there any new debugging mechanisms for carp(4) in
-current/4.x ? I was looking at ip_carp.{c,h} changelog. It doesn't seem
obvious if there are.
I.e., does
On Tue, Oct 10, 2006 at 05:50:50PM -0400, Brian A. Seklecki wrote:
Certainly a way to log events (interfaces, etc.) and the resulting actions
taken by the code would be useful in mission critical environments.
Anything beats tcpdump 'proto carp' and making guesses from there.
Nothing new to
3 matches
Mail list logo
