Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 840861 - snmpd does not report error when clientaddr <ip>:<port> cannot bind to the specified port
snmpd does not report error when clientaddr <ip>:<port> cannot bind to the sp...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: net-snmp (Show other bugs)
5.9
Unspecified Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Jan Safranek
Dalibor Pospíšil
:
Depends On:
Blocks: 886468 1086925
  Show dependency treegraph
 
Reported: 2012-07-17 08:19 EDT by Jan Safranek
Modified: 2014-04-11 16:31 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
This is regression found in internal build, it has not been released. No documentation needed.
Story Points: ---
Clone Of:
: 886468 (view as bug list)
Environment:
Last Closed: 2013-01-08 00:03:24 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0124 normal SHIPPED_LIVE Moderate: net-snmp security and bug fix update 2013-01-08 04:22:53 EST

  None (edit)
Description Jan Safranek 2012-07-17 08:19:47 EDT
Description of problem:
Having following /etc/snmp/snmpd.conf file, if snmpd fails to bind the specified clientaddr port, it quietly uses random port instead. It should at least report some error to system log.

rocommunity public
[snmp] clientaddr 127.0.0.1:30000
trapsink localhost public

Version-Release number of selected component (if applicable):
net-snmp-5.3.2.2-18

How reproducible:
always

Steps to Reproduce:
1. vi /etc/snmp/snmpd.conf
2. nc -ul localhost 30000 (or have SELinux in enforcing mode)
3. service snmpd start
  
Actual results:
- traps are sent from random port and not from port 30000, which is taken by 'nc'
- system log is empty

Expected results:
- system log should show an error
Comment 1 Jan Safranek 2012-07-17 08:21:16 EDT
Look at upstream's snmplib/transports/snmpUDPIPv4BaseDomain.c:190

    /* Retry with port = 0 */
    client_addr.sin_port = 0;
Comment 2 Jan Safranek 2012-08-07 04:03:49 EDT
This bug is in the same code as regression #845974, it makes sense to fix them together.
Comment 3 RHEL Product and Program Management 2012-08-07 04:09:06 EDT
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Comment 4 Jan Safranek 2012-08-07 04:10:27 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
This is regression found in internal build, it has not been released. No documentation needed.
Comment 11 errata-xmlrpc 2013-01-08 00:03:24 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0124.html

Note You need to log in before you can comment on or make changes to this bug.