On Feb 2, 2013, at 10:28 AM, Weiyang Mo wrote: > Thanks. Corrently I consider this because sometimes it's more convenient to > create a new module for some specific traffic with running a general module > at the same time. > > For example, If I need handle UDP traffic according to the data rate > specificly, I create a new module called handleUDP.py. However for other > traffic still go shortest hops (l2_multi). > > Currently for safety, I should also revise l2_multi to exclude the UDP > traffic (e.g. insert flowentry if packet not UDP) because l2_multi listens to > packet_in and set entries for all types of traffic, which probably a > confliction.
You don't need to alter l2_multi. Add a PacketIn handler with a higher priority than default. If you don't want l2_multi to see the packet, halt the event. The misc.mac_blocker component is an example of this. -- Murphy
