Re: [Pysnmp-dev] Receiving Traps Question

[Ilya E. <il...@gl...>]

Twisted dispatcher will surely be a part of pysnmp. I did not commit it 
into CVS yet because I'm trying to make sure it is done in a way 
consistent with Twisted spirit (and I'm not a Twisted expert).

As for Notification Originators identification - I'm trying to figure out
how it's supported to be done within the SNMPv3 standard. So far my 
impression is that you have to use peer's contextEngineId/contextName,
as comes with Notification, then lookup Manager's LCD for corresponding 
transport information.

Although I'm still not sure how this mechanism should work in SNMPv1/v2c 
compatibility mode. If you have any ideas on the subject, please, let me 
know. Meanwhile, I'm trying to figure that out.

-ilya

> First let me say thanks for pysnmp. Its quite nice. And thanks to Filippo for 
> the twisted dispatcher. Thats working great for me. Is that going to get 
> committed into CVS soon?
>
> I've been hacking on examples/v3arch/manager/ntfrcv.py and it works fine.
>
> I need to receive v1/v2/v3 traps from many sources in the same network so its 
> not possible to determine who the trap is from by authentication info.
>
> Is there an API through which I can determine who sent the trap in cbFun()?
>
> Once I get the trap, I need to query the device.