RE: trap pdu forwarding [was Re: File Descriptor Event Management]

OS> One last thing. Since the address and port of the trap publisher
will
OS> need to be configurable (snmpd.conf, etc...)

RS> Bad news. While trying to figure out better names for the tokens, I
RS> Realized that there is already a 'forward' token for forwarding
traps.
RS> This already allows specifying an IP address and a port. The big
RS> difference between it and your scheme is that it actually forwards a

RS> SNMP PDU, not a packed net-snmp pdu
RS> structure.

Actually might be good news for me. I assume you can specify the
protocol
to use too? TCP/UDP?

RS> So now I'm thinking that your patch might be slightly redundant. Had
you
RS> thought of using the existing mechanism? If so, why do you prefer
the
RS> method you came up with?

I think what it was is the forward function was not available back when
I
was writing this code (couple years back). Maybe it was and I didn't
realize it. How does one receive the PDU on the other side? It seems
like
I may just be able to put this PDU reception code into my management app
in
place of what I currently have (pack/unpack). This would be good. Can
you
point me to the code that does this?

This would be really good because then my system can go back to using an

unmodified NET-SNMP baseline. Right now we have our own rpm that we
install
and each time we need to upgrade to a new version of NET-SNMP it is a
pain.

Thanks,
Sten



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders