I've added a section on the host_tracker component to the documentation -- mostly just by copy/pasting from the docstring in the code. (Since the POX documentation is a wiki, anyone could have done this.)
Also, it's worth noting that the version of host_tracker in the carp branch has at least one significant improvement over the one in the betta branch -- it raises events when things change. -- Murphy On Jun 20, 2013, at 8:09 AM, Basavesh Shivakumar wrote: > Hi Kyriakos, > > Thank you very much. That was much needed info. It would be great if you > (/pox developers) can add that info to pox documentation. > > > On Thu, Jun 20, 2013 at 8:01 PM, Kyriakos Zarifis <[email protected]> > wrote: > Hi Basavesh, > > have you taken a look at the host_tracker? > > https://github.com/noxrepo/pox/tree/betta/pox/host_tracker > > > On Thu, Jun 20, 2013 at 7:49 AM, Basavesh Shivakumar > <[email protected]> wrote: > Hi, > > I want to collect topology information from pox controller. I'm able to > collect Switches and link between switches via event raisers. I need to > collect hosts information also. > > sol: > Initially all flow tables should be empty and we should do something like > pingall, from that there will be packet_in messages from connected switches. > By analysing those packets we will get to know Host's IP + MAC and its > connection to switch. > > Is there any other method to discover hosts? > > > -- > Regards, > Basavesh A S > Final year CSE B.Tech > NITK Surathkal > > > > > -- > Regards, > Basavesh A S > Final year CSE B.Tech > NITK Surathkal
