On Sun, Sep 30, 2012 at 1:46 AM, Ben Pfaff <b...@nicira.com> wrote:

> I don't see an OpenFlow 1.0 error code for the latter.  I don't think
> it's really an error.
>

True - this condition of the same in_port and out_port is not explicitly
called out in the spec.
Read this in one of the posts:

" If the controller sends action output:port X where X is also the input
port
that a packet came in on, a correctly behaving switch is supposed to drop
the offending flow_mod/packet_out and send a OFPBAC_BAD_OUT_PORT error.
This is a good thing, IMHO, as it prevents the most trivial class of
accidental  loops in the network."

My switch allows such a flow to be created but takes no actions and does
not send back the packets.
Thanks.


>
> On Sat, Sep 29, 2012 at 12:32:16PM -0700, Rob Sherwood wrote:
> > There are a number of cases that should result in an error code with
> > bad port.  One if is it doesn't exist.  Another if if you try to send
> > out a port that is the same as the in_port.
> >
> > - Rob
> > .
> >
> > On Sat, Sep 29, 2012 at 3:34 AM, Reid Price <reid.pr...@gmail.com>
> wrote:
> > > Off the top of my head, I would check to see what the exact definition
> of
> > > 'invalid' is.  Your subject seems to imply it is the same as 'does not
> > > exist'. What if you do port 'abc'?
> > >
> > > On Sep 29, 2555 BE, at 7:55, bhaskar jain <bhaskar.jain2...@gmail.com>
> > > wrote:
> > >
> > > Hi,
> > >
> > >  I am trying to make a  OF 1.0 conforming switch. Am unable to check
> this
> > > condition:
> > >
> > > must return a of_error_msg with OFPET_BAD_ACTION type,
> OFPBAC_BAD_OUT_PORT
> > > code if a flow mod message contains an invalid port. (Section 4.6)
> > >
> > > From ovs-ofctl tool, we can set a bad output port but I don't see any
> > > incoming error code. Is there a way to test this scenario. Thanks.
> > >
> > > bash-3.00# ./ovs-ofctl mod-flows sw0
> > > in_port=6,idle_timeout=30,actions=output:33 -v
> > > Oct 07 05:07:25|00001|ofctl|INFO|connecting to
> > > unix:/var/run/openvswitch/sw0.mgmt
> > > Oct 07 05:07:25|00002|vconn|DBG|unix:/var/run/openvswitch/sw0.mgmt:
> sent
> > > (Success): hello (xid=0x5165d):
> > > Oct 07 05:07:25|00003|vconn|DBG|unix:/var/run/openvswitch/sw0.mgmt:
> > > received: hello (xid=0x45b82):
> > > Oct 07 05:07:25|00004|vconn|DBG|unix:/var/run/openvswitch/sw0.mgmt:
> > > negotiated OpenFlow version 0x01 (we support versions 0x01 to 0x01
> > > inclusive, peer no later than version 0x01)
> > > Oct 07 05:07:25|00005|vconn|DBG|unix:/var/run/openvswitch/sw0.mgmt:
> sent
> > > (Success): flow_mod (xid=0xa9f8e):in_port=6, MOD: cookie:0x0 idle:30
> hard:0
> > > pri:32768 buf:0xffffffff flags:0 actions=output:33
>
_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss

Reply via email to