Actually the answer is a strong 'yes'. Conceptually, you can send any packet to any place as long as the matching pattern is supported by the switch. There is nothing specific to the controller, it's just the default path in many (most) configurations.
Is it wise to overload the controller functionality - most likely not. Can you use Openflow to 'tap into flows' and send duplicates to some collector - definitely - within bounds of course. CHeers, -max On 02/04/2013, at 3:36 PM, Olivier Mehani wrote: > Hi all, > > I want to confirm my understanding that OpenFlow cannot be used for > packet capture. > > This seems to be implied by quite a few documents where tools such as > PCAP-based applications are used for this purpose, alongside OpenFlow > switches. However, I cannot find any definitive answer about this, and I > would like a strong “no”, if that is the answer. > > I could also try to put the question another way: How would one capture > a significant (e.g., closer to all than to just SYN) packets of a given > flows using OpenFlow (maybe a switch sending all traffic to the > controller?)? Would it be efficient? Is it even sane? > > Thanks in advance, and sorry for the cluelessness of my question. > > PS: CC me on any followups, as I am not subscribed to this list. > > -- > Olivier Mehani <olivier.meh...@nicta.com.au> > PGP fingerprint: 4435 CF6A 7C8D DD9B E2DE F5F9 F012 A6E2 98C6 6655 > > > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments. _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
