Created attachment 705000 [details] tarball of a localhost test configuration Description of problem: If an SNMP trap or inform target is configured with a transport other than UDP (the easiest case to test is with plain TCP), then if snmpd is started while the target is running the target will correctly recieve the "coldStart" notification and an entry will be added to the "snmpTargetAddrTable" table with the proper address. If the target is then stopped (thus closing the original socket connection), the "snmpTargetAddrTable" will have a corrupted "snmpTargetAddrTAddress" value and no further notification will be sent to that target. This effectively makes SNMP notification useless if not using UDP transport, since there is no control over when a target will be up, is restarted, etc. Version-Release number of selected component (if applicable): net-snmp 5.7.1-5.fc17.1 How reproducible: Consistently; I have a tarball of test config files if necessary. Steps to Reproduce: 1. Start snmptrapd on local system with minimal test config. 2. Start snmpd on local system with minimal test config. 3. Observe that snmptrapd reports the coldStart message. 4. Run snmptable to get the snmpTargetAddrTable and observe the correct address. 5. Stop snmptrapd. 6. Run snmptable again and observe that the address is now different (and wrong). 7. Restart snmptrapd and trigger another notification via agentxtrap. 8. Observe that snmptrapd never receives the message. Actual results: When using non-UDP transport, snmpd target table becomes corrupted upon a disconnect. Expected results: The target table should not be corrupted by a disconnect. Also, snmpd should attempt to re-establish transports which have been closed. Otherwise, any restart of remote target will stop trap/inform messages from being sent properly. Additional info: attached config files can be used with SNMPCONFPATH environment
Have you tried to contact upstream? This seems to be quite large change in snmpd, which cannot be done as part of Fedora package maintenance.
I agree about the scope of the change, and I have put in a bug report on the Net-SNMP project bug tracker about a similar and related issue (at http://sourceforge.net/p/net-snmp/bugs/2445/) but have not seen any activity on that ticket.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.