Thank you very much.
In answer to your question, I´m looking just reporting routing-related
information. For example, when a new ip adress is added.
I want to implement Quagga code with snmp daemon inside. So, if I install
Quagga in a PC(1), it is not necessary to install Net-SNMP.
>From another PC(2), for example, I want to get the "routing table" with
MRTG.
PC(1) has the agent, and answers it.
In conclusion, I think I have to implement a new daemon into quagga, the
snmpd. What do you think?
2010/11/23 Dave Shield <d.t.shi...@liverpool.ac.uk>
> On 23 November 2010 15:29, Quagga Snmp <quaggas...@gmail.com> wrote:
> > In this situation, in PC(1) is necessary to install two things: quagga
> AND
> > stock snmpd.
>
> > In my project, I want the snmp daemon into quagga.
> > I need install only one thing: quagga
>
> I think that's somewhat misleading.
>
> In the current configuration, you need to install two packages
> (snmpd and quagga) - agreed. In your proposed configuration,
> you'd still need to install two packages - quagga, and the snmpd
> module.
> This feels like essentially the same software requirements.
> You're just changing the relationship between them.
>
>
> Another thing that's not immediately clear to me is the range
> of information that you'll need this combined system to handle.
> Are you looking at *just* reporting the routing-related information,
> or would the agent module still handle all the other data (network
> statistics, running and installed software, disk and hardware info,
> etc, etc) ?
>
>
>
> In answer to your original question:
>
> > Is it posible to extract snmpd of the Net-Snmp ?
>
> The code for the agent is to be found within the 'agent' subdirectory
> of the source tree. Note that you'll also need the code under 'snmplib',
> which is the core SNMP library.
> Plus some way of selecting the appropriate code files for the particular
> architecture that you are targeting - this is currently handled by the
> Net-SNMP 'configure' script, but I strongly suspect that Quagga will
> itself come with a configure script already.
>
>
> I would agree with Steve that this is not a particularly sensible
> approach.
> But if you're determined to go down this route, then you should probably
> start by looking at the code in 'agent/snmpd.c'. This is the file that
> handles the specifics of running the agent as a standalone daemon,
> including the main event loop.
> You'll need to construct an equivalent structure that fits into the
> Quagga
> module framework, which listens for incoming requests on port 161,
> and then call 'snmp_read' (or similar). This should then invoke the
> normal agent handling code, and everything else should flow as before.
>
> Good Luck (You'll need it!)
>
> Dave
>
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
