You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(315) |
Dec
(298) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(254) |
Feb
(467) |
Mar
(430) |
Apr
(345) |
May
(406) |
Jun
(336) |
Jul
(313) |
Aug
(265) |
Sep
(433) |
Oct
(462) |
Nov
(387) |
Dec
(232) |
2002 |
Jan
(352) |
Feb
(556) |
Mar
(463) |
Apr
(500) |
May
(557) |
Jun
(337) |
Jul
(317) |
Aug
(279) |
Sep
(273) |
Oct
(354) |
Nov
(267) |
Dec
(347) |
2003 |
Jan
(351) |
Feb
(445) |
Mar
(520) |
Apr
(665) |
May
(499) |
Jun
(393) |
Jul
(304) |
Aug
(425) |
Sep
(262) |
Oct
(329) |
Nov
(220) |
Dec
(174) |
2004 |
Jan
(365) |
Feb
(479) |
Mar
(515) |
Apr
(522) |
May
(214) |
Jun
(471) |
Jul
(292) |
Aug
(341) |
Sep
(243) |
Oct
(446) |
Nov
(294) |
Dec
(147) |
2005 |
Jan
(171) |
Feb
(209) |
Mar
(218) |
Apr
(321) |
May
(233) |
Jun
(534) |
Jul
(268) |
Aug
(345) |
Sep
(498) |
Oct
(557) |
Nov
(459) |
Dec
(238) |
2006 |
Jan
(288) |
Feb
(180) |
Mar
(151) |
Apr
(113) |
May
(164) |
Jun
(277) |
Jul
(160) |
Aug
(383) |
Sep
(221) |
Oct
(404) |
Nov
(358) |
Dec
(163) |
2007 |
Jan
(293) |
Feb
(175) |
Mar
(202) |
Apr
(155) |
May
(427) |
Jun
(484) |
Jul
(414) |
Aug
(125) |
Sep
(131) |
Oct
(160) |
Nov
(79) |
Dec
(70) |
2008 |
Jan
(133) |
Feb
(115) |
Mar
(158) |
Apr
(194) |
May
(197) |
Jun
(230) |
Jul
(146) |
Aug
(68) |
Sep
(93) |
Oct
(53) |
Nov
(95) |
Dec
(69) |
2009 |
Jan
(81) |
Feb
(162) |
Mar
(215) |
Apr
(216) |
May
(78) |
Jun
(131) |
Jul
(61) |
Aug
(176) |
Sep
(127) |
Oct
(28) |
Nov
(83) |
Dec
(94) |
2010 |
Jan
(100) |
Feb
(187) |
Mar
(320) |
Apr
(161) |
May
(194) |
Jun
(142) |
Jul
(129) |
Aug
(139) |
Sep
(239) |
Oct
(202) |
Nov
(139) |
Dec
(196) |
2011 |
Jan
(195) |
Feb
(191) |
Mar
(201) |
Apr
(127) |
May
(84) |
Jun
(126) |
Jul
(101) |
Aug
(237) |
Sep
(123) |
Oct
(104) |
Nov
(197) |
Dec
(114) |
2012 |
Jan
(65) |
Feb
(85) |
Mar
(129) |
Apr
(84) |
May
(94) |
Jun
(83) |
Jul
(89) |
Aug
(85) |
Sep
(89) |
Oct
(73) |
Nov
(34) |
Dec
(38) |
2013 |
Jan
(89) |
Feb
(30) |
Mar
(25) |
Apr
(18) |
May
(20) |
Jun
(45) |
Jul
(74) |
Aug
(37) |
Sep
(72) |
Oct
(30) |
Nov
(67) |
Dec
(24) |
2014 |
Jan
(23) |
Feb
(16) |
Mar
(40) |
Apr
(37) |
May
(12) |
Jun
(18) |
Jul
(30) |
Aug
(26) |
Sep
(24) |
Oct
(32) |
Nov
(15) |
Dec
(33) |
2015 |
Jan
(15) |
Feb
(45) |
Mar
(21) |
Apr
(24) |
May
(22) |
Jun
(7) |
Jul
(57) |
Aug
(17) |
Sep
(16) |
Oct
(3) |
Nov
(8) |
Dec
(13) |
2016 |
Jan
(7) |
Feb
(14) |
Mar
(40) |
Apr
(8) |
May
(10) |
Jun
(6) |
Jul
(8) |
Aug
(10) |
Sep
(19) |
Oct
(20) |
Nov
(45) |
Dec
(10) |
2017 |
Jan
(10) |
Feb
(12) |
Mar
(3) |
Apr
(17) |
May
(41) |
Jun
(21) |
Jul
(13) |
Aug
(13) |
Sep
(7) |
Oct
(23) |
Nov
(10) |
Dec
(23) |
2018 |
Jan
(45) |
Feb
(3) |
Mar
(57) |
Apr
(107) |
May
(173) |
Jun
(47) |
Jul
(28) |
Aug
(26) |
Sep
(38) |
Oct
(56) |
Nov
(22) |
Dec
(11) |
2019 |
Jan
(37) |
Feb
(8) |
Mar
(7) |
Apr
(29) |
May
(32) |
Jun
(5) |
Jul
(21) |
Aug
(31) |
Sep
(38) |
Oct
(8) |
Nov
(13) |
Dec
(10) |
2020 |
Jan
(9) |
Feb
(33) |
Mar
(14) |
Apr
(4) |
May
(16) |
Jun
(11) |
Jul
(14) |
Aug
(50) |
Sep
(24) |
Oct
(3) |
Nov
(14) |
Dec
(13) |
2021 |
Jan
(18) |
Feb
(15) |
Mar
(12) |
Apr
(9) |
May
(9) |
Jun
(8) |
Jul
(6) |
Aug
(7) |
Sep
(26) |
Oct
(17) |
Nov
(6) |
Dec
(2) |
2022 |
Jan
(3) |
Feb
(11) |
Mar
(7) |
Apr
(15) |
May
(5) |
Jun
(4) |
Jul
(29) |
Aug
(6) |
Sep
(7) |
Oct
|
Nov
(4) |
Dec
(1) |
2023 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(3) |
Jun
(5) |
Jul
(3) |
Aug
(10) |
Sep
(10) |
Oct
(7) |
Nov
(2) |
Dec
(4) |
2024 |
Jan
(22) |
Feb
(5) |
Mar
(11) |
Apr
(20) |
May
(16) |
Jun
(9) |
Jul
(14) |
Aug
(5) |
Sep
(7) |
Oct
(4) |
Nov
(3) |
Dec
|
2025 |
Jan
(6) |
Feb
(6) |
Mar
(14) |
Apr
(2) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Roberto A. F. <rob...@gm...> - 2021-07-21 12:48:26
|
Il giorno mer 21 lug 2021 alle ore 09:46 Roberto A. Foglietta < rob...@gm...> ha scritto: > Dear all, > > I found this suggestion about the issue in the object and I applied it in > a newer version but it did not work. Could you help me to address > this issue, please? > > https://sourceforge.net/p/net-snmp/mailman/message/16888540/ > It works, thank you, -R |
From: Roberto A. F. <rob...@gm...> - 2021-07-21 07:47:01
|
Dear all, I found this suggestion about the issue in the object and I applied it in a newer version but it did not work. Could you help me to address this issue, please? https://sourceforge.net/p/net-snmp/mailman/message/16888540/ AP> Is it possible for net-snmp to exec the script on each AP> snmpget request ? RMHH> If somebody knows a workaround/fix for this I'd be also RMHH>interested. The workaround is to edit the file include/net-snmp/net-snmp-config.h remove the definition of EXCACHETIME, and re-compile the agent. Thank you, -- Roberto A. Foglietta +39.349.33.30.697 |
From: Wes H. <har...@us...> - 2021-07-20 22:47:01
|
"Srilatha Devineni (sdevinen) via Net-snmp-coders" <net...@li...> writes: > I installed 5.9.1 net-snmp and I see there is no support for AES AES requires OpenSSL to be installed when Net-SNMP is compiled. Use the --with-openssl flag to point to the path where it is installed if it couldn't find it in a default location. -- Wes Hardaker Please mail all replies to net...@li... |
From: Craig S. <cs...@dr...> - 2021-07-19 12:43:49
|
On Mon, 19 Jul 2021, 20:28 Roberto A. Foglietta, < rob...@gm...> wrote: > I have been reported that the bottleneck is due to the single-thread > nature of SNMP. > The bottleneck is about 1 SNMP call served per second. > That sounds like asynchronous SNMP calls. The delay is due to the response time across the network. Do you anyone considered to have a multi-thread SNMP server? Just in case, > which kind of issues will be faced and how much effort it could require > such a porting? > So the answer is yes you could multi thread a bunch of synchronous SNMP senders. This is a terrible idea. If you use an asynchronous caller then the delay is basically how long it takes to create the PDU and punt it to the kernel socket before the next one can be started. This is Quite Fast. Not fast enough? Check your reply code, maybe whatever you are doing when you get the reply is taking the time. I didn't like how long RRD files took to update so I put that part into its own thread to make sure the reply side of the SNMP code was nice and fast with a simple IPC to a rrd update thread. If that is not fast enough then you can multi thread the Async code. I'm pretty sure you won't need this. BTW when you get to silly output levels you need to be careful not to smash the SNMP agent on the remote end. Most network equipment on the control plane uses bad CPUs and worse SNMP code (or the data handler) so your now mega fast SNMP query engine can overwhelm things or even crash them. Asynchronous code is tricky to write but it is possible. It's a matter of explicitly remembering what you have sent and what you will sent. Synchronous code is easy because your for loop is the "will sent" part and the single outgoing call is the "have sent" part. - Craig |
From: Roberto A. F. <rob...@gm...> - 2021-07-19 10:28:12
|
Hi All, I am experiencing a bottleneck in managing the SNMP calls when they have a flow peak. I have been reported that the bottleneck is due to the single-thread nature of SNMP. The bottleneck is about 1 SNMP call served per second. Do you anyone considered to have a multi-thread SNMP server? Just in case, which kind of issues will be faced and how much effort it could require such a porting? Thank you, -- Roberto A. Foglietta +39.349.33.30.697 |
From: Srilatha D. (sdevinen) <sde...@ci...> - 2021-07-09 06:37:26
|
Hi Developers, I installed 5.9.1 net-snmp and I see there is no support for AES I wonder , why the latest version doesn’tt have support for AES I don’t think that I missed any config. SDEVINEN-M-V0LX:net-snmp-5.9.1 sdevinen$ snmpwalk -v3 -l authPriv -u authPriv-sha-aes -a SHA -A PASSWORD1 -x AES -X PASSWORD1 10.195.235.6 1.3.6.1.2.1.47 Invalid privacy protocol specified after -3x flag: AES USAGE: snmpwalk [OPTIONS] AGENT [OID] Version: 5.9.1 Web: http://www.net-snmp.org/ Email: net...@li... OPTIONS: -h, --help display this help message -H display configuration file directives understood -v 1|2c|3 specifies SNMP version to use -V, --version display package version number SNMP Version 1 or 2c specific -c COMMUNITY set the community string SNMP Version 3 specific -a PROTOCOL set authentication protocol (MD5|SHA|SHA-224|SHA-256|SHA-384|SHA-512) -A PASSPHRASE set authentication protocol pass phrase -e ENGINE-ID set security engine ID (e.g. 800000020109840301) -E ENGINE-ID set context engine ID (e.g. 800000020109840301) -l LEVEL set security level (noAuthNoPriv|authNoPriv|authPriv) -n CONTEXT set context name (e.g. bridge1) -u USER-NAME set security name (e.g. bert) -x PROTOCOL set privacy protocol (DES) -X PASSPHRASE set privacy protocol pass phrase -Z BOOTS,TIME set destination engine boots/time Regards, Srilatha |
From: Code K. <cod...@gm...> - 2021-06-29 05:55:12
|
Hi Larry, Thanks for the reply. I'm able to create users using the snmpusm command but can only use them after adding their details to the config file. Our config file is generated at runtime by an application which will add an access line for each user that it can read from the persistent storage. But to trigger this application we must stop and start snmp via our GUI, replicating the behaviour described in the 'CREATING A SECOND USER' section in https://net-snmp.sourceforge.io/docs/README.snmpv3.html. My aim is to automate this if possible. So when for example a new user is created, we somehow detect this and restart our application which will stop Net-SNMP, create the user access controls lines and then restart Net-SNMP. Another thing that I'm wondering if it is possible is to have a more generic setup in the configuration to setup the access control, however I'm not sure if I can make use of authgroup without using authuser. Thanks again for your help, CK On Thu, 24 Jun 2021 at 18:05, Larry Hayes <lh...@gm...> wrote: > > I am more of a user of the net-snmp library so take what I say with skepticism. > > The snmpusm should be updating the usmUserTableby sending messages to the snmpd to do the work. > You can query this table to verify that the users are created in it. > Once in this table, I would suspect that these users are available for use and no restart of the snmpd is needed. > > When the snmpd is stopped it will update the persistent snmpd.conf file with the users from the usmUserTable. > The purpose of doing this is so on the next startup it can recreate the usmUserTable. > > I would find it very interesting if the snmpd needs to restart to start using V3 users created via snmpusm. > > What type of failure are you encountering? > Have you set up the user's access control? > > Access control can be done in the non-persistent snmpd.conf files and usually a SIGHUP will do the trick to get snmpd to reread these files. > > > On Thu, Jun 24, 2021 at 2:19 AM Code Kipper <cod...@gm...> wrote: >> >> Hi all, >> >> We have an application which generates the common configuration file >> for snmpd based on user settings and manages the snmpd and snmptrapd >> services. >> >> Currently, we're able to clone and manage v3 users via snmpusm but to >> use them we must shutdown snmpd so that the persistent snmpd.conf file >> is updated and then restart our application. This regenerates the >> common configuration file with the correct access control and starts >> snmpd. >> >> Our aim is to make this seamless but I'm not sure if this is possible. >> If, for example, if the snmpd.conf file was updated as soon as these >> table settings were modified then we could monitor that and then >> restart everything. I've skimmed the library functions but don't see >> anything that could provide notifications based on user changes. >> >> Is what I'm trying to do possible?, >> >> Thanks in advance, >> CK >> >> >> _______________________________________________ >> Net-snmp-coders mailing list >> Net...@li... >> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders |
From: Larry H. <lh...@gm...> - 2021-06-24 16:05:17
|
I am more of a user of the net-snmp library so take what I say with skepticism. The snmpusm should be updating the usmUserTableby sending messages to the snmpd to do the work. You can query this table to verify that the users are created in it. Once in this table, I would suspect that these users are available for use and no restart of the snmpd is needed. When the snmpd is stopped it will update the persistent snmpd.conf file with the users from the usmUserTable. The purpose of doing this is so on the next startup it can recreate the usmUserTable. I would find it very interesting if the snmpd needs to restart to start using V3 users created via snmpusm. What type of failure are you encountering? Have you set up the user's access control? Access control can be done in the non-persistent snmpd.conf files and usually a SIGHUP will do the trick to get snmpd to reread these files. On Thu, Jun 24, 2021 at 2:19 AM Code Kipper <cod...@gm...> wrote: > Hi all, > > We have an application which generates the common configuration file > for snmpd based on user settings and manages the snmpd and snmptrapd > services. > > Currently, we're able to clone and manage v3 users via snmpusm but to > use them we must shutdown snmpd so that the persistent snmpd.conf file > is updated and then restart our application. This regenerates the > common configuration file with the correct access control and starts > snmpd. > > Our aim is to make this seamless but I'm not sure if this is possible. > If, for example, if the snmpd.conf file was updated as soon as these > table settings were modified then we could monitor that and then > restart everything. I've skimmed the library functions but don't see > anything that could provide notifications based on user changes. > > Is what I'm trying to do possible?, > > Thanks in advance, > CK > > > _______________________________________________ > Net-snmp-coders mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders > |
From: Code K. <cod...@gm...> - 2021-06-24 07:18:34
|
Hi all, We have an application which generates the common configuration file for snmpd based on user settings and manages the snmpd and snmptrapd services. Currently, we're able to clone and manage v3 users via snmpusm but to use them we must shutdown snmpd so that the persistent snmpd.conf file is updated and then restart our application. This regenerates the common configuration file with the correct access control and starts snmpd. Our aim is to make this seamless but I'm not sure if this is possible. If, for example, if the snmpd.conf file was updated as soon as these table settings were modified then we could monitor that and then restart everything. I've skimmed the library functions but don't see anything that could provide notifications based on user changes. Is what I'm trying to do possible?, Thanks in advance, CK |
From: Romain B. <Rom...@ha...> - 2021-06-21 08:13:53
|
Dear all, I don't know if I should contact you this way but I have a question about a problem. When I create a userl3 for example, I have the line rwuser testl3 in my snmpd.conf as well as usmUser 1 3 0x80001f8803bcc23a007fe4 "testl3" NULL . 1.3.6.1.6.3.10.1.1.2 0xb1ccc82374fba0f25dc2dcca2eadc5ad .1.3.6.1.6.3.10.1.2.2 0xb1ccc82374fba0f25dc2dcca2eadc5ad 0x When I want to clone this user (using the following command : ./snmpusm -v3 -l authPriv -u testl3 -a MD5 -A unephrase -x DES -X unephrase 198.18.104.143 create usercloned testl3) I get the following error: Error in packet. Reason: notWritable (That object does not support modification) Failed object: iso.3.6.1.6.3.15.1.2.2.1.13.11.128.0.31.136.3.188.194.58.0.127.228.10.117.115.101.114.99.108.111.110.101.100 I have two questions: when creating a user the usmUserTable is supposed to be filled? In my case it looks empty. Do you have a solution to correct this problem? Is there a problem if I have changed the path of my snmpd.conf ? Thanks in advance, Naguraa |
From: Wes H. <har...@us...> - 2021-06-18 21:14:24
|
"Weiland, Nicholas" <nwe...@id...> writes: > libnetsnmpmibs.so.35 and libnetsnmptrapd.so.35 still have links to libcrypto.so.1.1 > (but not libssl.so.1.1). I would like to know if there are any configuration flags I > missed that would fix this for us, or if there is any manual hack that would get > around the issue. This was not an issue in older versions of snmp libraries (namely > we’ve used snmp 5.5). We do not use libnetsnmpmibs or libnetsnmptrapd. If there is a > way to exclude them from being built that would also solve the issue. Is there a chance that you have them from an older build? IE, can you try building it from a fresh source extraction? -- Wes Hardaker Please mail all replies to net...@li... |
From: Larry H. <lh...@gm...> - 2021-06-14 16:35:23
|
Not sure how to get rid of the libnetsnmpmibs.so, But you might try the configure option: '--disable-applications' to get rid of the libsnmptrapd.so >From configure help: --disable-applications Do not build the apps (snmpget, ...). On Sun, Jun 13, 2021 at 10:13 AM Weiland, Nicholas <nwe...@id...> wrote: > Hello, > > > > We would like to compile the net snmp 5.8 libs ( > https://sourceforge.net/projects/net-snmp/files/net-snmp/5.8/net-snmp-5.8.tar.gz/download) > without any crypto/ssl support whatsoever. Currently I have tried the > following configure options: > > '--disable-embedded-perl', > > '--without-perl-modules', > > '--with-persistent-directory=/tmp/snmp-persistence', > > '--with-logfile=/var/log/snmp.log', > > '--with-default-snmp-version=3', > > '--without-openssl', > > '--disable-md5', > > '--disable-privacy', > > '--disable-des' > > > > The –without-openssl flag gets the build to the point where most of the > libcrypto.so.1.1 and libssl.so.1.1 links are gone. The ones below it don’t > seem to do anything effecting link libs. > > > > Of the following libraries -- > > libnetsnmpagent.so.35 > > libnetsnmphelpers.so.35 > > libnetsnmpmibs.so.35 > > libnetsnmp.so.35 > > libnetsnmptrapd.so.35 > > > > libnetsnmpmibs.so.35 and libnetsnmptrapd.so.35 still have links to > libcrypto.so.1.1 (but not libssl.so.1.1). I would like to know if there are > any configuration flags I missed that would fix this for us, or if there is > any manual hack that would get around the issue. This was not an issue in > older versions of snmp libraries (namely we’ve used snmp 5.5). We do not > use libnetsnmpmibs or libnetsnmptrapd. If there is a way to exclude them > from being built that would also solve the issue. > > > > Thank you, > > > > Nicholas Weiland > ------------------------------ > > This electronic message and any files transmitted with it contains > information from iDirect Government, LLC, which may be privileged, > proprietary and/or confidential. It is intended solely for the use of the > individual or entity to whom they are addressed. If you are not the > original recipient or the person responsible for delivering the email to > the intended recipient, be advised that you have received this email in > error, and that any use, dissemination, forwarding, printing, or copying of > this email is strictly prohibited. If you received this email in error, > please delete it and immediately notify the sender. > _______________________________________________ > Net-snmp-coders mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders > |
From: Weiland, N. <nwe...@id...> - 2021-06-11 15:13:34
|
Hello, We would like to compile the net snmp 5.8 libs (https://sourceforge.net/projects/net-snmp/files/net-snmp/5.8/net-snmp-5.8.tar.gz/download) without any crypto/ssl support whatsoever. Currently I have tried the following configure options: '--disable-embedded-perl', '--without-perl-modules', '--with-persistent-directory=/tmp/snmp-persistence', '--with-logfile=/var/log/snmp.log', '--with-default-snmp-version=3', '--without-openssl', '--disable-md5', '--disable-privacy', '--disable-des' The -without-openssl flag gets the build to the point where most of the libcrypto.so.1.1 and libssl.so.1.1 links are gone. The ones below it don't seem to do anything effecting link libs. Of the following libraries -- libnetsnmpagent.so.35 libnetsnmphelpers.so.35 libnetsnmpmibs.so.35 libnetsnmp.so.35 libnetsnmptrapd.so.35 libnetsnmpmibs.so.35 and libnetsnmptrapd.so.35 still have links to libcrypto.so.1.1 (but not libssl.so.1.1). I would like to know if there are any configuration flags I missed that would fix this for us, or if there is any manual hack that would get around the issue. This was not an issue in older versions of snmp libraries (namely we've used snmp 5.5). We do not use libnetsnmpmibs or libnetsnmptrapd. If there is a way to exclude them from being built that would also solve the issue. Thank you, Nicholas Weiland ------ This electronic message and any files transmitted with it contains information from iDirect Government, LLC, which may be privileged, proprietary and/or confidential. It is intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please delete it and immediately notify the sender. |
From: Wes H. <har...@us...> - 2021-06-02 16:20:17
|
Josef Řídký <jr...@re...> writes: > But the more important question is, do we need the IRC channel at all? > I don't think there is much traffic (last usage was about migrating > project to GitHub, if I recall well) and most of the discussion is > held here or at the GitHub issues/PRs. It's certainly been a (very) long time since the IRC channel was fully active. I think it'd be great if one was used, but I agree that we should determine whether or not there is enough interest or not to actually have one. -- Wes Hardaker Please mail all replies to net...@li... |
From: Josef Ř. <jr...@re...> - 2021-05-31 13:31:44
|
Net-SNMP is the last one IRC channel I have active on freenode. All others have migrated to Libera.Chat, so I would vote for switching to Libera as well, but it's entirely up to you. But the more important question is, do we need the IRC channel at all? I don't think there is much traffic (last usage was about migrating project to GitHub, if I recall well) and most of the discussion is held here or at the GitHub issues/PRs. What do you think? Regards Josef Ridky Software Engineer Core Services Team Red Hat Czech, s.r.o. On Thu, May 27, 2021 at 3:46 PM Steve Friedl <st...@un...> wrote: > Are there any thoughts about the #net-snmp channel and Freenode, which > seems to be in quite an upheaval, with larger projects abandoning it for > Libera.Chat, started by the wave of resigning freenode admins. > > Ref: https://lwn.net/Articles/856543/ > > For reasons nobody can remember, I (SJFriedl) am still a channel op on > Freenode's #net-snmp, though I haven't done significant Net SNMP work in > quite some time. > > I have "reserved" the #net-snmp channel on Libera.Chat but none of this is > mine; have the powers that be thought about what to do with IRC? > > I don't have a strong opinion one way or another. > > Steve > > --- > Steve Friedl // Software & Network Security Consultant // 714-345-4571 > st...@un... // Southern California USA // I speak for me only > > > > > > _______________________________________________ > Net-snmp-coders mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders > > |
From: Pavel F. <PFr...@ad...> - 2021-05-30 12:00:57
|
Hi All. We are using the net-snmp ver.5.7.3. We see that "Authentication failure trap" is not sending in case of "Unknown user", but this "Authentication failure trap" is sending in case of "Authentication failure (invalid key)". We used the ucd-snmp for our earlier products, and this "Authentication failure trap" were sent in both cases on the devices that use the ucd-snmp. What is the reason that the "Authentication failure trap" is not sending in case of "Unknown user" (when we use "net-snmp")? Thank you. Best regards, Pavel Fridland ADVA Optical Networking SE E-mail: PFr...@ad...<mailto:Eta...@ad...> <http://www.advaoptical.com/> www.advaoptical.com<http://www.advaoptical.com/> Let’s ADVANCE Please see our privacy statement at https://www.adva.com/en/about-us/legal/privacy-statement for details of how ADVA processes personal information. |
From: Steve F. <st...@un...> - 2021-05-27 14:07:10
|
Are there any thoughts about the #net-snmp channel and Freenode, which seems to be in quite an upheaval, with larger projects abandoning it for Libera.Chat, started by the wave of resigning freenode admins. Ref: https://lwn.net/Articles/856543/ For reasons nobody can remember, I (SJFriedl) am still a channel op on Freenode's #net-snmp, though I haven't done significant Net SNMP work in quite some time. I have "reserved" the #net-snmp channel on Libera.Chat but none of this is mine; have the powers that be thought about what to do with IRC? I don't have a strong opinion one way or another. Steve --- Steve Friedl // Software & Network Security Consultant // 714-345-4571 st...@un... // Southern California USA // I speak for me only |
From: Magnus F. <ma...@ly...> - 2021-05-23 18:08:23
|
On Wed, Apr 28, 2021 at 02:57:39PM +0000, Alex Ordoñez wrote: > Hi friend, do you have mib for VNX 5500 ?, send me please. Or Where do you think I can find it ? I want to monitor disks, cpu, memory, etc. Talk to the vendor that sold the thing to you. /MF > Best regards, > > Alex Ordóñez Vélez > _______________________________________________ > Net-snmp-coders mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders |
From: Wes H. <har...@us...> - 2021-05-14 21:39:27
|
Simone Moni <sim...@gm...> writes: > if ($request_info->getMode() == MODE_GET) { > # ... generally, you would calculate value from oid > if ($oid == new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0")) { > $request->setValue(ASN_OCTET_STR, $default_SP); > } > if ($oid == new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.3.0")) { > $request->setValue(ASN_OCTET_STR, $default_PC); > } If these are your two values, then your GETNEXT code needs to deal with both. But you have both answers in your GETNEXT code in the same spot. You need another if statement for $oid < ... .1.3.0: > } elsif ($request_info->getMode() == MODE_GETNEXT) { > # ... generally, you would calculate value from oid > if ( $oid < new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0")) { > $request->setOID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0"); > $request->setValue(ASN_OCTET_STR, $default_SP); > $request->setOID(".1.3.6.1.4.1.193.37.10.11.64.10.1.3.0"); > $request->setValue(ASN_OCTET_STR, $default_PC); > } You only have one if statement above, eg. > } elsif ($request_info->getMode() == MODE_SET_RESERVE1) { > if ( ( $oid != new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0")) and ( $oid != > new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.3.0")) ) { # do error checking here > $request->setError($request_info, SNMP_ERR_NOSUCHNAME); > } > } elsif ($request_info->getMode() == MODE_SET_ACTION) { > # ... (or use the value) > $value = $request->getValue(); > } You're setting the $value variable but never using it again -- you would need to update the $default_SP or equivelent based on the incoming OID (which you'll need an if statement for each inside the MODE_SET_ACTION check). -- Wes Hardaker Please mail all replies to net...@li... |
From: Simone M. <sim...@gm...> - 2021-05-07 07:44:14
|
Hi, Can anyone help me? I'm a newbie with AgentX. I need to extend snmpd with a new custom MIB module. I have NET-SNMP version 5.5 on Redhat, I would implement perl API, using NetSNMP::agent. Hereby, the steps I've done: - /etc/snmp/snmpd.conf #sec.name source community com2sec notConfigUser default public #groupName securityModel securityName group notConfigGroup v1 notConfigUser group notConfigGroup v2c notConfigUser #name incl/excl subtree mask(optional) view all included .1 #group context sec.model sec.level prefix read write notif access notConfigGroup "" any noauth exact all all none master agentx - MIB module My custom MIB is related to an active alarms table for fault management. It must be queryable from an external management station. The MIB file (ACM-LOGWATCH-MIB) is located in /usr/share/snmp/mibs directory. Here the subset for Table: acmLogWatchTable OBJECT-TYPE SYNTAX SEQUENCE OF acmLogWatchEntry MAX-ACCESS read-only STATUS current DESCRIPTION "Table of objects" ::= { acmLogWatch 10 } acmLogWatchEntry OBJECT-TYPE SYNTAX acmLogWatchEntry MAX-ACCESS read-only STATUS current DESCRIPTION "" INDEX { acmLogWatchIndex } ::= { acmLogWatchTable 1 } acmLogWatchEntry ::= SEQUENCE { acmLogWatchIndex Integer32, acmLogWatchSpecificProblem DisplayString, acmLogWatchProbableCause DisplayString, } acmLogWatchIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "A unique value for each active alarm" ::= { acmLogWatchEntry 1 } acmLogWatchSpecificProblem OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-write STATUS current DESCRIPTION "the specific problem of the alarm" ::= { acmLogWatchEntry 2 } acmLogWatchProbableCause OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-write STATUS current DESCRIPTION "the probable cause of the alarm" ::= { acmLogWatchEntry 3 } snmpset is used to set OID's Values. - perl code: use NetSNMP::agent (':all'); use NetSNMP::ASN (':all'); use NetSNMP::OID(':all'); my $default_SP = "SP 1"; my $default_PC = "PC 1"; sub myhandler { my ($handler, $registration_info, $request_info, $requests) = @_; my $request; for($request = $requests; $request; $request = $request->next()) { my $oid = $request->getOID(); if ($request_info->getMode() == MODE_GET) { # ... generally, you would calculate value from oid if ($oid == new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0")) { $request->setValue(ASN_OCTET_STR, $default_SP); } if ($oid == new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.3.0")) { $request->setValue(ASN_OCTET_STR, $default_PC); } } elsif ($request_info->getMode() == MODE_GETNEXT) { # ... generally, you would calculate value from oid if ( $oid < new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0")) { $request->setOID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0"); $request->setValue(ASN_OCTET_STR, $default_SP); $request->setOID(".1.3.6.1.4.1.193.37.10.11.64.10.1.3.0"); $request->setValue(ASN_OCTET_STR, $default_PC); } } elsif ($request_info->getMode() == MODE_SET_RESERVE1) { if ( ( $oid != new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0")) and ( $oid != new NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.3.0")) ) { # do error checking here $request->setError($request_info, SNMP_ERR_NOSUCHNAME); } } elsif ($request_info->getMode() == MODE_SET_ACTION) { # ... (or use the value) $value = $request->getValue(); } } } my $agent = new NetSNMP::agent( # makes the agent read a my_agent_name.conf file 'Name' => "my_agent_name", 'AgentX' => 1 ); $agent->register("my_agent_name", ".1.3.6.1.4.1.193.37.10.11.64.10", \&myhandler); my $running = 1; while($running) { $agent->agent_check_and_process(1); } $agent->shutdown(); Results: # snmpget -v2c -c public localhost .1.3.6.1.4.1.193.37.10.11.64.10.1.2.0 ACM-LOGWATCH-MIB::acmLogWatchSpecificProblem.0 = STRING: SP 1 # snmpget -v2c -c public localhost .1.3.6.1.4.1.193.37.10.11.64.10.1.3.0 ACM-LOGWATCH-MIB::acmLogWatchProbableCause.0 = STRING: PC 1 SNMPWALK doesn't show all the OID's set, but last one: # snmpwalk -v2c -c public localhost .1.3.6.1.4.1.193.37.10.11.64.10 ACM-LOGWATCH-MIB::acmLogWatchProbableCause.0 = STRING: PC 1 SNMPSET doesn't work: [root@redhatgp ACM]# snmpset -v2c -c public localhost .1.3.6.1.4.1.193.37.10.11.64.10.1.3.0 s "PC 2" ACM-LOGWATCH-MIB::acmLogWatchProbableCause.0 = STRING: PC 2 [root@redhatgp ACM]# snmpget -v2c -c public localhost .1.3.6.1.4.1.193.37.10.11.64.10.1.3.0 ACM-LOGWATCH-MIB::acmLogWatchProbableCause.0 = STRING: PC 1 Can anyone help me? Thanks BR Simone |
From: Wes H. <har...@us...> - 2021-05-06 17:45:14
|
Feroz <fer...@gm...> writes: > I tried as follows, serverRecvBuf and serverSendBuf worked, but timeout/retries didn't work. > > [snmp] timeout 10 > [snmp] retries 60 So if you're forwarding via traps, timeouts and retries make no sense since they're not acknowledged by the remote server. There is no way to know whether or not it was received. If you want that support, you should be using INFORMs instead of TRAPs. -- Wes Hardaker Please mail all replies to net...@li... |
From: Feroz <fer...@gm...> - 2021-05-05 10:25:28
|
I tried as follows, serverRecvBuf and serverSendBuf worked, but timeout/retries didn't work. [snmp] timeout 10 [snmp] retries 60 [snmp] serverRecvBuf 425984 [snmp] serverSendBuf 425984 Moreover, I see the value of Recv/Send Buf is getting doubled in "ss -lumpna" output. -Feroz On Fri, Apr 30, 2021 at 5:36 AM Wes Hardaker <har...@us...> wrote: > Feroz <fer...@gm...> writes: > > > I see "serverRecvBuf", "serverSendBuf","retries" but they don't seem > > to work, when used in snmptrapd.conf file. -- Regards, Feroz Ahmed > > If those are what you need, put them inside the snmptrapd.conf file with > a [snmp] tag before them: > > [snmp] > serverRecvBuf ... > serverSendBuf ... > > [snmptrapd] > # rest of file > -- > Wes Hardaker > Please mail all replies to net...@li... > -- Regards, Feroz Ahmed |
From: Simone M. <sim...@gm...> - 2021-05-03 10:13:08
|
Hi, I have not received yet any reply. Please, may you keep in consideration my request? I am registered on SourgeForce site, is there any action I have to take? Thank you BR Simone Il giorno gio 22 apr 2021 alle ore 13:14 Simone Moni <sim...@gm...> ha scritto: > Hi all, > I'm a newbie with AgentX. I need to extend snmpd with a new custom MIB > module. > I have NET-SNMP version 5.5 on Redhat, I would implement perl API, using > NetSNMP::agent. > Hereby, the steps I've done: > > - /etc/snmp/snmpd.conf > #sec.name source community > com2sec notConfigUser default public > #groupName securityModel securityName > group notConfigGroup v1 notConfigUser > group notConfigGroup v2c notConfigUser > #name incl/excl subtree mask(optional) > view all included .1 > #group context sec.model sec.level prefix read write notif > access notConfigGroup "" any noauth exact all all none > master agentx > > - MIB module > My custom MIB is related to an active alarms table for fault management. > It must be queryable from an external management station. > The MIB file (ACM-LOGWATCH-MIB) is located in /usr/share/snmp/mibs > directory. > > Here the subset for Table: > > acmLogWatchTable OBJECT-TYPE > SYNTAX SEQUENCE OF acmLogWatchEntry > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Table of objects" > ::= { acmLogWatch 10 } > > acmLogWatchEntry OBJECT-TYPE > SYNTAX acmLogWatchEntry > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "" > INDEX { acmLogWatchIndex } > ::= { acmLogWatchTable 1 } > > acmLogWatchEntry ::= SEQUENCE { > acmLogWatchIndex Integer32, > acmLogWatchSpecificProblem DisplayString, > acmLogWatchProbableCause DisplayString, > } > > acmLogWatchIndex OBJECT-TYPE > SYNTAX INTEGER > ACCESS read-only > STATUS mandatory > DESCRIPTION > "A unique value for each active alarm" > ::= { acmLogWatchEntry 1 } > > acmLogWatchSpecificProblem OBJECT-TYPE > SYNTAX DisplayString > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "the specific problem of the alarm" > ::= { acmLogWatchEntry 2 } > > acmLogWatchProbableCause OBJECT-TYPE > SYNTAX DisplayString > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "the probable cause of the alarm" > ::= { acmLogWatchEntry 3 } > > snmpset is used to set OID's Values. > > - perl code: > > use NetSNMP::agent (':all'); > use NetSNMP::ASN (':all'); > use NetSNMP::OID(':all'); > > my $default_SP = "SP 1"; > my $default_PC = "PC 1"; > > sub myhandler { > my ($handler, $registration_info, $request_info, $requests) = @_; > my $request; > > for($request = $requests; $request; $request = $request->next()) { > my $oid = $request->getOID(); > if ($request_info->getMode() == MODE_GET) { > # ... generally, you would calculate value from oid > if ($oid == new > NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0")) { > $request->setValue(ASN_OCTET_STR, $default_SP); > } > if ($oid == new > NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.3.0")) { > $request->setValue(ASN_OCTET_STR, $default_PC); > } > } elsif ($request_info->getMode() == MODE_GETNEXT) { > # ... generally, you would calculate value from oid > if ( $oid < new > NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0")) { > $request->setOID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0"); > $request->setValue(ASN_OCTET_STR, $default_SP); > $request->setOID(".1.3.6.1.4.1.193.37.10.11.64.10.1.3.0"); > $request->setValue(ASN_OCTET_STR, $default_PC); > } > } elsif ($request_info->getMode() == MODE_SET_RESERVE1) { > if ( ( $oid != new > NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.2.0")) and ( $oid != new > NetSNMP::OID(".1.3.6.1.4.1.193.37.10.11.64.10.1.3.0")) ) { # do error > checking here > $request->setError($request_info, SNMP_ERR_NOSUCHNAME); > } > } elsif ($request_info->getMode() == MODE_SET_ACTION) { > # ... (or use the value) > $value = $request->getValue(); > } > } > > } > > my $agent = new NetSNMP::agent( > # makes the agent read a my_agent_name.conf file > 'Name' => "my_agent_name", > 'AgentX' => 1 > ); > $agent->register("my_agent_name", ".1.3.6.1.4.1.193.37.10.11.64.10", > \&myhandler); > > my $running = 1; > while($running) { > $agent->agent_check_and_process(1); > } > > $agent->shutdown(); > > Results: > > # snmpget -v2c -c public localhost .1.3.6.1.4.1.193.37.10.11.64.10.1.2.0 > ACM-LOGWATCH-MIB::acmLogWatchSpecificProblem.0 = STRING: SP 1 > # snmpget -v2c -c public localhost .1.3.6.1.4.1.193.37.10.11.64.10.1.3.0 > ACM-LOGWATCH-MIB::acmLogWatchProbableCause.0 = STRING: PC 1 > > SNMPWALK doesn't show all the OID's set, but last one: > # snmpwalk -v2c -c public localhost .1.3.6.1.4.1.193.37.10.11.64.10 > ACM-LOGWATCH-MIB::acmLogWatchProbableCause.0 = STRING: PC 1 > > SNMPSET doesn't work: > [root@redhatgp ACM]# snmpset -v2c -c public localhost > .1.3.6.1.4.1.193.37.10.11.64.10.1.3.0 s "PC 2" > ACM-LOGWATCH-MIB::acmLogWatchProbableCause.0 = STRING: PC 2 > [root@redhatgp ACM]# snmpget -v2c -c public localhost > .1.3.6.1.4.1.193.37.10.11.64.10.1.3.0 > ACM-LOGWATCH-MIB::acmLogWatchProbableCause.0 = STRING: PC 1 > > Can anyone help me? > > Thanks > Simone > > > |
From: Wes H. <har...@us...> - 2021-04-30 00:07:06
|
Feroz <fer...@gm...> writes: > I see "serverRecvBuf", "serverSendBuf","retries" but they don't seem > to work, when used in snmptrapd.conf file. -- Regards, Feroz Ahmed If those are what you need, put them inside the snmptrapd.conf file with a [snmp] tag before them: [snmp] serverRecvBuf ... serverSendBuf ... [snmptrapd] # rest of file -- Wes Hardaker Please mail all replies to net...@li... |
From: Wes H. <har...@us...> - 2021-04-29 03:08:51
|
I've pushed Net-SNMP 5.9.1.rc1. This means we're now in the release-candidate cycle which requires request-for-vote posts to this list in order to approve any additional changes before the final release (with a delta of at least people voting positively for any change). https://sourceforge.net/projects/net-snmp/files/net-snmp/5.9.1-pre-releases/ -- Wes Hardaker Please mail all replies to net...@li... |