Trap issue agent-addr header
Opmanager filter trap snmp bases on agent-addr header in the PDU instead of real sender IP. This is real problem for most snmp agent because agent-addr is the first active interface.
DUMP
10:20:58.356873 IP 10.10.4.10.55184 > Opmanager.162: C=agilan Trap(502) E:6876.4.3 195.238.251.2 enterpriseSpecific s=203 213976554 [|snmp]
ANOTHER ONE
18:12:00.165411 IP 10.10.1.210.46585 > Opmanager.162: Trap(91) E:2190 1.0.0.127 enterpriseSpecific s=3 0 E:2190.100.5[|snmp]
net-snmp
In the trap message send from the client to the server using net-snmp, the agent address is the first active interface on the client and not the actual eth port on client that is connected to the server.It scans the list of active interfaces, and takes the first found active IPv4 address.
Is there a fix or a workaround?
DUMP
10:20:58.356873 IP 10.10.4.10.55184 > Opmanager.162: C=agilan Trap(502) E:6876.4.3 195.238.251.2 enterpriseSpecific s=203 213976554 [|snmp]
ANOTHER ONE
18:12:00.165411 IP 10.10.1.210.46585 > Opmanager.162: Trap(91) E:2190 1.0.0.127 enterpriseSpecific s=3 0 E:2190.100.5[|snmp]
net-snmp
In the trap message send from the client to the server using net-snmp, the agent address is the first active interface on the client and not the actual eth port on client that is connected to the server.It scans the list of active interfaces, and takes the first found active IPv4 address.
Is there a fix or a workaround?