On 2/4/20 8:27 AM, 'Spencer Neuschmid' via ns-3-users wrote:
> Hi,
>
> I recently downloaded Quagga so that I could do similar analysis to
> OSPF. I was wondering how you went about finding convergence times
> using Quagga OSPF. There is very minimal documentation for using
> Quagga in ns3 and the examples are very minimal in the dce quagga
> directory. My next question is to what extent is quagga integrated in
> ns3? I noticed the examples don't use tracing, csma modules, and many
> other features that you would be able to find in ns3 RIP examples. I
> would also like to track LSA messages being sent on the way to
> convergence and also install simple ping applications as well.
>
> Thank you for any help you can give.
> Spencer
Spencer,
As you discovered, there are not many helpers available for managing
Quagga within ns-3 DCE. The existing examples are more like a
proof-of-concept.
DCE is designed to try to avoid intrusive markup of the application
code, for inserting tracing statements, etc. However, this is less
useful to simulation users, who could use some tracing. Quagga does
have a good logging framework. One brute force way to handle Quagga
traces would be to configure logging in quagga and then post-process,
using separate scripts, the log files that land up in the files-*
directories. However, I'm sure a more elegant hooking of this log
output could be devised.
We are applying to Google Summer of Code and, if accepted, one project
that I would be interested in mentoring would be a project devoted to
improving the integration and usability of Quagga with ns-3. Interested
students, please contact me regarding this.
- Tom