net-snmp-coders — Discussion of internal project coding (Please use this OR -users, NOT both!)

Does variable of data type ASN_OCTET_STR null terminated?

[Pushpa T. <pus...@gm...>]

Hi All,


I am adding SNMPGET support for a MIB object and have created a MIB
implementation file. Some sites say the datatype ASN_OCTET_STR is not
null-terminated as in a C-style string. I did see that snmp_set_var_value()
appends '\0' at the end of the ASN_OCTET_STR type.

Kindly confirm whether I have to terminate the string with a null character
and set the length to include the null character before calling
snmp_set_var_value().



Thanks,
Pushpa.T

Re: Regarding changing default agentXSocket

[Magnus F. <ma...@ly...>]

On Thu, Jan 09, 2025 at 10:58:22AM +0530, Pushpa Thimmaiah wrote:
> Hi All,
> 
> Net-snmp FAQ reads that agentx can be run with different unix socket
> address (i.e other that /var/agentx/master). I too verified it works fine.
> Is there any configuration file that reads by subagent (eg:./mysubagent in
> https://net-snmp.sourceforge.io/wiki/index.php/TUT:Writing_a_Subagent)

Subagents are independent programs so they might not even use the Net-SNMP
subagent implementation. If that is the case you have to ask the people who
wrote the subagent.

If the subagent is using the Net-SNMP implementation then it might
read the config files snmp.conf and <program>.conf

> Thanks,
> Pushpa.T
> 
> On Tue, Jan 7, 2025 at 10:37 AM Pushpa Thimmaiah <pus...@gm...>
> wrote:
> 
> > Hi All,
> >
> > I am configuring net-snmp  with  agentx support.  Can I change agentx
> > socket address to any path eg: /tmp/agentx/master ?
> > Its default unix socket address is /var/agentx/master?
> >
> > Add following in snmpd.conf
> >
> > master agentx
> > agentXSocket /tmp/agentx/master
> >
> >
> >
> > Thanks,
> > Pushpa.T
> >


> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Re: Regarding changing default agentXSocket

[Pushpa T. <pus...@gm...>]

Hi All,

Net-snmp FAQ reads that agentx can be run with different unix socket
address (i.e other that /var/agentx/master). I too verified it works fine.
Is there any configuration file that reads by subagent (eg:./mysubagent in
https://net-snmp.sourceforge.io/wiki/index.php/TUT:Writing_a_Subagent)

Thanks,
Pushpa.T

On Tue, Jan 7, 2025 at 10:37 AM Pushpa Thimmaiah <pus...@gm...>
wrote:

> Hi All,
>
> I am configuring net-snmp  with  agentx support.  Can I change agentx
> socket address to any path eg: /tmp/agentx/master ?
> Its default unix socket address is /var/agentx/master?
>
> Add following in snmpd.conf
>
> master agentx
> agentXSocket /tmp/agentx/master
>
>
>
> Thanks,
> Pushpa.T
>

engineTime not resetting upon snmpd restart

[Pushpa T. <pus...@gm...>]

Hi All,

I am sending engineTime,engineBoot in outgoing  snmpv3 traps. I have
noticed that enginetime is not resetting to zero upon snmpd restart
however, engineBoot time is getting incremented properly. However,
trapreceiver (silvercreek, snmp4j, snmptrapd) doesnot complaint and
authenticate the same
Is there any situation that makes engineTime not reset?

Details:
net-snmp Version: 5.7.3
OS : linux


Thanks,
Pushpa.T

Regarding changing default agentXSocket

[Pushpa T. <pus...@gm...>]

Hi All,

I am configuring net-snmp  with  agentx support.  Can I change agentx
socket address to any path eg: /tmp/agentx/master ?
Its default unix socket address is /var/agentx/master?

Add following in snmpd.conf

master agentx
agentXSocket /tmp/agentx/master



Thanks,
Pushpa.T

VACM token in snmpd.conf not recognized

[Vincent G. <vin...@ov...>]

Hello,

I've implemented my own net-snmp Agent in a Linux embedded system.

While the Agent seems to start correctly, it seems the config file parser is not recognizing the VACM tokens "createUser ", "rwuser", "group", "access" and "view" within my snmpd.conf file

Snmpd.log file shows :

9:read_config:line: /var/net-snmp/snmpd.conf:1 examining: createUser vincent
trace: read_config(): read_config.c, 994:
read_config:line: /var/net-snmp/snmpd.conf:1 examining: createUser vincent
/var/net-snmp/snmpd.conf: line 1: Warning: Unknown token: createUser.

I have this snmpd.conf log file :

createUser vincent

#
# Listening connections :
agentAddress dtlsudp:10161
#
# DTLS, TLS and certificates support :
[snmp] tlsAlgorithms DEFAULT
[snmp] localCert tboxvincent

# User access :
view viewallmibs included .1
access grptbox "" any priv exact viewallmibs viewallmibs none
access grptbox_unsec "" any auth exact viewallmibs none none

certSecName 10 2D:27:C4:AC:4D:5B:39:7C:51:99:8A:80:F9:C3:80:F7:D5:3D:64:8E --sn vincent
group grptbox tsm vincent
rwuser -s tsm vincent priv -V viewallmibs


And this configure call :

./configure --prefix=$(INSTALL_PREFIX) --host=$(HOST) \
              --disable-applications --enable-debugging --disable-embedded-perl --without-perl-modules \
              --enable-reentrant \
              --with-cc=$(CC) --with-linkcc=$(CC) --with-ar=$(AR) --with-ldflags="$(LDFLAGS)" --with-cflags="$(CFLAGS_EXT)" \
              --with-openssl=$(LIB_DIRS) \
              --without-rpm \
              --with-logfile="/tmp/var/snmpd.log" \
              --with-default-snmp-version="3" \
              --with-transports="UDP,TCP,DTLSUDP,TLSTCP" --with-security-modules="usm,tsm" \
              --with-persistent-directory="/var/net-snmp" \
              --enable-shared=yes --enable-static=no --enable-tagCC-libtool


Any ideas ?

Thanks for helping !

Vincent.

Regarding engineTime value when snmpd restart

[Pushpa T. <pus...@gm...>]

Hi All,

Is there any scenario where engineTime Value not reset to zero  upon snmpd
restart?

Details:
OS: Linux
Version: 5.7.3

I can see engineBoot counter is getting increment and engineTime also
increments instead of reset to zero.

engineBoot: 2
engineTime: 1200

restart snmpd
engineBoot: 3
engineTime: 1201 or 1103 (increments or decrements but not reset to zero)

I am using same net-snmp version on other desktop and can see it is
resetting to zero upon snmp restart.

Thanks,
Pushpa.T

Tools for converting V3 to V1 traps or vice versa.

[Suresh <skj...@ho...>]

Hi all
I have the below requirement

Supporiting SNMP V3 veriosn on device.
Where we SNMP V1 agent already written in C++ code working fine , so we are planning to use Net-snmp for V3 support.
I know that net-snmp will support using AgentX, but how will I configure this?

2. Second, if any Net-snmp is not running on that device , then V1 Agent will be able to respond, get/walk, and be able to generate V1 trap.
So because of these, I need tools that are able to convert V3 trap to V1 and vice versa. is such type tools are  available in net-snmp.

 3. And what type of authentication and encryption methods are supported by net-snmp (other than MD5, SHA, and DES AES)? Because MD5 ,SHA and AES,DES not much secure

Thanks
Suresh

Re: (Previous email had a weird formatting) Custom Mib returning wrong values when Magic number is larger than 255

[Craig S. <cs...@dr...>]

Hi,
  You can definitely have more than 255 custom OIDs, the trick is you only
have 255 values for magic. I'm surprised hacking the magic value didn't
crash it before.

There's probably a few options; the good, the bad and the ugly.

Good
Rebuild the MIB and functions so each type of variable uses a different
accessor function, so testboard_var becomes testboard_load,
testboard_temperature etc.
As long as you don't have 256 temperature sensors or load sensors or same
things this works. If you have different ways of getting values, it also
means the
functions are simpler/smaller because the temperature getter has no code
for working out system load and vice-versa. It also means you're not
bothering to fetch the
temperature when you want to get the load too.

Bad
Keep the mib as it is, but have several accessor functions which have a
different magic which you add to the parameters passed to the real accessor.
Your testboard_var() will need a new parameter, say mymagic which is
something larger than u_char

testboard_var1(vp, other variables)
  return (testboard_var(vp->magic, vp, other variables)
testboard_var2(vp, other_variables)
  return (testboard_var(vp->magic+256, vp, other_variables)
testboard_var3(vp, other_variables)
  return (testboard_var(vp->magic+512, vp, other_variables)
In your variables array the ones that use 1-255 use testboard_var1, 256-511
use testboard_var2 (but use magic-256) etc.

Ugly
Overload or ignore the magic and match on the OID directly, which is called
vp->name. There's a reason why this is the ugly option.

 - Craig


On Sat, 21 Sept 2024 at 05:24, Neeraj Bansal <nee...@gm...>
wrote:

> That makes sense Craig. Thank you for your input.
>
> To summarize the issue, we are unable to use more than 255 OID entries and
> would love to get any help on this issue.
>
> Is there another way to use more than 255 custom OID's?
>
> Thank You to anyone looking into this matter.
>
> - Neeraj
>
> On Mon, 29 Jul 2024 at 14:26, Craig Small <csmall@dropbear.xyz> wrote:
>
>> On Fri, 12 Jul 2024 at 08:31, Neeraj Bansal <nee...@gm...>
>> wrote:
>> > We recompile everything and install no problem, but instead of fixing
>> our problem it caused net-snmp-5.9.3 to not be able to start. The error it
>> gives is: Bad user id, which could be a red herring. example below:
>> > [root@testboard: /root# /etc/init.d/S59netsnmp restart
>> > Stopping SNMP daemon: [OK]
>> > Starting SNMP daemon: Bad user id: snmp
>> I think it is a red herring, that error is from the -u option.
>>
>> # /usr/sbin/snmpd -u blah
>> Bad user id: blah
>>
>> I know that is not solving your main issue, but its got rid of one thing.
>>
>>  - Craig
>>
>>
>>
>> > [root@testboard: /root#
>> >
>> > So, we take our patches out and recompile and install, and it works
>> again but still has the 255 custom oid limitation.
>> >
>> > A snippet from our header file. Too big to paste it all.
>> >
>> > #define TEMPC 1
>> > #define TEMPF 2
>> > #define   UPTIME_STR 3
>> > #define   SERIALNUMBER 4
>> > #define   ALLOFIT 5
>> > #define   ROOTFSBUILD 6
>> > #define   KERNELBUILD      7
>> > #define   OSINFO    8
>> > ......
>> > #define PRODUCT_ID 250
>> > #define RUNSCRIPT 251
>> > #define TIMER1 252
>> > #define TIMER2 253
>> > #define TIMER3 254
>> > #define TIMER4 255
>> > #define TIMER5 256 <- This outpts an error because it wraps around and
>> 0 is not defined.
>> > #define TIMER6 257 <- This outputs TEMPC value instead of TIMER6.
>> > #define TIMER7 258
>> > #define TIMER8 259
>> > #define TIMER9 260
>> > #define TIMER10 261
>> >
>> > #define    EXAMPLETIMETICKS 3333
>> > #define EXAMPLEIPADDRESS        4444
>> > #define   EXAMPLECOUNTER 7777
>> > #define EXAMPLEGAUGE            8888
>> > #define EXAMPLETRIGGERTRAP      9999
>> > #define EXAMPLETRIGGERTRAP2     1000
>> >
>> > Notice the example defines above that were provided in the example C
>> header file, those magic numbers would have never worked because of the
>> u_char (8-bit) magic variable limitation.
>> >
>> > This is a code snippet from our custom mib C file.
>> >
>> > struct variable4 testboard_variables[] = {
>> >    {ROOTFSBUILD, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2,
>> {7, 1}},
>> >    {KERNELBUILD, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2,
>> {7, 2}},
>> >    {OSINFO, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2, {7,
>> 3}},
>> >    {PRODUCT_ID, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, etestboard_var, 2,
>> {7, 4}},
>> >    {UPTIME_STR, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2,
>> {5, 1}},
>> >    {SERIALNUMBER, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var,
>> 2, {5, 2}},
>> >    {TEMPC, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2,
>> {6,1}},
>> >    {TEMPF, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2,
>> {6,2}},
>> >
>> > We have poured over the souce code looking for any other instance of
>> u_char magic that we may have missed, but they are only defined in the two
>> files mentioned above.
>> >
>> > We need some help with this. What else do we need to do in the 5.9
>> versions to make the magic number not wrap around to zero after 255 and not
>> crash when we do that?
>> >
>> > Thanks,
>> >
>> > Neeraj Bansal
>> > _______________________________________________
>> > Net-snmp-coders mailing list
>> > Net...@li...
>> > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>>
>

Please help

[Shaji, S. (GE V. consultant) <Sre...@ge...>]

Hi,

Please help us for an issue observing in our application.

SNMP version using  : net-snmp-5.9.4
OpenSSL version : openssl-3.0.13

Our application supports

  *   SNMP polling for version 1 , 2c and 3 and encryption SHA, MD5, AES, DES,
  *   SNMP traps

We are using more than 60 + devices to get the SNMP information. We use continuous device polling via threads.
Now we found memory leaks in the application while using SNMP v3 version. No issues found in SNMP v2 version.
The issues found in snmp_sess_synch_response with v3 version only.
When we use all other code except this line, no leak found. When we include this function with v3 issue coming.

Please find the usage below,

snmp_sess_init(&session);

ss = snmp_sess_open(&session);

Setting v3 parameters
{

}

/*pdu create/*
snmp_pdu_create

snmp_sess_synch_response(ss, pdu, &response);

/* data parsing /*

if (response)
{
      snmp_free_pdu(response);
}

//freed V3 and other configuration memory
free(session.peername); session.peername= NULL;
free(session.securityName); session.peername= NULL;

snmp_sess_close(ss);

Please let us know any memory leak bug reported for V3 in openssl or net snmp side and any patch or fix is available?
Please reply ASAP it is Very CRITICAL

Thanks
Sreeja Shaji

Re: snmpd failed to start when agentx is enabled

[Pushpa T. <pus...@gm...>]

Hi Bill Fenner,

Issue resolved. I have rebooted the device and started snmpd .  socket file
/var/agentx/master got created and example code is working.

Thanks,
Pushpa.T

On Thu, Oct 3, 2024 at 5:09 PM Pushpa Thimmaiah <pus...@gm...>
wrote:

> Hi Bill Fenner,
>
> Thank you. I enabled Unix transport and added 'agentXSocket
> /var/agentx/master' in /etc/snmp/snmpd.conf, and I was able to execute
> snmpd. There was no /var/agentx/master created after starting snmpd, and
> AgentX was unable to connect to snmpd.
> I am following the AgentX tutorial at
> http://www.net-snmp.org/tutorial/tutorial-5/toolkit/demon/. Kindly guide.
>
> *example_daemon log*
>
> tdomain: Found domain "unix" from specifier "unix"
> trace: netsnmp_lookup_default_target(): snmp_service.c, 413:
> defaults: netsnmp_lookup_default_target("agentx", "unix") ->
> "/var/agentx/master"
> trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 794:
> tdomain: trying domain "unix" address "[NIL]" default address
> "/var/agentx/master"
> trace: netsnmp_unix_transport(): transports/snmpUnixDomain.c, 322:
> netsnmp_unix: open remote Local IPC: /var/agentx/master
> trace: netsnmp_unix_transport(): transports/snmpUnixDomain.c, 432:
> netsnmp_unix_transport: *couldn't connect to "/var/agentx/master"*, errno
> 2 (No such file or directory)
>
> *Snmpd.log*
> trace: read_config(): read_config.c, 843:
> 9:read_config:line: /etc/snmp/snmpd.conf:214 examining: agentXSocket
> /var/agentx/master
> trace: read_config(): read_config.c, 971:
> read_config:line: /etc/snmp/snmpd.conf:214 examining: agentXSocket
> /var/agentx/master
> trace: run_config_handler(): read_config.c, 536:
> read_config:parser: Found a parser.  Calling it: agentXSocket /
> /var/agentx/master
> trace: agentx_parse_agentx_socket(): mibgroup/agentx/agentx_config.c, 34:
> agentx/config: port spec: /var/agentx/master
> trace: netsnmp_ds_set_string(): default_store.c, 285:
> *netsnmp_ds_set_string: Setting APP:1 = "/var/agentx/master"*
> trace: read_config(): read_config.c, 843:
>
>
> *Details:-*
>
> Both snmpd , agentx example 'example-daemon'  and folder /var/agentx  has
> same permission
> root@SyncServer:/var/log# ls -la /var/agentx
> total 8
> drwxr-xr-x  2 root root 4096 Oct  2 11:46 .
> drwxr-xr-x 13 root root 4096 Oct  2 11:46 ..
> root@SyncServer:/var/log# ls -la /usr/sbin/snmpd
> -rwxr-xr-x 1 root root 64488 Oct  2 09:59 /usr/sbin/snmpd
> root@SyncServer:/var/log# ls -la /tmp/example-demon
> -rwxr-xr-x 1 root root 37664 Oct  2 09:52 /tmp/example-demon
>
>
> *net-snmp-5.9 config summary*
>
>  SNMP Versions Supported:    1 2c 3
>   Building for:               linux
>   Net-SNMP Version:           5.9
>   Network transport support:  Unix Alias UDP UDPIPv6 Callback UDPIPv4Base
> UDPBase IPv4Base IPBase SocketBase IPv6Base
>   SNMPv3 Security Modules:     usm
>   Agent MIB code:            clock default_modules gnss host mibII
> notification ntpSystem snmpv3mibs system target utilities =>  snmpv3mibs
> mibII notification notification-log-mib target* agentx* disman/event
> disman/schedule utilities host host/hrh_storage host/hrh_filesys
> host/hrSWInstalledTable host/hrSWRunTable host/hr_system host/hr_device
> host/hr_other host/hr_proc host/hr_network host/hr_print host/hr_disk
> host/hr_partition mibII/system_mib mibII/sysORTable mibII/snmp_mib
> mibII/vacm_vars mibII/setSerialNo mibII/at mibII/ifTable mibII/ip mibII/tcp
> mibII/udp mibII/ipv6 mibII/icmp if-mib ip-mib ip-forward-mib tcp-mib
> udp-mib notification/snmpNotifyTable
> snmp-notification-mib/snmpNotifyFilterTable
> notification/snmpNotifyFilterProfileTable ntpSystem/ntpSystem
> snmpv3/snmpEngine snmpv3/snmpMPDStats snmpv3/usmStats snmpv3/usmConf
> snmpv3/usmUser system/system target/snmpTargetAddrEntry
> target/snmpTargetParamsEntry target/target target/target_counters
> utilities/override utilities/execute utilities/iquery
>   MYSQL Trap Logging:         unavailable
>   Embedded Perl support:      disabled
>   SNMP Perl modules:          disabled
>   SNMP Python modules:        disabled
>   Crypto support from:        crypto
>   Authentication support:     MD5 SHA1 SHA224 SHA256 SHA384 SHA512
>   Encryption support:         DES AES AES128 AES192 AES192C AES256 AES256C
>   Local DNSSEC validation:    disabled
>
> Thanks,
> Pushpa.T
>
> On Fri, Sep 27, 2024 at 12:14 AM Bill Fenner <fe...@gm...> wrote:
>
>> Hi Pushpa,
>>
>> You are not enabling UNIX domain support, so net-snmp can't open the UNIX
>> domain socket for agentx. You can either use the TCP socket by configuring
>> with something like
>>
>> agentXSocket tcp:127.0.0.1:705
>>
>> and then configuring clients similarly, e.g., "snmptrap -X tcp:705"
>>
>> Or adding the UNIX domain transport, e.g., add "Unix" to your
>> "--with-transports" configure argument.
>>
>>   Bill
>>
>>
>> On Thu, Sep 26, 2024 at 9:20 AM Pushpa Thimmaiah <
>> pus...@gm...> wrote:
>>
>>> Hi All,
>>>
>>> I am getting following error while starting snmpd in net-snmp-5.9. I
>>> have enabled  agentx and compiled the source. Kindly guide me to resolve
>>> the same.
>>> I have created directory /var/agentx
>>> ---------------
>>>
>>> agentx/master: initializing...
>>> trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 655:
>>> tdomain: tdomain_transport_spec("agentx", "/var/agentx/master", 1,
>>> "[NIL]", "[NIL]", "[NIL]")
>>> trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 736:
>>> tdomain: Address starts with '/', so assume "unix" domain
>>> trace: find_tdomain(): snmp_transport.c, 610:
>>> tdomain: Found no domain from specifier "unix"
>>> No support for any checked transport domain
>>> Error: Couldn't open a master agentx socket to listen on
>>> (/var/agentx/master):
>>> ---------------------------------------------------
>>>
>>>
>>> Thanks,
>>> Pushpa.T
>>> _______________________________________________
>>> Net-snmp-coders mailing list
>>> Net...@li...
>>> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>>>
>>

Re: snmpd failed to start when agentx is enabled

[Pushpa T. <pus...@gm...>]

Hi Bill Fenner,

Thank you. I enabled Unix transport and added 'agentXSocket
/var/agentx/master' in /etc/snmp/snmpd.conf, and I was able to execute
snmpd. There was no /var/agentx/master created after starting snmpd, and
AgentX was unable to connect to snmpd.
I am following the AgentX tutorial at
http://www.net-snmp.org/tutorial/tutorial-5/toolkit/demon/. Kindly guide.

*example_daemon log*

tdomain: Found domain "unix" from specifier "unix"
trace: netsnmp_lookup_default_target(): snmp_service.c, 413:
defaults: netsnmp_lookup_default_target("agentx", "unix") ->
"/var/agentx/master"
trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 794:
tdomain: trying domain "unix" address "[NIL]" default address
"/var/agentx/master"
trace: netsnmp_unix_transport(): transports/snmpUnixDomain.c, 322:
netsnmp_unix: open remote Local IPC: /var/agentx/master
trace: netsnmp_unix_transport(): transports/snmpUnixDomain.c, 432:
netsnmp_unix_transport: *couldn't connect to "/var/agentx/master"*, errno 2
(No such file or directory)

*Snmpd.log*
trace: read_config(): read_config.c, 843:
9:read_config:line: /etc/snmp/snmpd.conf:214 examining: agentXSocket
/var/agentx/master
trace: read_config(): read_config.c, 971:
read_config:line: /etc/snmp/snmpd.conf:214 examining: agentXSocket
/var/agentx/master
trace: run_config_handler(): read_config.c, 536:
read_config:parser: Found a parser.  Calling it: agentXSocket /
/var/agentx/master
trace: agentx_parse_agentx_socket(): mibgroup/agentx/agentx_config.c, 34:
agentx/config: port spec: /var/agentx/master
trace: netsnmp_ds_set_string(): default_store.c, 285:
*netsnmp_ds_set_string: Setting APP:1 = "/var/agentx/master"*
trace: read_config(): read_config.c, 843:


*Details:-*

Both snmpd , agentx example 'example-daemon'  and folder /var/agentx  has
same permission
root@SyncServer:/var/log# ls -la /var/agentx
total 8
drwxr-xr-x  2 root root 4096 Oct  2 11:46 .
drwxr-xr-x 13 root root 4096 Oct  2 11:46 ..
root@SyncServer:/var/log# ls -la /usr/sbin/snmpd
-rwxr-xr-x 1 root root 64488 Oct  2 09:59 /usr/sbin/snmpd
root@SyncServer:/var/log# ls -la /tmp/example-demon
-rwxr-xr-x 1 root root 37664 Oct  2 09:52 /tmp/example-demon


*net-snmp-5.9 config summary*

 SNMP Versions Supported:    1 2c 3
  Building for:               linux
  Net-SNMP Version:           5.9
  Network transport support:  Unix Alias UDP UDPIPv6 Callback UDPIPv4Base
UDPBase IPv4Base IPBase SocketBase IPv6Base
  SNMPv3 Security Modules:     usm
  Agent MIB code:            clock default_modules gnss host mibII
notification ntpSystem snmpv3mibs system target utilities =>  snmpv3mibs
mibII notification notification-log-mib target* agentx* disman/event
disman/schedule utilities host host/hrh_storage host/hrh_filesys
host/hrSWInstalledTable host/hrSWRunTable host/hr_system host/hr_device
host/hr_other host/hr_proc host/hr_network host/hr_print host/hr_disk
host/hr_partition mibII/system_mib mibII/sysORTable mibII/snmp_mib
mibII/vacm_vars mibII/setSerialNo mibII/at mibII/ifTable mibII/ip mibII/tcp
mibII/udp mibII/ipv6 mibII/icmp if-mib ip-mib ip-forward-mib tcp-mib
udp-mib notification/snmpNotifyTable
snmp-notification-mib/snmpNotifyFilterTable
notification/snmpNotifyFilterProfileTable ntpSystem/ntpSystem
snmpv3/snmpEngine snmpv3/snmpMPDStats snmpv3/usmStats snmpv3/usmConf
snmpv3/usmUser system/system target/snmpTargetAddrEntry
target/snmpTargetParamsEntry target/target target/target_counters
utilities/override utilities/execute utilities/iquery
  MYSQL Trap Logging:         unavailable
  Embedded Perl support:      disabled
  SNMP Perl modules:          disabled
  SNMP Python modules:        disabled
  Crypto support from:        crypto
  Authentication support:     MD5 SHA1 SHA224 SHA256 SHA384 SHA512
  Encryption support:         DES AES AES128 AES192 AES192C AES256 AES256C
  Local DNSSEC validation:    disabled

Thanks,
Pushpa.T

On Fri, Sep 27, 2024 at 12:14 AM Bill Fenner <fe...@gm...> wrote:

> Hi Pushpa,
>
> You are not enabling UNIX domain support, so net-snmp can't open the UNIX
> domain socket for agentx. You can either use the TCP socket by configuring
> with something like
>
> agentXSocket tcp:127.0.0.1:705
>
> and then configuring clients similarly, e.g., "snmptrap -X tcp:705"
>
> Or adding the UNIX domain transport, e.g., add "Unix" to your
> "--with-transports" configure argument.
>
>   Bill
>
>
> On Thu, Sep 26, 2024 at 9:20 AM Pushpa Thimmaiah <
> pus...@gm...> wrote:
>
>> Hi All,
>>
>> I am getting following error while starting snmpd in net-snmp-5.9. I have
>> enabled  agentx and compiled the source. Kindly guide me to resolve the
>> same.
>> I have created directory /var/agentx
>> ---------------
>>
>> agentx/master: initializing...
>> trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 655:
>> tdomain: tdomain_transport_spec("agentx", "/var/agentx/master", 1,
>> "[NIL]", "[NIL]", "[NIL]")
>> trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 736:
>> tdomain: Address starts with '/', so assume "unix" domain
>> trace: find_tdomain(): snmp_transport.c, 610:
>> tdomain: Found no domain from specifier "unix"
>> No support for any checked transport domain
>> Error: Couldn't open a master agentx socket to listen on
>> (/var/agentx/master):
>> ---------------------------------------------------
>>
>>
>> Thanks,
>> Pushpa.T
>> _______________________________________________
>> Net-snmp-coders mailing list
>> Net...@li...
>> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>>
>

Re: snmpd failed to start when agentx is enabled

[Bill F. <fe...@gm...>]

Hi Pushpa,

You are not enabling UNIX domain support, so net-snmp can't open the UNIX
domain socket for agentx. You can either use the TCP socket by configuring
with something like

agentXSocket tcp:127.0.0.1:705

and then configuring clients similarly, e.g., "snmptrap -X tcp:705"

Or adding the UNIX domain transport, e.g., add "Unix" to your
"--with-transports" configure argument.

  Bill


On Thu, Sep 26, 2024 at 9:20 AM Pushpa Thimmaiah <pus...@gm...>
wrote:

> Hi All,
>
> I am getting following error while starting snmpd in net-snmp-5.9. I have
> enabled  agentx and compiled the source. Kindly guide me to resolve the
> same.
> I have created directory /var/agentx
> ---------------
>
> agentx/master: initializing...
> trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 655:
> tdomain: tdomain_transport_spec("agentx", "/var/agentx/master", 1,
> "[NIL]", "[NIL]", "[NIL]")
> trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 736:
> tdomain: Address starts with '/', so assume "unix" domain
> trace: find_tdomain(): snmp_transport.c, 610:
> tdomain: Found no domain from specifier "unix"
> No support for any checked transport domain
> Error: Couldn't open a master agentx socket to listen on
> (/var/agentx/master):
> ---------------------------------------------------
>
>
> Thanks,
> Pushpa.T
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>

snmpd failed to start when agentx is enabled

[Pushpa T. <pus...@gm...>]

Hi All,

I am getting following error while starting snmpd in net-snmp-5.9. I have
enabled  agentx and compiled the source. Kindly guide me to resolve the
same.
I have created directory /var/agentx
---------------

agentx/master: initializing...
trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 655:
tdomain: tdomain_transport_spec("agentx", "/var/agentx/master", 1, "[NIL]",
"[NIL]", "[NIL]")
trace: netsnmp_tdomain_transport_tspec(): snmp_transport.c, 736:
tdomain: Address starts with '/', so assume "unix" domain
trace: find_tdomain(): snmp_transport.c, 610:
tdomain: Found no domain from specifier "unix"
No support for any checked transport domain
Error: Couldn't open a master agentx socket to listen on
(/var/agentx/master):
---------------------------------------------------


Thanks,
Pushpa.T

Re: (Previous email had a weird formatting) Custom Mib returning wrong values when Magic number is larger than 255

[Neeraj B. <nee...@gm...>]

That makes sense Craig. Thank you for your input.

To summarize the issue, we are unable to use more than 255 OID entries and
would love to get any help on this issue.

Is there another way to use more than 255 custom OID's?

Thank You to anyone looking into this matter.

- Neeraj

On Mon, 29 Jul 2024 at 14:26, Craig Small <csmall@dropbear.xyz> wrote:

> On Fri, 12 Jul 2024 at 08:31, Neeraj Bansal <nee...@gm...>
> wrote:
> > We recompile everything and install no problem, but instead of fixing
> our problem it caused net-snmp-5.9.3 to not be able to start. The error it
> gives is: Bad user id, which could be a red herring. example below:
> > [root@testboard: /root# /etc/init.d/S59netsnmp restart
> > Stopping SNMP daemon: [OK]
> > Starting SNMP daemon: Bad user id: snmp
> I think it is a red herring, that error is from the -u option.
>
> # /usr/sbin/snmpd -u blah
> Bad user id: blah
>
> I know that is not solving your main issue, but its got rid of one thing.
>
>  - Craig
>
>
>
> > [root@testboard: /root#
> >
> > So, we take our patches out and recompile and install, and it works
> again but still has the 255 custom oid limitation.
> >
> > A snippet from our header file. Too big to paste it all.
> >
> > #define TEMPC 1
> > #define TEMPF 2
> > #define   UPTIME_STR 3
> > #define   SERIALNUMBER 4
> > #define   ALLOFIT 5
> > #define   ROOTFSBUILD 6
> > #define   KERNELBUILD      7
> > #define   OSINFO    8
> > ......
> > #define PRODUCT_ID 250
> > #define RUNSCRIPT 251
> > #define TIMER1 252
> > #define TIMER2 253
> > #define TIMER3 254
> > #define TIMER4 255
> > #define TIMER5 256 <- This outpts an error because it wraps around and 0
> is not defined.
> > #define TIMER6 257 <- This outputs TEMPC value instead of TIMER6.
> > #define TIMER7 258
> > #define TIMER8 259
> > #define TIMER9 260
> > #define TIMER10 261
> >
> > #define    EXAMPLETIMETICKS 3333
> > #define EXAMPLEIPADDRESS        4444
> > #define   EXAMPLECOUNTER 7777
> > #define EXAMPLEGAUGE            8888
> > #define EXAMPLETRIGGERTRAP      9999
> > #define EXAMPLETRIGGERTRAP2     1000
> >
> > Notice the example defines above that were provided in the example C
> header file, those magic numbers would have never worked because of the
> u_char (8-bit) magic variable limitation.
> >
> > This is a code snippet from our custom mib C file.
> >
> > struct variable4 testboard_variables[] = {
> >    {ROOTFSBUILD, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2,
> {7, 1}},
> >    {KERNELBUILD, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2,
> {7, 2}},
> >    {OSINFO, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2, {7,
> 3}},
> >    {PRODUCT_ID, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, etestboard_var, 2,
> {7, 4}},
> >    {UPTIME_STR, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2,
> {5, 1}},
> >    {SERIALNUMBER, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2,
> {5, 2}},
> >    {TEMPC, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2, {6,1}},
> >    {TEMPF, ASN_OCTET_STR, NETSNMP_OLDAPI_RONLY, testboard_var, 2, {6,2}},
> >
> > We have poured over the souce code looking for any other instance of
> u_char magic that we may have missed, but they are only defined in the two
> files mentioned above.
> >
> > We need some help with this. What else do we need to do in the 5.9
> versions to make the magic number not wrap around to zero after 255 and not
> crash when we do that?
> >
> > Thanks,
> >
> > Neeraj Bansal
> > _______________________________________________
> > Net-snmp-coders mailing list
> > Net...@li...
> > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>

Re: Reconfigure snmpd listening ports

[Teus B. <teu...@gm...>]

On Wed, 18 Sept 2024 at 14:35, Craig Small <csmall@dropbear.xyz> wrote:
[...]

Hello,

Thank you lots for confirming what I already feared would be the case.

I like the idea of putting something in front of the SNMP daemon that will
manage ports opening and closing, I never thought of this, but when
thinking about it, it seems like a good solution. I guess that something
controlling iptables on the fly would do this well.

Thanks again,

Regards,

Teus Benschop




On Mon, 16 Sept 2024 at 22:44, Teus Benschop <teu...@gm...> wrote:
>
>> The daemon kept the same ports open as before editing the snmpd.conf even
>> in case some agentaddress entries were removed from snmpd.conf.
>>
> Some changes to the configuration file can be enabled with a reload or HUP
> and some things need a complete restart.
>
> Changing ports is one of those complete restart things.
>
> There might be many reasons for it, but one of them would be that binding
> to low ports needs root (or capabilities)
> but you can also change to a different user after binding the ports. Once
> you're non root, there's no going back
> so binding to ports could fail.
>
> Interestingly enough, that "snmpd restarted" message is in
> snmpd_reconfig(). Technically it's not restarting.
>
> The port bindings happen in init_master_agent() with the repeated calls in
> netsnmp_agent_listen_on()
> In theory you could do a bunch of nsap_unregisters then copy that do-while
> loop into snmpd_reconfig() but I think the end-result
> is something that sort of does what you want but breaks in new interesting
> random ways because I'm sure something somewhere
> in snmpd assumes the NSAPs (the sockets effectively) remain the same.
>
> If I needed to shift ports around dynamically, I'd approach it from
> restarting the daemon and saving the state somehow
> or do some funky DNAT/load balancer type thing that moved the ports for me
> and left snmpd alone.
>

Re: Reconfigure snmpd listening ports

[Craig S. <cs...@dr...>]

On Mon, 16 Sept 2024 at 22:44, Teus Benschop <teu...@gm...> wrote:

> The daemon kept the same ports open as before editing the snmpd.conf even
> in case some agentaddress entries were removed from snmpd.conf.
>
Some changes to the configuration file can be enabled with a reload or HUP
and some things need a complete restart.

Changing ports is one of those complete restart things.

There might be many reasons for it, but one of them would be that binding
to low ports needs root (or capabilities)
but you can also change to a different user after binding the ports. Once
you're non root, there's no going back
so binding to ports could fail.

Interestingly enough, that "snmpd restarted" message is in
snmpd_reconfig(). Technically it's not restarting.

The port bindings happen in init_master_agent() with the repeated calls in
netsnmp_agent_listen_on()
In theory you could do a bunch of nsap_unregisters then copy that do-while
loop into snmpd_reconfig() but I think the end-result
is something that sort of does what you want but breaks in new interesting
random ways because I'm sure something somewhere
in snmpd assumes the NSAPs (the sockets effectively) remain the same.

If I needed to shift ports around dynamically, I'd approach it from
restarting the daemon and saving the state somehow
or do some funky DNAT/load balancer type thing that moved the ports for me
and left snmpd alone.

Reconfigure snmpd listening ports

[Teus B. <teu...@gm...>]

Hello,

The SNMP daemon can be configured to listen on a set of ports through
entries like this in file snmpd.conf :

agentaddress tcp:2161
agentaddress tcp:2162

I tried to reconfigure the daemon to listen on more or less ports than the
above as follows:
1. Edit snmpd.conf and add or remove agentaddress entries.
2. $ killall -HUP snmpd

The logging was like this:

Reconfiguring daemon
NET-SNMP version 5.9.4.pre2 restarted

The daemon kept the same ports open as before editing the snmpd.conf even
in case some agentaddress entries were removed from snmpd.conf.

Questions:
1. Is this the correct way of reconfiguring the SNMP agent?
2. How to add or remove listening ports during reconfigure, is this even
possible at all?
3. Can I do a bit of library patching work to get this done?

Thank you for considering this question, and thank you for the great SNMP
library, we use it a lot.

With kind regards,

Teus Benschop

[Pushpa T. <pus...@gm...>]

Hi All,

I am learning about the AgentX subagent to support SNMPGET/SNMPSET.
 Kindly provide clarification for the below queries:

   1. Do I need to use both --with-agentx and --with-mib-modules="agentx"
   in Net-SNMP to have AgentX support?
   2. I am following
   http://www.net-snmp.org/tutorial/tutorial-5/toolkit/demon/. I have
   encountered the following error upon execution

*./example-demon &*

Warning: Failed to connect to the agentx master agent ([NIL]):
example-demon is up and running.
Warning: Failed to connect to the agentx master agent ([NIL]):


Thank you,
Pushpa.T

Having some issues moving subagent from running with 5.8 to 5.9

[Lennart S. <lso...@gm...>]

I am trying to get a subagent to work after moving from net-snmp 5.8 to
5.9, but it keeps segfaulting for me.  I have tracked down that it is
failing when trying to sort the table due to the structure not being what
it should be.  It is using table_container to store the tables that are
causing issues.  If I switch them to linked_list, they work fine, and no
more bad pointer accesses.  The bad pointer accesses are showing as trying
to compare oids where the length is in fact one of the pointers rather than
the actual length of the oid, so it makes sense to be crashing when that
happens.  The code has not really changed in years and has been working
with many versions of net-snmp so far, but 5.9 for reasons I have failed to
figure out is different in some way.  Nothing in the changelogs or diff'ing
the header files have pointed me in the right direction.  I don't think
switching to linked_list is the right thing to do since that might make it
quite a bit slower.

Does anyone have any idea where I should have a look to try and narrow down
where the data structure is ending up wrong when using table_container (aka
binary_array)?

Thanks.

-- 
Len

Re: [*Newsletter*] SNMPv3 informs behavior when destination is unreachable

[Pushpa T. <pus...@gm...>]

Hi All,

Kindly confirm whether snmpv3 Inform should be sent out till response
received from NMS.  Kindly provide RFC reference.

Regards,
Pushpa.T


On Tue, Aug 6, 2024 at 8:02 PM Pushpa Thimmaiah <pus...@gm...>
wrote:

> Hi Mostafa,
>
> Thank you for response.
> I have given  information  that SNMPv3 inform should be sent out until it
> will get response from NMS.  I didnot not get much information about SNMPv3
> Informs in RFC3414. Could you please share RFC that has information about
> SNMPv3 inform.
>
> Thanks,
> Pushpa.T
>
> On Tue, Aug 6, 2024 at 5:41 PM Mostafa Kassem <mos...@da...>
> wrote:
>
>> Until it exhausts the number of retries and then it gives up (that is why
>> there is timeout period and retry value), but not until it gets a reply.
>>
>> Mostafa
>> ------------------------------
>> *From:* Pushpa Thimmaiah <pus...@gm...>
>> *Sent:* Tuesday, August 6, 2024 12:41 AM
>> *To:* Net-SNMP Coders <net...@li...>
>> *Subject:* [*Newsletter*] SNMPv3 informs behavior when destination is
>> unreachable
>>
>> CAUTION: This email originated from outside of the organization. Do not
>> click links or open attachments unless you recognize the sender and know
>> the content is safe.
>>
>> Hi All,
>>
>> As per my knowledge,  Whenever trap-destination is unreachable snmpv3
>> informs retries upto default retry i.e 5 (if not defined) and in default
>> timeout.
>> Kindly let me know if this is correct.
>> Eg:
>> snmptrap -Ci -v 3 -r 4 -t 1 -n "" -a SHA -A test12345 -x AES -X
>> test123456 -l authPriv -u traptest  172.16.1.131 69 .1.3.6.1.4.1.8072.2.3.1
>> .1.3.6.1.4.1.8072.2.1.1 i 11
>> Here, timeout=1sec retry=4 , NMS=172.16.1.131(down)
>> Does it send snmpv3 informs until it gets response from
>> NMS/trap-destination
>>
>>
>> Thanks,
>> Pushpa.T
>>
>

Re: [*Newsletter*] SNMPv3 informs behavior when destination is unreachable

[Pushpa T. <pus...@gm...>]

Hi Mostafa,

Thank you for response.
I have given  information  that SNMPv3 inform should be sent out until it
will get response from NMS.  I didnot not get much information about SNMPv3
Informs in RFC3414. Could you please share RFC that has information about
SNMPv3 inform.

Thanks,
Pushpa.T

On Tue, Aug 6, 2024 at 5:41 PM Mostafa Kassem <mos...@da...>
wrote:

> Until it exhausts the number of retries and then it gives up (that is why
> there is timeout period and retry value), but not until it gets a reply.
>
> Mostafa
> ------------------------------
> *From:* Pushpa Thimmaiah <pus...@gm...>
> *Sent:* Tuesday, August 6, 2024 12:41 AM
> *To:* Net-SNMP Coders <net...@li...>
> *Subject:* [*Newsletter*] SNMPv3 informs behavior when destination is
> unreachable
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
> Hi All,
>
> As per my knowledge,  Whenever trap-destination is unreachable snmpv3
> informs retries upto default retry i.e 5 (if not defined) and in default
> timeout.
> Kindly let me know if this is correct.
> Eg:
> snmptrap -Ci -v 3 -r 4 -t 1 -n "" -a SHA -A test12345 -x AES -X test123456
> -l authPriv -u traptest  172.16.1.131 69 .1.3.6.1.4.1.8072.2.3.1
> .1.3.6.1.4.1.8072.2.1.1 i 11
> Here, timeout=1sec retry=4 , NMS=172.16.1.131(down)
> Does it send snmpv3 informs until it gets response from
> NMS/trap-destination
>
>
> Thanks,
> Pushpa.T
>

SNMPv3 informs behavior when destination is unreachable

[Pushpa T. <pus...@gm...>]

Hi All,

As per my knowledge,  Whenever trap-destination is unreachable snmpv3
informs retries upto default retry i.e 5 (if not defined) and in default
timeout.
Kindly let me know if this is correct.
Eg:
snmptrap -Ci -v 3 -r 4 -t 1 -n "" -a SHA -A test12345 -x AES -X test123456
-l authPriv -u traptest  172.16.1.131 69 .1.3.6.1.4.1.8072.2.3.1
.1.3.6.1.4.1.8072.2.1.1 i 11
Here, timeout=1sec retry=4 , NMS=172.16.1.131(down)
Does it send snmpv3 informs until it gets response from
NMS/trap-destination


Thanks,
Pushpa.T

Re: libnetsnmpagent.so.35: cannot open shared object file: No such file or directory

[Bart V. A. <bva...@ac...>]

On 7/30/24 11:46 AM, Niels Baggesen wrote:
> You probably need to rerun ldconfig after doing the install.

Since the Net-SNMP library path is passed to the linker with the
linker option -rpath, is it really necessary to run ldconfig after
having installed Net-SNMP? See also commit 3857d43233d4 from April
2000.

Thanks,

Bart.

RE: libnetsnmpagent.so.35: cannot open shared object file: No such file or directory

[Peter M. <pma...@ac...>]

It installed into /usr/local/bin

I ran "sudo ldconfig" and it still outputs the same error for command "/usr/sbin/snmpd":

“/usr/sbin/snmpd: error while loading shared libraries: libnetsnmp.so.35: cannot open shared object file: No such file or directory”

inside the /usr/local/lib directory are symbolic link files "libnetsnmpagent.so.40", "libnetsnmpmibs.so.40", and "libnetsnmp.so.40"

A solution I tried was to make symbolic links inside the /usr/local/lib for the respective libnetsnmpagent.so.35 that link to their respective .so.40 links

I reran "sudo ldconfig" afterwards

I then ran the command "/usr/sbin/snmpd" and the following error occurred

"/usr/sbin/snmpd: symbol lookup error: /usr/sbin/snmpd: undefined symbol: smux_listen_sd"





-----Original Message-----
From: Niels Baggesen <ni...@ba...> 
Sent: Tuesday, July 30, 2024 2:46 PM
To: net...@li...
Subject: Re: libnetsnmpagent.so.35: cannot open shared object file: No such file or directory

Using the defaults, I would expect it to install into /usr/local/{sbin,bin} ?

You probably need to rerun ldconfig after doing the install.

/Niels

Den 30-07-2024 kl. 16:03 skrev Peter Majdalani:
> Hi,
> 
> I am currently trying to get net-snmp to work on my Ubuntu 20.04.6 
> Linux machine.
> 
> I have downloaded net-snmp 5.9.4
> I ran ./configure with all default settings I ran `make`, no errors 
> occurred I then ran `sudo make install` as root, no errors occurred
> 
> I have the following user settings in the snmpd.conf:
> `rouser linuser priv
>    createUser linuser SHA linuserpass DES linprivpass
> 
>    rw user linadmin priv
>    rw user linadmin SHA linauthpass DES linprivpass`
> 
> When I run the following command:
> 
> `snmpwalk -v 3 -u linuser -l authPriv -a SHA -A linuserpass -x DES -X 
> linprivpass localhost`
> 
> It outputs:
> “snmpwalk: Timeout”
> 
> When I run the following command:
> `/usr/sbin/snmpd`
> 
> It outputs:
> “/usr/sbin/snmpd: error while loading shared libraries: 
> libnetsnmp.so.35: cannot open shared object file: No such file or directory”
> 
> If and when I run the following command:
> `ldd /usr/sbin/snmpd`
> 
> It outputs the following:
> “linux-vdso.so.1 (0x00007ffec37ad000)
> libnetsnmpagent.so.35 => not found
> libnetsnmpmibs.so.35 => not found
> libnetsnmp.so.35 => not found
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f34d86f000) 
> /lib64/ld-linux-x86_64.so.2”
> 
> Any ideas on how to fix this?
> 
> 
> 
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

--
Niels Baggesen -- @home -- Århus -- Denmark -- ni...@ba... The purpose of computing is insight, not numbers  --  R W Hamming




_______________________________________________
Net-snmp-coders mailing list
Net...@li...
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders