[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 / \ / \HOST1(192.168.1.1) --- SW1 Sw3-HOST2(192.168.1.2)and I run command line "./nox_core -i ptcp:6699 -v spanning_tree simplerouting"But, I can't ping from HOST1 to HOST2.I don't know why I can't ping.any suggestion ?and is below message fatal error ?00643|openflow-event|ERR:received Openflow error packet from dpid=423456abcdef: type=2, code=4, 80 bytes of data00644|openflow-event|ERR:received Openflow error packet from dpid=423456abcdef: type=2, code=4, 80 bytes of data00645|openflow-event|ERR:received Openflow error packet from dpid=223456abcdef: type=3, code=0, 80 bytes of data00646|openflow-event|ERR:received Openflow error packet from dpid=223456abcdef: type=3, code=0, 80 bytes of data Best Regards, Min-Hyup KANG ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[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 is in the def packet_in_callback(dpid, inport, reason, len, bufid, packet) how do the arguments dpid, inport, reason, len, bufid, packet come out ? I understand that according to registering different events, NOX would generate corresponding parameters for using by corresponding callback method. Such as for packet_in_event, NOX generate dpid, inport, reason, len, bufid, packet. For datapath_leave event, NOX only generate parameter dpid for callback method uses. Is my understanding right? If not, could someone explain how do these arguments for callback method come out? Thank you very much in advance. Best regards, Chen ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
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, so I can modify "handle_dns" to create a DNS replay and > send it out to the inport, right? Am I missing something? > > Thanks, > > Ibrahim > ___ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[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 something? Thanks, Ibrahim ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
