[nox-dev] Simplerouting component on pronto 3290

Hi all,I am trying to test routing on pronto 3290 switch.below is my test bed                                     NOX controller(destiny)                                               |=(internet)                                            SW2 

[nox-dev] Question about how do arguments of callback method in component come out?

Dear All, I'm confused about how do arguments for method callback in component come out. For example, I register an event in install like self.register_for_packet_in(packet_in_callback). Then, I can do some stuff corresponding to packet_in_event in packet_in_callback method. My question i

Re: [nox-dev] Adding DNS functionality to nox

You're not missing anything; that's about it. -- Murphy On Aug 18, 2011, at 1:30 AM, ibrahim mun wrote: > Hi, I'm using zaku, I wonder if I can use dnsspy.py to add basic dns > functionality to NOX. > As I understand, Running the dnsspy component will allow nox to match and > parse DNS packets

[nox-dev] Adding DNS functionality to nox

Hi, I'm using zaku, I wonder if I can use dnsspy.py to add basic dns functionality to NOX. As I understand, Running the dnsspy component will allow nox to match and parse DNS packets, so I can modify "handle_dns" to create a DNS replay and send it out to the inport, right? Am I missing somethi