Dear Murphy KK,
Thanks for your kindly reply and help. Just like KK mentioned, we might need
an IGMP multicast. So, in this point, we must do something on NOX. That is,
we need to implement a data structure that do the same thing as Group table
for recording which ports have IGMP request. Is is
Hi,
although that would take some effort, it is perfectly doable to hold that
information on your component. You wouldn't have to use v1.1 tables or
anything like that, all the state would be on your controller. While there
are several packet types of packets included in the packet parsing
Dear Kyriakos,
Thanks for your quickly help. Last week, I found in lib/packet have some
files, such as arp or icmp. That time, I think may not follow them to do
similar thing. But after your explanation, I think we are wrong and must to
do it. The other thing is we also record which ports contain
On Wed, Mar 30, 2011 at 11:38 PM, Jen-Wei Hu jenwe...@gmail.com wrote:
Dear Kyriakos,
Thanks for your quickly help. Last week, I found in lib/packet have some
files, such as arp or icmp. That time, I think may not follow them to do
similar thing. But after your explanation, I think we are
Hi Jen-Wei,
OpenFlow 1.1 (implemented) is released, so it is quite final for me.
Also, if you are not constrained to using the group semantics (in
OpenFlow 1.1), you can do multicast by listing all the ports you want
to multicast to in the flow_mod command.
If you are looking for IGMP multicast
