cc-ing openflow people. > On May 6, 2016, at 1:41 PM, Ryan Dietrich <[email protected]> wrote: > > So, I have a working southbound plugin using the PacketProcessingListener. > My goal is to read the payload of the OpenFlow 1.3 “PacketIn” message. > This “per packet” approach seems unwieldy, as I am parsing both the Ethernet > header as well as the IP and TCP headers. Is there a “shortcut” ? > > I went searching for a simpler approach and found this file: > > controller/opendaylight/md-sal/sal-binding-broker/src/main/java/org/opendaylight/controller/md/sal/binding/impl/BindingDOMNotificationServiceAdapter.java > > This is what my plugin calls when it registers itself as a packet handler > (implementing the “onPacketReceived”). > > 1. I tried to create another listener using the “OpenflowProtocolListener”, > and used the same approach to register it, but it is never called (I have an > OVS pointed to my controller, and the PacketProcessingListener is logging > like crazy). Do I need to add anything to my yang file beyond the > notification service? Or some other configuration that is not immediately > apparent? > > 2. Can you even listen to PacketInMessage using the notification service? Or > are they considered RPC, and do you implement that differently (similar to > how Toaster implements RPC)? > > … > > Long story short, I’m currently using the PacketProcessingListener, and I > tried to use OpenflowProtocolListener the same way, to get the > “onPacketInMessage” to fire, but it is not working, and I’m not sure if it is > configuration related, or me doing something totally incorrect. > > Thanks to anyone who can give me a pointer in the right direction. > > -Ryan Dietrich > _______________________________________________ > controller-dev mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/controller-dev
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
