Hi Timo, Oflops is at best in an alpha state right now, although I've been working with a bunch of people to improve it. Thanks for your patience with it.
About your questions: - the "found unmarked probe" message is harmless and you can ignore it. All it means is that oflops has found a packet that is not part of the test. This could easily happen if your switch is sending STP discovery messages or any other type of probe. - about the segmentation fault, I haven't seen this. Are you able to replicate this behavior running with a different switch (for examle, OVS or the stanford reference switch)? Knowing how to replicate the problem could help with debugging it. Thanks, - Rob . On Mon, May 16, 2011 at 10:30 AM, Timo Sperveslage <[email protected]> wrote: > Hello, > > regarding to a students project me and my colleague want to use the example > modules "packet_in" and "port_status" for the oflops controller. We > connected a broadcom switch and a pc over a second switch which is connected > to the university network. > > - The port_status test answers just "found unmarked probe" although all open > flow packets were send and acknowledged as TCP packets. > > - Regarding the test packet_in we get the message "segmentation fault" after > the initial statistic: > Ether type 0 received !=1 sent > Ether type 101 received !=1 sent > Ether type 0 received !=1 sent > > Any advice would be helpful! > > Best regards, > Timo Sperveslage & Florian Fiedler > > > > _______________________________________________ > openflow-discuss mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
