Hi Aaron, First I'd like to thank you for the help with the code, I believe without your tip I wouldn't be able to progress any further. But now I'm stumbling with a new problem... :-) After following your idea with the flow match and using the "register_for_packet_in" NOX event, I was finally able to not just install the flows but also I was able to connect the hosts from the topology scenario, but the OFPAT_SET_VLAN_VID doesn't seem to work in the way I was expecting, in other words, it seems that isn't adding the VLAN tag since I'm getting empty results from Wireshark, when I filter for VLAN. Below some information that I believe will be helpfull:
Code: http://pastebin.com/XBfAJht0 Switch 1 dump-flow: http://imageshack.us/photo/my-images/717/dumpswitch1code2.png/ Switch 2 dump-flow: http://imageshack.us/photo/my-images/254/dumpswitch2code2.png/ If anyone have some tip or solution for this problem, I would really appreciate it. Thanks in advance, Daniel PS.:Sorry for the double email, gmail unconfigured the first one. Em 29 de novembro de 2011 22:49, Daniel de Arêa Leão <daniel.area.l...@gmail.com> escreveu: > Hi Aaron, > First I'd like to thank you for the help with the code, I believe > without your tip I wouldn't be able to progress any further. But now > I'm stumbling with a new problem... :-)After following your idea with > the flow match and using the "register_for_packet_in" NOX event, I was > finally able to not just install the flows but also I was able to > connect the hosts from the topology scenario, but the > OFPAT_SET_VLAN_VID doesn't seem to work in the way I was expecting, in > other words, it seems that isn't adding the VLAN tag since I'm getting > empty results from Wireshark, when I filter for VLAN.Below some > information that I believe will be helpfull: > Code: http://pastebin.com/XBfAJht0Switch 1 dump-flow: > http://imageshack.us/photo/my-images/717/dumpswitch1code2.png/Switch 2 > dump-flow: http://imageshack.us/photo/my-images/254/dumpswitch2code2.png/ > If anyone have some tip or solution for this problem, I would really > appreciate it. > Thanks in advance,Daniel > Em 29 de novembro de 2011 01:55, Aaron Rosen <aro...@clemson.edu> escreveu: >> You need to do something with flow to tell it what you want to match on. Try >> adding something like >> >> flow[core.IN_PORT] = inport >> >> >> Aaron >> >> 2011/11/28 Daniel de Arêa Leão <daniel.area.l...@gmail.com> >>> >>> Hi, >>> >>> I'm a newbie in NOX and Python and I'm trying to create a VLAN path >>> using NOX. After some researches I was finally able to create a >>> component that at least doesn't show any kind of compilation error, >>> but it also doesn't work as I expect... It seems that it doesn't >>> install the flow on the switch. >>> Below, some informations that I believe that will be helpfull: >>> In the environment that I've created, I'm using NOX 0.9.0 (zaku) and >>> Mininet 1.0.0. In the Mininet, I am using "linear 2" as the topology >>> scenario. >>> >>> Command lines that I have used: >>> # ./nox_core -v -i ptcp:6634 dcnflow >>> # mn -x --mac --controller=remote --ip=192.168.56.101 --port=6634 >>> --topo linear,2 >>> >>> My code for the component: http://pastebin.com/2Ue7Hpmr >>> >>> And here some logs that I collected: >>> dpctl show log: http://imageshack.us/photo/my-images/522/dpctl.png/ >>> dpctl dump-flows: http://imageshack.us/photo/my-images/853/dumpt.png/ >>> NOX log: http://pastebin.com/cRDzYi7F >>> >>> Does anyone have a tip or a solution for this problem? Reaffirming >>> that I want to create a VLAN path. >>> >>> Thanks in advance, >>> Daniel >>> _______________________________________________ >>> nox-dev mailing list >>> nox-dev@noxrepo.org >>> http://noxrepo.org/mailman/listinfo/nox-dev >> >> >> >> >> -- >> Aaron O. Rosen >> Masters Student - Network Communication >> 306B Fluor Daniel >> >> _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
