On Wed, 2012-02-29 at 13:25 +0100, Zeljko Mihelcic wrote:
> Hello Dave
> Thanks for the command, but this is not what I'd like to have....
> Namely, on the client side is received:
>  
> "......neta4-pm:/home/easfsc# tcpdump -nnr traps40.pcap
> reading from file traps40.pcap, link-type EN10MB (Ethernet)
> 10:39:20.740420 IP 10.140.20.71.56185 > 10.140.20.69.162:
> V2Trap(251)  .1.3.6.1.2.1.1.3.0=1286381362 
> .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.193.109.2.0.3 
> .1.3.6.1.4.1.193.72.500.1.1.0="EAN" 
> .1.3.6.1.4.1.193.72.500.1.2.0="EAN=10.93.112.14,EFN324xf,Port=1002.0.12" 
> .1.3.6.1.4.1.193.72.500.1.3.0=24 
> .1.3.6.1.4.1.193.72.500.1.4.0=1 
> .1.3.6.1.4.1.193.72.500.1.4.0=07_dc_01_11_0d_02_37_59_2b_00_00 
> .1.3.6.1.4.1.193.72.500.1.6.0=2 .1.3.6.1.4.1.193.72.500.1.7.0=65
> neta4-pm:/home/easfsc#....."
>  
> Note: IP 10.140.20.71.56185 is Agent's IP  !!!
>  
> Back, to my problem:
> I'd like to use the command snmptrap (?) to reach following scenarios
>  
>              Agent                                   Client
>           (10.140.20.71)                         (10.140.20.69)
>                |                                       |
>    snmptrap *  |                                       |
>    =========>  |                                       |
>                |          Notification (SNMP v2)       |
>                |       ============================>   |
>                |       source  **                      |
>                |       destination (10.140.20.69)      |
>                |       and so on...                    |
>                |                                       |
>                |                                       |
>  
> * a) snmptrap -v 2c  [COMMON OPTIONS] [-Ci] uptime trap-oid [OID TYPE
> VALUE]...
>      Note: there is no possibility to generate wanted source with this
> command,
>            i.e. Agent address (10.140.20.71) will be always in
> source  ....as in an example above
>   b) snmptrap -v 1 [COMMON OPTIONS] [-Ci] destination enterprise-oid
> agent generic-trap specific-trap uptime [OID TYPE VALUE]
>      Note: there is possibility to generate wanted source (parameter
> agent) with this command, but the protocol
>            to the client is not SNMP v2   !!!

As a matter of fact this is wrong. In both case a) and case b) the
source address of the package is set to 10.140.20.71. The agent
parameter to v1-traps does not affect the source address, it only
affects the agent-addr data field of the package. Proxies that translate
to v2-notifications should convert that to a data item with OID
snmpTrapAddress.0.

You could use the agentxtrap command to, as your picture shows, tell the
agent to issue a trap or notification in accordance with it's
configuration but there would still be no support for source address
spoofing.

/MF



------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to