I don't think I'm aware of any bugs that would cause this in stock NOX, but can you retry with the destiny branch? If it continues to happen with the destiny branch, can you please use tcpdump or wireshark to send a trace of the connection between NOX at the switch?
-- Murphy On Friday, May 27, 2011 10:36:10 AM ahmad numan wrote: > ./nox_core -V gives output > > "*NOX 0.9.0(zaku)~full~beta (nox_core)*" > > I download using git* > * > > *git clone git://noxrepo.org/nox* > > > Ahmed bilal > > On Fri, May 27, 2011 at 9:12 PM, Murphy McCauley <[email protected]> wrote: > > Which version of NOX is this? Has it been modified at all? > > > > -- Murphy > > > > On Friday, May 27, 2011 05:58:16 AM ahmad numan wrote: > > > Hello > > > I configured a linux powered machine to run as OpenFlow switch (OVS) > > > and connect it with out-of-band NOX controller (NOX controller was > > > > initialized > > > > > by following instruction "*nox_core -i ptcp:6633 routing*"). When I > > > connected the switch with controller i got following error message > > > > > > *openflow-event|ERR:received Openflow error packet from > > > > dpid=002320ba0007: > > > type=1, code=7, 24 bytes of data* > > > > > > and the "*ovs-openflowd*" terminal showed following error* > > > > > > "attempt to reuse the buffer*" > > > > > > while discussing on ovs-discuss mailing list they suggest that "Send a > > > given buffer_id only in a single OpenFlow request". Guide me how can I > > > solve this problem > > > > > > Thanks > > > Ahmed Bilal _______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev
