Sorry to bother you again. I have two issues regarding both authenticator module and routing module. Please look at the code in sprouting.cc, set_route() function.
1, The inport is from fi.src_location.location->dpport. Can you explain the structure of the location variable? How it maintains both datapathid and port number? My actual concern is: Sometimes, packets will get broadcasted before a route is calculated. When a broadcasted packet hit another switch, the inport also changed. I understand route.id.src is the real ingress switch, so, the whole procedure is to find a route from the src datapath, not current datapath. But sometimes, because of this, it consistently show "Packet not on route" and freezes there. I guess this is because the controller is always processing at this "Packet not on route" but not continue. 2, Sometimes the egress datapath read from the authenticator module is not the closest one to the dst mac. This makes the flow sent to different datapath other than the correct one. Is this a known bug or is this not important? Our experiment shows this sometimes matters. Thanks. _______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
