Nagios Support Forum

Did you also try what Sean suggested? The replies came in kinda close so you might not have seen his.

Yes. I edited /etc/sysconfig/snmptrapd since its sourced after OPTIONS is defined. I had to add udp:162 because leaving it out made it not process anything. Still no IPv6 traps.

OPTIONS="-Lsd udp:162,udp6:[::1]162 -p /var/run/snmptrapd.pid"
OPTIONS="-Lsd udp:162,udp6:[::]:162 -p /var/run/snmptrapd.pid"
OPTIONS="-Lsd udp:162,udp6:162 -p /var/run/snmptrapd.pid"

I'm starting to think IPv6 isn't in the binary, and I'll need to compile a new one... I guess not many use Nagios and IPv6 since it seems so little is known.

Regarding your earlier post about looking for info elsewhere, I've subscribed to the net-snmp mailing list, but my mail is waiting on a blessing from a moderator. I've also been searching the internet for info.

gormank wrote:I'm starting to think IPv6 isn't in the binary, and I'll need to compile a new one...

I'm hoping this isn't the case, but it's kinda looking that way.

gormank wrote:Regarding your earlier post about looking for info elsewhere, I've subscribed to the net-snmp mailing list, but my mail is waiting on a blessing from a moderator.

I think that even though this might take a few days, they're going to have a much better idea of what's going on. We've strayed somewhat out of Nagios land at this point, so it's not something we're necessarily going to have documented or even have seen before.

I built a new set of binaries, but didn't install them (so as not to break my system). I stop snmptapd and run the new one manually.

./snmptrapd -Lsd udp:162,udp6:162 -p /var/run/snmptrapd.pid

Its not very happy (can't find modules), but it runs. If I send a trap on IPv4, it logs it. If I send a trap on IPv6, nothing.

Just for grins, here's my question to the net-snmp folks...

https://sourceforge.net/p/net-snmp/mail ... nth=201604

As far as straying out of Nagiosland, my guess is that as time goes on, the Nagios community will need to support SNMP traps over IPv6 regardless of the fact that the trouble is an issue with net-snmp, and not with Nagios.

My guess is that this is an issue with my not getting the syntax right. I've also tried udpv6 and udpipv6 in place of udp6, as well as the -x arg, -n, etc.

Can anyone say that they're processing traps from IPv6, or better both v4 and v6?

gormank wrote:As far as straying out of Nagiosland, my guess is that as time goes on, the Nagios community will need to support SNMP traps over IPv6 regardless of the fact that the trouble is an issue with net-snmp, and not with Nagios.

This is a tricky point to address. Make no doubt, we definitely tend to stray on the side of "We'll help you even though this is not really a Nagios question anymore" but that's the exception, not the rule. If we have a quick answer, or we know roughly where the answer will lie, it doesn't take much effort at all for us to give an answer. But in some cases, like this one, the answer is not something we have readily available, and/or troubleshooting will take a significant amount of time. If it were clearly a Nagios issue then it would not be a problem, we'd have the knowledge and experience to pinpoint the issue, but with net-snmp that's not the case. We're just not the experts in that field, but if we were I can't imagine we would hold back answers simply because it was out of scope.

That having been said, we can absolutely keep this open to address your last point:

gormank wrote:Can anyone say that they're processing traps from IPv6, or better both v4 and v6?

However being in the Customer forum is going to somewhat limit the community responses you are able to receive - would you like me to move this to General for more exposure?

Sure.

I've moved the thread out from Customer to General, and will leave this open for community comment.

It looks like we got the syntax right a while back and its listening, but not processing the traps...

# ps -ef | grep snmptrapd | grep -v grep
root 14576 1 0 20:35 ? 00:00:00 /usr/sbin/snmptrapd -a -A -Lf /var/log/snmtrapd.log -On -p /var/run/snmptrapd.pid udp:162,udp6:[::1]:162

# netstat -an | grep ":162 "
udp 0 0 0.0.0.0:162 0.0.0.0:*
udp 0 0 ::1:162 :::*

# tcpdump -i eth3 -s 0 port 162
tcpdump: WARNING: eth3: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth3, link-type EN10MB (Ethernet), capture size 65535 bytes

20:54:19.444292 IP6 2001:4888:a03:311f:c0:a:0:190.32861 > txslm2mlnag001v6.snmptrap: C=sp1der Trap(167) E:232 0.0.0.0 enterpriseSpecific s=11003 78131151 system.sysName.0="TXSLM2MCHP7004-OA" E:232.11.2.11.1=1 E:232.11.2.8.1="HP Onboard Administrator Test Trap sent from enclosure: TXSLM2MCHP7004"

# cat /var/log/snmtrapd.log
NET-SNMP version 5.5

Have you checked the snmptt log files in /var/log/snmptt to see if there are any errors or if that trap was unknown?