From: Vivien Didelot
Date: Thu, 8 Sep 2016 12:50:43 -0400
> If /sbin/bridge-stp is available on the system, bridge tries to execute
> it instead of the kernel implementation when starting/stopping STP.
>
> If anything goes wrong with /sbin/bridge-stp, bridge silently falls back
> to kernel STP,
Hi Stephen,
Stephen Hemminger writes:
> On Thu, 8 Sep 2016 12:50:43 -0400
> Vivien Didelot wrote:
>
>> If /sbin/bridge-stp is available on the system, bridge tries to execute
>> it instead of the kernel implementation when starting/stopping STP.
>>
>> If anything goes wrong with /sbin/bridge-
On Thu, 8 Sep 2016 12:50:43 -0400
Vivien Didelot wrote:
> If /sbin/bridge-stp is available on the system, bridge tries to execute
> it instead of the kernel implementation when starting/stopping STP.
>
> If anything goes wrong with /sbin/bridge-stp, bridge silently falls back
> to kernel STP, m
If /sbin/bridge-stp is available on the system, bridge tries to execute
it instead of the kernel implementation when starting/stopping STP.
If anything goes wrong with /sbin/bridge-stp, bridge silently falls back
to kernel STP, making hard to debug userspace STP.
This patch adds a br_stp_call_use