DragonFly bugs List (threaded) for 2008-07
Re: [issue957] CARP panic
On 7/11/08, Petr Janda <email@example.com> wrote:
> Can you please commit the fix?
Using ETHER_INPUT2 is tied with the CARP lock flag changing. Using
ETHER_INPUT2 by default is a little bit risky for this release and
ipflow can't be worked out in compat fashion. You can just keep the
patch locally; if you have other NICs that you want to use it with
CARP, please just tell me. Currently following NICs has ETHER_INPUT2
support (so I could test that code path from day to day before release
bge(4) bce(4) em(4) et(4) msk(4) nfe(4) re(4), bfe(4) fxp(4) xl(4)
Once release is done, I will switch to ETHER_INPUT2 in repo; along
with the CARP lock flag changing of course.
Live Free or Die