Unfortunately, the rest of the original discussion went off-list. Yes, a change of behavior in OVS (which probably brings it more in-line with the intention of the OF spec) caused this. In short, there are places in destiny where it uses the OFPP_CONTROLLER virtual port where it should actually use the OFPP_NONE virtual port (e.g., as the source port for messages generated by the controller). These should be changed.
-- Murphy On Jul 25, 2012, at 12:41 AM, Neha Jatav wrote: > I am getting the same error. I got it from destiny. I'm using openvswitch on > FC17. > > ./nox_core --version > NOX 0.9.1~full~beta (nox_core), compiled Jul 11 2012 23:12:53 > > Along with the nox inside the VM > (http://www.openflow.org/wk/index.php/OpenFlow_Tutorial), the same in_port > worked. The version for that was: NOX 0.9.0(zaku)~full~beta (nox_core), > compiled Oct 13 2011 17:49:51 > > > On Thu, Jul 19, 2012 at 12:32 PM, Murphy McCauley <[email protected]> > wrote: > What repository on github did you clone this from? What does ./nox_core > --version say? > > -- Murphy > > On Jul 18, 2012, at 11:50 PM, crayon z wrote: > > > Hi all, > > > > I installed NOX with the code cloned from github and connect OVS > > with NOX successfully. However, when I tried out the monitoring and routing > > app, it turned out some errors, the console log is as follows: > > > > 00592|openflow-event|ERR:received Openflow error packet from > > dpid=000743104570: type=45250, code=0, 72 bytes of data > > > > And the ovs-ofctl snoop result shows: > > > > OFPT_ERROR (xid=0x0): type OFPET_BAD_REQUEST, code NXBRC_BAD_IN_PORT > > (***truncated to 64 bytes from 66***) > > 00000000 01 0d 00 42 00 00 00 00-ff ff ff ff ff fd 00 08 |...B............| > > 00000010 00 00 00 08 00 01 00 00-01 23 20 00 00 01 00 07 |.........# .....| > > 00000020 43 10 45 70 88 cc 02 0f-07 64 70 69 64 3a 37 34 |C.Ep.....dpid:74| > > 00000030 33 31 30 34 35 37 30 04-03 02 00 01 06 02 00 78 |3104570........x| > > ^COFPT_PACKET_OUT (xid=0x0): in_port=CONTROLLER actions_len=8 > > actions=output:2 data_len=42 > > 00:07:43:10:45:70 > 01:23:20:00:00:01, ethertype LLDP (0x88cc), length 42: > > > > It seems that the in_port shouldn' t be CONTROLLER, but how can I > > fix this? > > > > > >
