Thanks for clarifying. Regards, Raksha

Hi John, you can inspect traffic via wireshark and also add a callback to listenable future returned by the flowServvice.addFlow(). ... Futures.addCallback(listenableFuture, ...inline function

Your solution solvet it, although now, when I set the Ipv4Match field, the flow is not inserted in the switch (although no error is thrown).IOt says it is inserted correctly but nothing

I l come back if I have questions Thank you On Mon, Nov 30, 2015 at 5:30 PM, Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...> wrote:

Yes, exactly. Please get inspired by: (/openFlowPlugin/test-common) org.opendaylight.openflowplugin.testcommon.DropTestRpcSender#processPacket Regards, Michal

Hi Michal, So, I should specify the node-ref identifier in the code?Right? Thanx in advance On Mon, Nov 30, 2015 at 4:38 PM, Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...>

Hi Giannis, add-flow is routed rpc and needs a node-ref identifier in input (field "node"). This error message usually appears when the node is not connected or the identifier is completely missing

I try to push some flows programmatically to some switches but I get this error: WriteFlow Error: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No local or

Hi Raksha, there is currently no way how to register your deserializer from outside of openflowjava. The only option would be to add it into openflowjava directly and build the project

Hi, I am trying to write a java program that can benchmark ODL controller. I am building OF messages using openflow-java library, de-serializing the OF messages received from controller. I noticed

Hello Giuseppe, there is a reason behind this implementation. MultipartReply messages are RPCs, but there can be multiple of them delivered from switch to controller (eg. OFPMPF_REPLY_* flags). If

Hi all, I am working with the

Hello, I reviewed the change - I added a few comments, but it looks fine. I also updated some info in the bughttps://bugs.opendaylight.org/show_bug.cgi?id=4473. Regards, Michal Polkorab

As we talked yesterday - thanks for investigating this and finding the issue. Let's hope that will help us support OVS 2.4.

Hi, The current implementation of openflowjava refuses to keep the connection to switches which implements unsupported features. As a result, if a supported switch implements a new feature, it could

Hello guys, I hope this is the right place for my question. I'm trying to migrate my project from helium sr1 to lithium sr1 and I have an issue with setting tunnel dest ip action in a flow. I'm

See if this helps https://wiki.opendaylight.org/view/Editing_OpenDaylight_OpenFlow_Plugin:End_to_End_Flows:Example_Flows --André Martins On 05/11/15 07:56, John Schistos wrote:

Hello, I have the mininet and an ODL controlller up.I would like to be able to write some flow rules to the controller and the controller to pass the flow rules at the switch(in mininet) only if

Hi Michal, I reproduced the same issue using OVS: - Created an OVS fork that return an OFPERR_OFPBAC_TOO_MANY to all flowmods. - openflowplugin is expected to refuse all flowmods because the switch

Hi Michel, You are right, this is what I'm expecting, but openflowplugin always report successful future even if the device return an Error Here is a capture