On Wed, Mar 12, 2014 at 05:00:09PM +0900, YAMAMOTO Takashi wrote:
> > On Wed, Mar 12, 2014 at 12:00:12PM +0900, YAMAMOTO Takashi wrote:
> >> > A packet_in message may be sent for one of two reasons.
> >> >
> >> > 1. As the result of an controller action supplied in a rule.
> >> >This is execut
> On Wed, Mar 12, 2014 at 12:00:12PM +0900, YAMAMOTO Takashi wrote:
>> > A packet_in message may be sent for one of two reasons.
>> >
>> > 1. As the result of an controller action supplied in a rule.
>> >This is executed if a packet matches the match for the rule.
>> >The packet_in reason
On Wed, Mar 12, 2014 at 12:00:12PM +0900, YAMAMOTO Takashi wrote:
> > A packet_in message may be sent for one of two reasons.
> >
> > 1. As the result of an controller action supplied in a rule.
> >This is executed if a packet matches the match for the rule.
> >The packet_in reason is expl
> A packet_in message may be sent for one of two reasons.
>
> 1. As the result of an controller action supplied in a rule.
>This is executed if a packet matches the match for the rule.
>The packet_in reason is explicitly part of the action and
>is thus correct.
for OFPACT_CONTROLLER (
A packet_in message may be sent for one of two reasons.
1. As the result of an controller action supplied in a rule.
This is executed if a packet matches the match for the rule.
The packet_in reason is explicitly part of the action and
is thus correct.
2. As the result of the failure to
