If you look at authenticator.hh, you will see the AUTH_WITH_ROUTING #ifdef When this is enabled, the authenticator component depends on the application named "routing_module" (which is basically just a library). The application named "routing" meanwhile (defined by sprouting.hh/.cc) will actually route flows based on the flow-in events it sees. I was just saying that AUTH_WITH_ROUTING can be enabled without running the "routing" application since it only depends on the library (thus allowing someone to run a different routing application should they so choose).
On Fri, Mar 12, 2010 at 4:11 PM, Guanyao Huang <gyhu...@ucdavis.edu> wrote: > Sorry. > I dont quite follow your reply below. > Do you mean I just enable AUTH_WITH_ROUTING then the existing routing > module will work? I canot find this AUTH_WITH_ROUTING > What do you mean by "which depends on the routing_module library, > NOT the sprouting.hh/sprouting.cc component"?? > > > Finally, in regard to the presence of multiple locations for a given mac > > address. We found the need for this in certain topologies where a host > was > > effectively connected to two distinct openflow ports in the network, > > sending/receiving packets on both using the same mac address. If this > > doesn't happen in your topologies, and the AUTH_WITH_ROUTING ifdef is > > enabled in authenticator.hh (which depends on the routing_module library, > > NOT the sprouting.hh/sprouting.cc component) then you should not be > seeing > > multiple locations, or they should be timing out. > > Feel free to resend any questions I missed. > > Natasha > >> > >> On Fri, Mar 12, 2010 at 1:40 PM, Srini Seetharaman > >> <seeth...@stanford.edu> wrote: > >> > Just to add to Guanyao's observations: I wanted to mention that the > >> > host having two bindings is something we run across often in our > >> > Stanford setup. However, we notice it only when the topology is > >> > changed during runtime. > >> > > >> > Srini. > >> > > > > > >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
