Hi,
Furthur to my previous email. I use the net-snmp version 5.4.1.2, which use the
agentx other than smux for snmpd to communicate with subagents.
In version 5.2.1 as smux was used, we can define 'smuxpeer OID PASS' in
snmpd.conf, then restriction of traps from a specific subagent (told by
Tayyab Akram wrote:
>
> I personaly think that there is something wrong with my Network Manager
> code as I used WireShark paket sniffer to see the packets which shows,
> *snmpinform* sent 5 INFORMS (retries) Against every INFORM my
> network manager sent response but pakets sniffer shows tha
Hi,
I have a scenario that an enterprise mib acting as a subagent. When some
events happen, the subagent will send traps to snmpd via agentx. I was
wondering if there is a directive to be defined in the snmpd.conf that it will
allow/restrict the trap from this specific subagent to be sent out
Hi Jan,
I checked the patch for 'v1trapaddress', it used the following to register the
v1trapaddress string in the snmpd.conf:
netsnmp_ds_register_config(ASN_OCTET_STR, app, "v1trapaddress",
NETSNMP_DS_APPLICATION_ID,
NETSNMP_D
Hi,
I had a coredump when I run net-snmp 5.3.1. It seems the leakage was observed
when traps are sent.
Doesanyoneknow about this issue and any possible patch has been done tofix
this?It seems the problem also happens in net-snmp 5.4.1.
My coredump is as the following:
===
Hi all,
I need some help, I am developing OAM&P solution and using Net-Snmp for
Agents and Snmp4j for Network Manager.
I have implemented trap receiver using Snmp4j and now I am sending SnmpV3
INFORM using net-snmp tool "*snmpinform*"
[EMAIL PROTECTED] *snmpinform -v 3 -u wes localhost ''
SNMPv2-