Makes sense to me.
-Andrew
On Apr 7, 2012, at 4:02 AM, Andrew Thompson wrote:
> On 3 April 2012 00:35, John Baldwin wrote:
>> On Friday, March 30, 2012 6:04:24 pm Andrew Boyer wrote:
>>> While investigating a LACP issue, I turned on LACP_DEBUG on a debug kernel.
>> In this configuration it's ea
On 3 April 2012 00:35, John Baldwin wrote:
> On Friday, March 30, 2012 6:04:24 pm Andrew Boyer wrote:
>> While investigating a LACP issue, I turned on LACP_DEBUG on a debug kernel.
> In this configuration it's easy to panic the kernel - just run 'ifconfig lagg0
> laggproto lacp' on a lagg that's a
On Friday, March 30, 2012 6:04:24 pm Andrew Boyer wrote:
> While investigating a LACP issue, I turned on LACP_DEBUG on a debug kernel.
In this configuration it's easy to panic the kernel - just run 'ifconfig lagg0
laggproto lacp' on a lagg that's already in LACP mode and receiving LACP
messages
While investigating a LACP issue, I turned on LACP_DEBUG on a debug kernel. In
this configuration it's easy to panic the kernel - just run 'ifconfig lagg0
laggproto lacp' on a lagg that's already in LACP mode and receiving LACP
messages.
The problem is that lagg_lacp_detach() drops the lagg wl
