I think some document of authenticator module is very necessary. The newest version of authenticator module seems changed a lot, but the code for routing module remains the same. For example, why there are many events defined in host_event.hh, why there are many entries, bindings defined in authenticator.hh. Normally, given a mac address, or, IP address, what is the API used to get its datapath? Without such things, I feel easily get lost in the code. I guess many people are developing their own module based on flow_in event. It would be nice if they know how this flow_in event was generated.
On Fri, Mar 12, 2010 at 1:40 PM, Srini Seetharaman <[email protected]> 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 [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
