Bug 1190679
| Summary: | In IPv6, snmp packet does not send from specified interface assigned by clientaddr option in snmpd.conf. | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Keigo Noha <knoha> | |
| Component: | net-snmp | Assignee: | Jan Safranek <jsafrane> | |
| Status: | CLOSED ERRATA | QA Contact: | Dalibor Pospíšil <dapospis> | |
| Severity: | low | Docs Contact: | Mark Flitter <mflitter> | |
| Priority: | medium | |||
| Version: | 7.0 | CC: | btotty, dapospis, jsafrane | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
SNMP now correctly obeys the clientaddr directive over IPv6
Previously, the *clientaddr* option in `snmp.conf` only affected outgoing messages sent over IPv4. With this release, the outgoing IPv6 messages are correctly sent from the interface specified by *clientaddr*.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1279501 (view as bug list) | Environment: | ||
| Last Closed: | 2015-11-19 11:45:49 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1205796, 1279501 | |||
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. https://rhn.redhat.com/errata/RHSA-2015-2345.html |
Description of problem: In IPv6, snmp trap packet does not send from specified interface assigned by clientaddr option in snmpd.conf. Version-Release number of selected component (if applicable): net-snmp-5.7.2-18.el7 How reproducible: Always. Steps to Reproduce: 1. Prepare two nics for the server. 2. Assign IPv6 address to two NICs. e.x. ~~~ 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:e1:9e:6c brd ff:ff:ff:ff:ff:ff inet6 2001:db4::101/64 scope global valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:9e6c/64 scope link valid_lft forever preferred_lft forever 3: ens7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:61:3e:3e brd ff:ff:ff:ff:ff:ff inet6 2001:db4::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe61:3e3e/64 scope link valid_lft forever preferred_lft forever ~~~ 3. Assigned clientaddr to ens3 - /etc/snmp/snmpd.conf ~~~ clientaddr 2001:db4::101 ~~~ 4. Send snmp trap to another server. 5. Check source address in the packet. Actual results: The source address is not the assigned address. Expected results: The source address is the assigned address in clientaddr option. Additional info: This bug is reported from NEC. And upstream has a fix for this issue. http://sourceforge.net/p/net-snmp/bugs/2584/