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 ifconfig(8)'ing the DEBUG flag onto the interface generate any
helpful output to log(9)? Something along the lines of what you would get
from "debug standby error", "debug standby event", "debug standby terse"
in an IOS environment?
Anything to help debug the decision making algorithm used in
master/standy/backup election process.
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.
TIA,
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
