Re: UPDATE: Starting snmpd deliver 128 duplicate notifications to each trap2sink destinations

Hello Bill,
Thank you for your post.

Well, I tried some configurations in my snmpd.conf, disabling ipv6, listen in only one interface, etc.
but never tried trapsess, i.e. I already used trap2sink as ou can see in debug dump I posted.

Do you have tried to use snmptrap to see how much duplicates your get in your network?

An interesting fact is that if I enable IPV6 I get 128 duplicates without IPV6 I get 64…
Because of this I said that something is really wrong with the NET-SNMP network code and how
its interpreting the network characteristics where is running.
Also with IPV6 enabled I waas unable to use agentaddress clause, with the 5.7.3 just a message saing that the end point couldnt
be used, with 5.8.dev. the message says that the end point couldn’t be used because the address (anyone) is in use, what is
not true.

I also disabled IPV6 in my host where snmpd is running … no difference. 5.7.3 and 5.8 here
behaves exactly same duplicating packets.


And no others directives, my snmpd.conf is really simple.
Here is my snmpd.conf:

trap2sink	            192.168.0.100	xyz
trap2sink	            192.168.0.205	xyz

com2sec readonly  default   abc
com2sec readwrite default   def

rocommunity                 abc
rwcommunity                 def

master                          agentx


agentaddress                udp:192.168.0.221:161
agentXSocket                /var/agentx/master
agentxperms                 0660 0550 root root
agentxRetries               1
agentxTimeout              3

dontLogTCPWrappersConnects  yes

agentuser                   root
agentgroup                  root



On Thu, Dec 28, 2017 at 2:02 PM, Jose Roberto Fernandez Anahia <
jrfndes@...> wrote:

> Something really .. really wrong with the network code on NET-SNMP.
>

You don't say much about *exactly* what's in your snmpd.conf, but I tried
this:

agentaddress udp:161,tcp:161,udp6:161,tcp6:161
trapsess -v 2c -c sekrit udp:172.25.24.236:162

and I got exactly one packet:

12:26:15.577079 44:4c:a8:64:2b:df > be:7e:8c:45:ca:7e, ethertype IPv4
(0x0800), length 138: (tos 0x0, ttl 59, id 43952, offset 0, flags [DF],
proto UDP (17), length 124)
    172.30.188.156.57296 > 172.25.24.236.snmptrap:  { SNMPv2c C="sekrit" {
V2Trap(81) R=456329610  .1.3.6.1.2.1.1.3.0=1869016
.1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.8072.4.0.3
.1.3.6.1.6.3.1.1.4.3.0=.1.3.6.1.4.1.8072.4 } }

This is using net-snmp 5.8.

  Bill

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users