On Sun, Mar 16, 2014 at 12:50 AM, Ben Pfaff wrote:
> On Wed, Mar 12, 2014 at 03:31:26PM +0800, Kmindg G wrote:
>> On Wed, Mar 12, 2014 at 1:41 PM, Ben Pfaff wrote:
>> > On Sun, Mar 09, 2014 at 05:48:52PM +0800, kmindg wrote:
>> >> The restriction only allows to send bpdu in forwarding state in
>>
On Wed, Mar 12, 2014 at 03:31:26PM +0800, Kmindg G wrote:
> On Wed, Mar 12, 2014 at 1:41 PM, Ben Pfaff wrote:
> > On Sun, Mar 09, 2014 at 05:48:52PM +0800, kmindg wrote:
> >> The restriction only allows to send bpdu in forwarding state in
> >> compose_output_action__. But a port could send bpdu in
On Wed, Mar 12, 2014 at 1:41 PM, Ben Pfaff wrote:
> On Sun, Mar 09, 2014 at 05:48:52PM +0800, kmindg wrote:
>> The restriction only allows to send bpdu in forwarding state in
>> compose_output_action__. But a port could send bpdu in listening
>> and learning state according to comments in lib/stp.
On Sun, Mar 09, 2014 at 05:48:52PM +0800, kmindg wrote:
> The restriction only allows to send bpdu in forwarding state in
> compose_output_action__. But a port could send bpdu in listening
> and learning state according to comments in lib/stp.h(State of
> an STP port).
>
> Signed-off-by: kmindg
The restriction only allows to send bpdu in forwarding state in
compose_output_action__. But a port could send bpdu in listening
and learning state according to comments in lib/stp.h(State of
an STP port).
Signed-off-by: kmindg
---
lib/stp.c| 9 +
lib/stp.h
