Hej, Can you elaborate a bit more on your problem? Provide a TcpDump/wireshark showing the transmitted packets (txt dump + capture file), and the command/binary that you called (with all the arguments).
My guess is that you provided some incorrect arguments as if the IPv6 address would be flawed the socket creation would fail, and the application should terminate with a 'clear' error notification. BR/Patrik Den tis 23 nov. 2021 kl 20:09 skrev Anuj Kumar Goyal < goyal.anujku...@gmail.com>: > Hi, > > I'm seeing an issue where netsnmp 5.9.1 seems to be adding 161 with > destination ipv6. Because of this Ipv6 address becomes invalid and the > packet doesn't reach the client. > This issue doesn't come with netsnmp 5.7.2. > > Can someone help me with this. > > Regards, > Anuj > _______________________________________________ > Net-snmp-users mailing list > Net-snmp-users@lists.sourceforge.net > Please see the following page to unsubscribe or change other options: > https://lists.sourceforge.net/lists/listinfo/net-snmp-users >
_______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
