Hi,
that was one of the cases that failed for me.
You can try to have 'clientaddr 10.2.24.121" $HOME/.snmp/snmp.conf
and run
"snmptrap -v3 -u usertest -l authPriv -a SHA -A usertest -x AES -X
usertest 10.2.24.18 84100 …… "
(w/o -s 10.2.24.121)
I hope to get some time to dig into the issue late
Hi,
I found two issues using latest git repo master branch;
IPv4, using "clientaddr srcip" in snmp.conf and "snmptrap" to a local ip -
OK
IPv4, using "clientaddr srcip" in snmp.conf and "snmptrap" to a remote ip -
OK
IPv4, using "snmptrap -s srcip" to a local ip - OK
IPv4, using "snmptrap -s srcip
By routing decision, as I noted before.
RegK
On Fri, May 24, 2019 at 3:23 PM ww wrote:
> Hi.
> Thanks for your reply. I try to use "-s" and "--clientaddr" but it dose
> not work.
> My version is net-snmp-5.8.
> My commond is "snmptrap -v3 -u usertest -l authPriv -a SHA -A usertest -x
> AES -X
Hi.
Any traffic originating from snmpd will have src IP of outgoing network
interface.
>From my experience "clientaddr" helps for replies generated by snmpd. For
example,
if you have multiple interfaces and "clientaddr" is set, any snmpd
response, like response to
snmpget, snmpwalk etc. will have
You can use "clientaddr" in snmp.conf or snmpd.conf,
https://linux.die.net/man/5/snmp.conf
In 5.8 you also have the possibility to use "-s" with trapsess, but I did
not found any documentation on it.
but check the test code, testing/fulltests/default/T184trapsesssource_simple
Regards
Anders Walli
