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

Re: Net-SNMP 5.9.4.rc1 available for final testing

[Wes H. <har...@us...>]

Alexander Bergmann <abe...@su...> writes:

> Hi Craig,
> 
> Thanks for the reply. Any update on your search for the GPG signing
> key?

Sorry fro the delay.  I just put a new file in:

https://sourceforge.net/projects/net-snmp/files/net-snmp-admin%20PGP%20key/current-key/

Specifically, the net-snmp-admins-2023-to-2033.asc file is the one you
need.

[and yes I published it to key servers a while ago too]
-- 
Wes Hardaker
Please mail all replies to net...@li...

Re: Inquiry about FIPS Certification for net-snmp's Crypto Module

[Wes H. <har...@us...>]

MOUHOUNE Samir <sam...@gm...> writes:

> I am writing to inquire whether your crypto module is FIPS
> certified.

Hi Samir,

We do not have FIPS certification for the net-snmp source-code, nor are
there any plans to do so.

Having said that, one of the motivations behind the "internal" option
that can be passed to the --with-openssl flag for configure is that the
version we included supposedly is FIPS certificate, which may meet your
requirements.  It is, unfortunately, an older version of openssl and
given its age, it may be wise for organizations to instead try to link
against a different openssl that has received certification instead.
-- 
Wes Hardaker
Please mail all replies to net...@li...

Inquiry about FIPS Certification for net-snmp's Crypto Module

[MOUHOUNE S. <sam...@gm...>]

Dear net-snmp team,

I am writing to inquire whether your crypto module is FIPS certified. If
yes, could you please provide me with the certificate number? Otherwise, I
would like to know if you have any plans to certify your Crypto module
according to the Federal Information Processing Standards (FIPS). If so, I
would also like to know the current stage of the certification process and
if you have an estimated timeline for obtaining the certification.

FIPS certification is globally recognized for information system security
and ensures that cryptographic modules meet rigorous standards. Considering
FIPS certification for your Crypto module would be a significant step
towards enhancing users' trust in your software.

I truly appreciate the efforts you have already made to maintain the
quality and security of net-snmp. I am confident that achieving FIPS
certification would further strengthen the reputation of your project.

Thank you in advance for your response and attention to this request. If
you need any further information or have any updates regarding FIPS
certification, I would be delighted to receive them.

Best regards,

-- 

*Cordialement,*
*Samir MOUHOUNE*

Re: Net-SNMP 5.9.4.rc1 available for final testing

[Alexander B. <abe...@su...>]

Hi Craig,

Thanks for the reply. Any update on your search for the GPG signing key?

I know that this is a minor problem, but we try to keep the code
signature validation in place as good as we can.


Thanks,
Alex~

On Wed, Jul 12, 2023 at 07:20:56PM +1000, Craig Small wrote:
> I asked the same thing a few weeks ago. Wes said he put the key on the mit
> servers. I haven't checked that (or rc1 either).
> 
> Both are on my to-do list.
> 
>  - Craig
> 
> 
> On Wed, 12 July 2023, 19:12 Alexander Bergmann via Net-snmp-coders, <
> net...@li...> wrote:
> 
> > Hi Wes / everyone,
> >
> > Where can I find the current GPG signing key that was used to sign the
> > latest updates?
> >
> > gpg: assuming signed data in 'net-snmp-5.9.4.rc1.tar.gz'
> > gpg: Signature made Thu 22 Jun 2023 05:15:02 PM CEST
> > gpg:                using EDDSA key
> > 6E6718AEF1EB5C65C32D1B2A356BC0B552D53CAB
> > gpg: Can't check signature: No public key
> >
> > I was only able to locate some old keys on SourceForge:
> >
> > files/net-snmp-admin PGP key/current-key/
> >
> >  net-snmp-admins-2014.asc       2011-06-03
> >  net-snmp-admin-keys.asc        2006-01-18
> >
> > I've also opened an issue on github.com:
> >
> > https://github.com/net-snmp/net-snmp/issues/595
> >
> >
> > Thanks in advance,
> > Alex~
> >
> > On Thu, Jun 22, 2023 at 08:31:02AM -0700, Wes Hardaker via Net-snmp-coders
> > wrote:
> > >
> > > It seems like the V5-9-4 branch has finally quieted down a bit.  Thank
> > > you to all the people that have submitted patches, fixes, bug reports,
> > > etc in the last month.  It's time, however, to really get this out the
> > > door.  As such, I've published 5.9.4.rc1 and is available for testing:
> > >
> > >
> > https://sourceforge.net/projects/net-snmp/files/net-snmp/5.9.4-pre-releases/
> > >
> > > As a reminder, all patches from here out to the V5-9 branch must have
> > > discussion on -coders first, with at least 3 people in favor of applying
> > > them.  Additionally, any code changes will likely cause another rc
> > > candidate to appear instead of the real release as well.  So make them
> > > count :-)
> > >
> > > The one exception to this: I'd love some help adding to the NEWS file.
> > > It's rather bland at the moment and doesn't reflect the hard work that
> > > has gone into this release by everyone.  Feel free to add NEWS blips
> > > without multi-person reviews.
> > >
> > > --
> > > Wes Hardaker
> > > Please mail all replies to net...@li...
> > >
> > >
> > > _______________________________________________
> > > Net-snmp-coders mailing list
> > > Net...@li...
> > > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
> >
> > --
> > Alexander Bergmann <abe...@su...>
> > Security Engineer, GPG: E30A 65A4 0F50 0066 B2B5  F614 DE54 E875 9FFA 4886
> > SUSE Software Solutions Germany GmbH
> > Maxfeldstr. 5, 90409 Nuremberg, Germany
> > (HRB 36809, AG Nürnberg)
> > Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew
> > McDonald, Boudien Moerman
> > _______________________________________________
> > Net-snmp-coders mailing list
> > Net...@li...
> > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
> >

-- 
Alexander Bergmann <abe...@su...>
Security Engineer, GPG: E30A 65A4 0F50 0066 B2B5  F614 DE54 E875 9FFA 4886
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nuernberg, Germany
Managing Director/Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich
(HRB 36809, AG Nürnberg)

Re: Net-SNMP 5.9.4.rc1 available for final testing

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

I asked the same thing a few weeks ago. Wes said he put the key on the mit
servers. I haven't checked that (or rc1 either).

Both are on my to-do list.

 - Craig


On Wed, 12 July 2023, 19:12 Alexander Bergmann via Net-snmp-coders, <
net...@li...> wrote:

> Hi Wes / everyone,
>
> Where can I find the current GPG signing key that was used to sign the
> latest updates?
>
> gpg: assuming signed data in 'net-snmp-5.9.4.rc1.tar.gz'
> gpg: Signature made Thu 22 Jun 2023 05:15:02 PM CEST
> gpg:                using EDDSA key
> 6E6718AEF1EB5C65C32D1B2A356BC0B552D53CAB
> gpg: Can't check signature: No public key
>
> I was only able to locate some old keys on SourceForge:
>
> files/net-snmp-admin PGP key/current-key/
>
>  net-snmp-admins-2014.asc       2011-06-03
>  net-snmp-admin-keys.asc        2006-01-18
>
> I've also opened an issue on github.com:
>
> https://github.com/net-snmp/net-snmp/issues/595
>
>
> Thanks in advance,
> Alex~
>
> On Thu, Jun 22, 2023 at 08:31:02AM -0700, Wes Hardaker via Net-snmp-coders
> wrote:
> >
> > It seems like the V5-9-4 branch has finally quieted down a bit.  Thank
> > you to all the people that have submitted patches, fixes, bug reports,
> > etc in the last month.  It's time, however, to really get this out the
> > door.  As such, I've published 5.9.4.rc1 and is available for testing:
> >
> >
> https://sourceforge.net/projects/net-snmp/files/net-snmp/5.9.4-pre-releases/
> >
> > As a reminder, all patches from here out to the V5-9 branch must have
> > discussion on -coders first, with at least 3 people in favor of applying
> > them.  Additionally, any code changes will likely cause another rc
> > candidate to appear instead of the real release as well.  So make them
> > count :-)
> >
> > The one exception to this: I'd love some help adding to the NEWS file.
> > It's rather bland at the moment and doesn't reflect the hard work that
> > has gone into this release by everyone.  Feel free to add NEWS blips
> > without multi-person reviews.
> >
> > --
> > Wes Hardaker
> > Please mail all replies to net...@li...
> >
> >
> > _______________________________________________
> > Net-snmp-coders mailing list
> > Net...@li...
> > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>
> --
> Alexander Bergmann <abe...@su...>
> Security Engineer, GPG: E30A 65A4 0F50 0066 B2B5  F614 DE54 E875 9FFA 4886
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nuremberg, Germany
> (HRB 36809, AG Nürnberg)
> Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew
> McDonald, Boudien Moerman
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>

Re: Net-SNMP 5.9.4.rc1 available for final testing

[Alexander B. <abe...@su...>]

Hi Wes / everyone,

Where can I find the current GPG signing key that was used to sign the
latest updates?

gpg: assuming signed data in 'net-snmp-5.9.4.rc1.tar.gz'
gpg: Signature made Thu 22 Jun 2023 05:15:02 PM CEST
gpg:                using EDDSA key 6E6718AEF1EB5C65C32D1B2A356BC0B552D53CAB
gpg: Can't check signature: No public key

I was only able to locate some old keys on SourceForge:

files/net-snmp-admin PGP key/current-key/

 net-snmp-admins-2014.asc       2011-06-03
 net-snmp-admin-keys.asc        2006-01-18

I've also opened an issue on github.com:

https://github.com/net-snmp/net-snmp/issues/595


Thanks in advance,
Alex~

On Thu, Jun 22, 2023 at 08:31:02AM -0700, Wes Hardaker via Net-snmp-coders wrote:
> 
> It seems like the V5-9-4 branch has finally quieted down a bit.  Thank
> you to all the people that have submitted patches, fixes, bug reports,
> etc in the last month.  It's time, however, to really get this out the
> door.  As such, I've published 5.9.4.rc1 and is available for testing:
> 
> https://sourceforge.net/projects/net-snmp/files/net-snmp/5.9.4-pre-releases/
> 
> As a reminder, all patches from here out to the V5-9 branch must have
> discussion on -coders first, with at least 3 people in favor of applying
> them.  Additionally, any code changes will likely cause another rc
> candidate to appear instead of the real release as well.  So make them
> count :-)
> 
> The one exception to this: I'd love some help adding to the NEWS file.
> It's rather bland at the moment and doesn't reflect the hard work that
> has gone into this release by everyone.  Feel free to add NEWS blips
> without multi-person reviews.
> 
> -- 
> Wes Hardaker
> Please mail all replies to net...@li...
> 
> 
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

-- 
Alexander Bergmann <abe...@su...>
Security Engineer, GPG: E30A 65A4 0F50 0066 B2B5  F614 DE54 E875 9FFA 4886
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nuremberg, Germany
(HRB 36809, AG Nürnberg)
Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman

timeout and retry for snmptrap

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

Hi,

I am using tool 'snmptrap'  to send informs .   I would like to know
default timeout and retry here.
  snmpcmd manpage says default timeout=1sec  and retry=5.
Could you confirm whether it is applicable to command 'snmptrap -Ci' ?

Regards,
Pushpa.T

Is there a similar VRF patch in version 5.9

[Vic L. (刘威)-浪. <liu...@ie...>]

hi：
I'm using SNMPD version 5.9 and I had an issue with VRF and then saw this
patch 《#1376 Linux VRF》.So, I was wondering if there was a patch like this
<linux-vrf-5.8.0.patch> in snmpd 5.9. 
If so, could you please provide it to me, thank you.

 

Net-SNMP 5.9.4.rc1 available for final testing

[Wes H. <har...@us...>]

It seems like the V5-9-4 branch has finally quieted down a bit.  Thank
you to all the people that have submitted patches, fixes, bug reports,
etc in the last month.  It's time, however, to really get this out the
door.  As such, I've published 5.9.4.rc1 and is available for testing:

https://sourceforge.net/projects/net-snmp/files/net-snmp/5.9.4-pre-releases/

As a reminder, all patches from here out to the V5-9 branch must have
discussion on -coders first, with at least 3 people in favor of applying
them.  Additionally, any code changes will likely cause another rc
candidate to appear instead of the real release as well.  So make them
count :-)

The one exception to this: I'd love some help adding to the NEWS file.
It's rather bland at the moment and doesn't reflect the hard work that
has gone into this release by everyone.  Feel free to add NEWS blips
without multi-person reviews.

-- 
Wes Hardaker
Please mail all replies to net...@li...

Re: snmp inform

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

Hi Kuldeep,

Thank you.
Unfortunately, I didnot capture packets, but there was engineID missing on
SNMP manager during the test.  I fixed that and noticed no snmpinforms
then.   So checked at snmp-agent side and noticed that snmptrap is stuck.
Does 'snmptrap'  not timeout if there is no engineID in response from
SNMP-manager?

*System details:*
net-snmp :  5.7.1
Kernel      : 4.1.22-ltsi
machine   : arm
OS           : linux


Thank you,
Pushpa.T

On Mon, Jun 19, 2023 at 3:54 PM Kuldeep Patidar <kul...@gm...>
wrote:

> Hello pushpa ..
>
> Thank you for providing the additional information. From the given
> details, it seems that the issue is occurring within the `main()` function
> of the `snmptrap.c` file.
>
> Based on the provided local variables, it appears that the SNMP session is
> configured correctly, including the SNMP version, community string, and
> security parameters. The session has the correct peername set to
> "192.168.18.69," indicating that the destination IP is reachable.
>
> Since the manager IP being unreachable results in a timeout, it is
> possible that there is a network connectivity issue or a problem with the
> SNMP server configuration. However, since you have confirmed that the IP is
> reachable, we can explore other potential causes.
>
> Here are a few suggestions to further investigate the issue:
>
> 1. Verify the response from the SNMP server: Check the SNMP server logs or
> enable debugging on the server side to see if it is receiving the SNMP
> inform request and generating a response. This can help determine if the
> issue lies with the server's handling of the inform requests.
>
> 2. Capture network traffic: Use network monitoring tools (e.g., Wireshark)
> to capture the network traffic between the device running the `snmptrap`
> command and the SNMP server. Analyze the captured packets to ensure that
> the inform request is being sent correctly and that the server is
> responding.
>
> 3. Check for firewall or security restrictions: Ensure that there are no
> firewall rules or security restrictions on either the device running the
> `snmptrap` command or the SNMP server that might be blocking or interfering
> with the SNMP inform packets.
>
> 4. Monitor system resources: Monitor the system resources (CPU, memory,
> disk) on the device running the `snmptrap` command to ensure that it is not
> overwhelmed or experiencing resource constraints that could cause the
> command to hang.
>
> 5. Test with a different SNMP manager: Try sending the SNMP inform to a
> different SNMP manager or tool to see if the issue persists. This can help
> determine if the problem is specific to the SNMP server or if it occurs
> with other managers as well.
>
> 6. Review SNMP library or command versions: Check if there are any known
> issues or bugs related to the SNMP library or the `snmptrap` command
> version you are using. Consider updating to the latest version or trying an
> alternative SNMP library or command implementation.
>
> If none of the above steps resolve the issue, it might be necessary to
> engage the support channels of the SNMP library or the SNMP server vendor
> for further assistance. They can provide more specific guidance and help
> troubleshoot the problem in-depth.
>
> Remember to provide them with the relevant details, such as the SNMP
> library version, operating system, and any error messages or log entries
> associated with the issue.
>
> Thanks
> Kukdeep Paridar
>
> On Mon, 19 Jun 2023, 3:36 pm Pushpa Thimmaiah, <pus...@gm...>
> wrote:
>
>> Hi Kuldeep,
>>
>> Thanks a lot for quick response.  I did check them, it was working fine
>> and   turned into this state at  some point time.
>>   GDB shows  all input args from snmptrap is correct.  IP is reachable.
>>   I have noticed when manager IP unreachable then it would time out with
>> error:snmpInform: Timeout.
>>
>>
>> ----------------------------------------------------------------------------------------------------------------------------------------------
>> (gdb) frame 3
>> #3  0x00011e00 in main (argc=19, argv=0x0) at snmptrap.c:377    <-----
>> snmp_synch_response() called in this function
>> (gdb) info locals
>> session = {version = 3, retries = 1, timeout = 2000000, flags = 256,
>> subsession = 0x0, next = 0x0, peername = 0x7ed46f05 "192.168.18.69",
>>   remote_port = 0, localname = 0x0, local_port = 0, authenticator = 0x0,
>> callback = 0x12658 <snmp_input>, callback_magic = 0x0, s_errno = 0,
>>   s_snmp_errno = 0, sessid = 0, community = 0x7ed4672c "public",
>> community_len = 6, rcvMsgMaxSize = 1472, sndMsgMaxSize = 0,
>>   isAuthoritative = 0 '\000', contextEngineID = 0x0, contextEngineIDLen =
>> 0, engineBoots = 0, engineTime = 0, contextName = 0x0,
>>   contextNameLen = 0, securityEngineID = 0x0, securityEngineIDLen = 0, securityName
>> = 0x29588 "v3", securityNameLen = 2,
>>   securityAuthProto = 0x76f34384 <usmHMACMD5AuthProtocol>,
>> securityAuthProtoLen = 10,
>>   securityAuthKey = "\274\363\267\031\034\toI\\\331\376\070th\234\345",
>> '\000' <repeats 15 times>, securityAuthKeyLen = 16,
>>   securityAuthLocalKey = 0x0, securityAuthLocalKeyLen = 0,
>> securityPrivProto = 0x0, securityPrivProtoLen = 0,
>>   securityPrivKey = '\000' <repeats 31 times>, securityPrivKeyLen = 0,
>> securityPrivLocalKey = 0x0, securityPrivLocalKeyLen = 0,
>>   securityModel = -1, securityLevel = 2, paramName = 0x0, securityInfo =
>> 0x0, transport_configuration = 0x0, myvoid = 0x0}
>> ss = 0x2310c
>> pdu = 0x2c3e8
>> response = 0x7ed465c0
>> pdu_in_addr_t = <optimized out>
>>
>> On Mon, Jun 19, 2023 at 3:16 PM Kuldeep Patidar <
>> kul...@gm...> wrote:
>>
>>> Hello ..
>>>
>>> From the provided information, it appears that the `snmptrap` command is
>>> getting stuck in the `snmp_synch_response_cb()` function in the
>>> `snmp_client.c` file. The `state->waiting` flag is set to 1, indicating
>>> that it is waiting for a response.
>>>
>>> To troubleshoot this issue, you can follow these steps:
>>>
>>> 1. Check the SNMP configuration: Ensure that the SNMP configuration on
>>> the device is correct, including the SNMP version, community string, and
>>> authentication settings.
>>>
>>> 2. Verify SNMP server availability: Confirm that the SNMP server is
>>> running and reachable from the device where you are executing the
>>> `snmptrap` command. You can use tools like `snmpwalk` or `snmpget` to check
>>> the SNMP connectivity and retrieve SNMP data from the server.
>>>
>>> 3. Confirm SNMPv3 settings: Since you mentioned using SNMPv3 informs,
>>> verify that the SNMPv3 settings, such as security parameters (username,
>>> authentication protocol, privacy protocol) and context name, are correctly
>>> configured on both the sending and receiving ends.
>>>
>>> 4. Check network connectivity: Ensure that there are no network
>>> connectivity issues between the device and the SNMP server. Verify that the
>>> required ports (typically UDP 161 and 162) are open and accessible.
>>>
>>> 5. Review SNMP timeout and retries: Although you mentioned that the
>>> timeout is set to 2 seconds with 2 retries, it's worth confirming if these
>>> settings are appropriate for your environment. You may consider increasing
>>> the timeout value or adjusting the number of retries to see if it affects
>>> the behavior.
>>>
>>> 6. Debug SNMP agent/server: Enable SNMP debugging or logging on the
>>> receiving SNMP server to gather more information about the incoming
>>> `snmptrap` requests. This can help identify any issues on the server side.
>>>
>>> 7. Update SNMP libraries: If you're using third-party SNMP libraries,
>>> make sure they are up to date. There might be known issues or bug fixes in
>>> newer versions that could resolve the problem.
>>>
>>> 8. Consult vendor documentation or support: If the issue persists, it
>>> may be beneficial to consult the documentation or reach out to the vendor's
>>> support team for assistance. They can provide specific troubleshooting
>>> steps or insights related to their SNMP implementation.
>>>
>>> It's important to note that without additional context or access to the
>>> system, it can be challenging to pinpoint the exact cause of the issue.
>>> Therefore, the above suggestions should help you investigate and resolve
>>> the problem.
>>>
>>> Thanks
>>> Kuldeep patidar
>>>
>>>
>>>
>>> On Mon, 19 Jun 2023, 3:13 pm Pushpa Thimmaiah, <
>>> pus...@gm...> wrote:
>>>
>>>>
>>>> Hi Folks,
>>>>
>>>> I am using 'snmptrap -Ci ' to send snmpv3 informs .   Noticed scenario
>>>> on one device where snmptrap command stuck and gdb shows that flow stuck
>>>> in snmp_synch_response_cb() .  File snmp_client.c,  flag state->waiting
>>>> set to 1.
>>>> Kindly guide .
>>>> According to my knowledge, snmpinform will timeout after given period.
>>>> Here timeout is 2 seconds and retry 2.
>>>>
>>>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>>  bt
>>>> #0  0x76e2e850 in select () at ../sysdeps/unix/syscall-template.S:84
>>>> #1  0x76eddb68 in snmp_synch_response_cb (ss=0x2c288, ss@entry=0x2310c,
>>>> pdu=pdu@entry=0x2c3e8, response=0x7ebd5558,
>>>>     response@entry=0x7ebd5550, pcb=<optimized out>) at
>>>> snmp_client.c:1060
>>>> #2  0x76eddc40 in snmp_synch_response (ss=ss@entry=0x2310c,
>>>> pdu=pdu@entry=0x2c3e8, response=response@entry=0x7ebd5550) at
>>>> snmp_client.c:1108
>>>> (gdb) frame 1
>>>> #1  0x76eddb68 in snmp_synch_response_cb (ss=0x2c288, ss@entry=0x2310c,
>>>> pdu=pdu@entry=0x2c3e8, response=0x7ebd5558,
>>>>     response@entry=0x7ebd5550, pcb=<optimized out>) at
>>>> snmp_client.c:1060
>>>> 1060 in snmp_client.c
>>>> (gdb) info locals
>>>> lstate = {waiting = 1, status = 1, reqid = 82488738, pdu = 0x0}
>>>> state = 0x7ebd5450
>>>> cbsav = 0x0
>>>> cbmagsav = 0x1
>>>> numfds = 5
>>>> count = <optimized out>
>>>> fdset = {fds_bits = {16, 0 <repeats 31 times>}}
>>>> timeout = {tv_sec = 0, tv_usec = 0}
>>>> tvp = 0x0
>>>> block = 1
>>>> (gdb) frame 2
>>>> #2  0x76eddc40 in snmp_synch_response (ss=ss@entry=0x2310c,
>>>> pdu=pdu@entry=0x2c3e8, response=response@entry=0x7ebd5550) at
>>>> snmp_client.c:1108
>>>> 1108 snmp_client.c: No such file or directory.
>>>> (gdb) info locals
>>>> No locals.
>>>> (gdb)
>>>> (gdb) frame 0
>>>> #0  0x76e2e850 in select () at ../sysdeps/unix/syscall-template.S:84
>>>> 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
>>>> (gdb) info locals
>>>> No locals.
>>>> (gdb)
>>>>
>>>> ------------------------------------------------------------------------------------------------------
>>>>
>>>> Thanks,
>>>> Pushpa.T
>>>> _______________________________________________
>>>> Net-snmp-coders mailing list
>>>> Net...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>>>>
>>>

Re: snmp inform

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

Hi Kuldeep,

Thanks a lot for quick response.  I did check them, it was working fine
and   turned into this state at  some point time.
  GDB shows  all input args from snmptrap is correct.  IP is reachable.
  I have noticed when manager IP unreachable then it would time out with
error:snmpInform: Timeout.

----------------------------------------------------------------------------------------------------------------------------------------------
(gdb) frame 3
#3  0x00011e00 in main (argc=19, argv=0x0) at snmptrap.c:377    <-----
snmp_synch_response() called in this function
(gdb) info locals
session = {version = 3, retries = 1, timeout = 2000000, flags = 256,
subsession = 0x0, next = 0x0, peername = 0x7ed46f05 "192.168.18.69",
  remote_port = 0, localname = 0x0, local_port = 0, authenticator = 0x0,
callback = 0x12658 <snmp_input>, callback_magic = 0x0, s_errno = 0,
  s_snmp_errno = 0, sessid = 0, community = 0x7ed4672c "public",
community_len = 6, rcvMsgMaxSize = 1472, sndMsgMaxSize = 0,
  isAuthoritative = 0 '\000', contextEngineID = 0x0, contextEngineIDLen =
0, engineBoots = 0, engineTime = 0, contextName = 0x0,
  contextNameLen = 0, securityEngineID = 0x0, securityEngineIDLen = 0,
securityName
= 0x29588 "v3", securityNameLen = 2,
  securityAuthProto = 0x76f34384 <usmHMACMD5AuthProtocol>,
securityAuthProtoLen = 10,
  securityAuthKey = "\274\363\267\031\034\toI\\\331\376\070th\234\345",
'\000' <repeats 15 times>, securityAuthKeyLen = 16,
  securityAuthLocalKey = 0x0, securityAuthLocalKeyLen = 0,
securityPrivProto = 0x0, securityPrivProtoLen = 0,
  securityPrivKey = '\000' <repeats 31 times>, securityPrivKeyLen = 0,
securityPrivLocalKey = 0x0, securityPrivLocalKeyLen = 0,
  securityModel = -1, securityLevel = 2, paramName = 0x0, securityInfo =
0x0, transport_configuration = 0x0, myvoid = 0x0}
ss = 0x2310c
pdu = 0x2c3e8
response = 0x7ed465c0
pdu_in_addr_t = <optimized out>

On Mon, Jun 19, 2023 at 3:16 PM Kuldeep Patidar <kul...@gm...>
wrote:

> Hello ..
>
> From the provided information, it appears that the `snmptrap` command is
> getting stuck in the `snmp_synch_response_cb()` function in the
> `snmp_client.c` file. The `state->waiting` flag is set to 1, indicating
> that it is waiting for a response.
>
> To troubleshoot this issue, you can follow these steps:
>
> 1. Check the SNMP configuration: Ensure that the SNMP configuration on the
> device is correct, including the SNMP version, community string, and
> authentication settings.
>
> 2. Verify SNMP server availability: Confirm that the SNMP server is
> running and reachable from the device where you are executing the
> `snmptrap` command. You can use tools like `snmpwalk` or `snmpget` to check
> the SNMP connectivity and retrieve SNMP data from the server.
>
> 3. Confirm SNMPv3 settings: Since you mentioned using SNMPv3 informs,
> verify that the SNMPv3 settings, such as security parameters (username,
> authentication protocol, privacy protocol) and context name, are correctly
> configured on both the sending and receiving ends.
>
> 4. Check network connectivity: Ensure that there are no network
> connectivity issues between the device and the SNMP server. Verify that the
> required ports (typically UDP 161 and 162) are open and accessible.
>
> 5. Review SNMP timeout and retries: Although you mentioned that the
> timeout is set to 2 seconds with 2 retries, it's worth confirming if these
> settings are appropriate for your environment. You may consider increasing
> the timeout value or adjusting the number of retries to see if it affects
> the behavior.
>
> 6. Debug SNMP agent/server: Enable SNMP debugging or logging on the
> receiving SNMP server to gather more information about the incoming
> `snmptrap` requests. This can help identify any issues on the server side.
>
> 7. Update SNMP libraries: If you're using third-party SNMP libraries, make
> sure they are up to date. There might be known issues or bug fixes in newer
> versions that could resolve the problem.
>
> 8. Consult vendor documentation or support: If the issue persists, it may
> be beneficial to consult the documentation or reach out to the vendor's
> support team for assistance. They can provide specific troubleshooting
> steps or insights related to their SNMP implementation.
>
> It's important to note that without additional context or access to the
> system, it can be challenging to pinpoint the exact cause of the issue.
> Therefore, the above suggestions should help you investigate and resolve
> the problem.
>
> Thanks
> Kuldeep patidar
>
>
>
> On Mon, 19 Jun 2023, 3:13 pm Pushpa Thimmaiah, <pus...@gm...>
> wrote:
>
>>
>> Hi Folks,
>>
>> I am using 'snmptrap -Ci ' to send snmpv3 informs .   Noticed scenario on
>> one device where snmptrap command stuck and gdb shows that flow stuck
>> in snmp_synch_response_cb() .  File snmp_client.c,  flag state->waiting
>> set to 1.
>> Kindly guide .
>> According to my knowledge, snmpinform will timeout after given period.
>> Here timeout is 2 seconds and retry 2.
>>
>> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>  bt
>> #0  0x76e2e850 in select () at ../sysdeps/unix/syscall-template.S:84
>> #1  0x76eddb68 in snmp_synch_response_cb (ss=0x2c288, ss@entry=0x2310c,
>> pdu=pdu@entry=0x2c3e8, response=0x7ebd5558,
>>     response@entry=0x7ebd5550, pcb=<optimized out>) at snmp_client.c:1060
>> #2  0x76eddc40 in snmp_synch_response (ss=ss@entry=0x2310c, pdu=pdu@entry=0x2c3e8,
>> response=response@entry=0x7ebd5550) at snmp_client.c:1108
>> (gdb) frame 1
>> #1  0x76eddb68 in snmp_synch_response_cb (ss=0x2c288, ss@entry=0x2310c,
>> pdu=pdu@entry=0x2c3e8, response=0x7ebd5558,
>>     response@entry=0x7ebd5550, pcb=<optimized out>) at snmp_client.c:1060
>> 1060 in snmp_client.c
>> (gdb) info locals
>> lstate = {waiting = 1, status = 1, reqid = 82488738, pdu = 0x0}
>> state = 0x7ebd5450
>> cbsav = 0x0
>> cbmagsav = 0x1
>> numfds = 5
>> count = <optimized out>
>> fdset = {fds_bits = {16, 0 <repeats 31 times>}}
>> timeout = {tv_sec = 0, tv_usec = 0}
>> tvp = 0x0
>> block = 1
>> (gdb) frame 2
>> #2  0x76eddc40 in snmp_synch_response (ss=ss@entry=0x2310c, pdu=pdu@entry=0x2c3e8,
>> response=response@entry=0x7ebd5550) at snmp_client.c:1108
>> 1108 snmp_client.c: No such file or directory.
>> (gdb) info locals
>> No locals.
>> (gdb)
>> (gdb) frame 0
>> #0  0x76e2e850 in select () at ../sysdeps/unix/syscall-template.S:84
>> 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
>> (gdb) info locals
>> No locals.
>> (gdb)
>>
>> ------------------------------------------------------------------------------------------------------
>>
>> Thanks,
>> Pushpa.T
>> _______________________________________________
>> Net-snmp-coders mailing list
>> Net...@li...
>> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>>
>

snmp inform

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

Hi Folks,

I am using 'snmptrap -Ci ' to send snmpv3 informs .   Noticed scenario on
one device where snmptrap command stuck and gdb shows that flow stuck
in snmp_synch_response_cb() .  File snmp_client.c,  flag state->waiting set
to 1.
Kindly guide .
According to my knowledge, snmpinform will timeout after given period.
Here timeout is 2 seconds and retry 2.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 bt
#0  0x76e2e850 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x76eddb68 in snmp_synch_response_cb (ss=0x2c288, ss@entry=0x2310c,
pdu=pdu@entry=0x2c3e8, response=0x7ebd5558,
    response@entry=0x7ebd5550, pcb=<optimized out>) at snmp_client.c:1060
#2  0x76eddc40 in snmp_synch_response (ss=ss@entry=0x2310c,
pdu=pdu@entry=0x2c3e8,
response=response@entry=0x7ebd5550) at snmp_client.c:1108
(gdb) frame 1
#1  0x76eddb68 in snmp_synch_response_cb (ss=0x2c288, ss@entry=0x2310c,
pdu=pdu@entry=0x2c3e8, response=0x7ebd5558,
    response@entry=0x7ebd5550, pcb=<optimized out>) at snmp_client.c:1060
1060 in snmp_client.c
(gdb) info locals
lstate = {waiting = 1, status = 1, reqid = 82488738, pdu = 0x0}
state = 0x7ebd5450
cbsav = 0x0
cbmagsav = 0x1
numfds = 5
count = <optimized out>
fdset = {fds_bits = {16, 0 <repeats 31 times>}}
timeout = {tv_sec = 0, tv_usec = 0}
tvp = 0x0
block = 1
(gdb) frame 2
#2  0x76eddc40 in snmp_synch_response (ss=ss@entry=0x2310c,
pdu=pdu@entry=0x2c3e8,
response=response@entry=0x7ebd5550) at snmp_client.c:1108
1108 snmp_client.c: No such file or directory.
(gdb) info locals
No locals.
(gdb)
(gdb) frame 0
#0  0x76e2e850 in select () at ../sysdeps/unix/syscall-template.S:84
84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
(gdb) info locals
No locals.
(gdb)
------------------------------------------------------------------------------------------------------

Thanks,
Pushpa.T

Re: snmptrap v3 authentication

[Wes H. <we...@ne...>]

Niels Baggesen <ni...@ba...> writes:

> > I tried with SimpleMib browser as well as MGSOFT Mib browser.
> 
> In that case you should direct your question towards them, why they
> accept a trap with unknown credentials.

Indeed, some trap receivers always accept and print traps regardless of
whether or not it has been authenticated.  It's the responsibility of
the receiver to decide what to do.

[some have argued they should always log what they receive, but mark it
as whether it was authenticated or not]
-- 
Wes Hardaker
Please mail all replies to net...@li...

SIGHUP not re-reading the updated Engine-ID

[Abhishek S. <abh...@gm...>]

Hi All,

Updated engine-id is not being re-read after sending SIGHUP to snmpd.
I am performing a snmpwalk with '-e' engine-id. After changing the
engine-id and sending a SIGHUP to snmpd, I was expecting snmpwalk with the
previous engine-id to fail while snmpwalk with the updated engine-id to be
successful.
But snmpwalk with the previous engineid is successful and fails with the
updated one.

Now, after restarting snmpd, snmpwalk is successful with the updated
engine-id and fails with the previous (which is expected)

Please let me know if engine-id change needs mandatory restart of snmpd
daemon or is there any API/patch to solve this?

Thank You in advance,
Abhishek S

getNextRequest sending actual OID to module instead of the "next" OID

[Pyokkimies, Esa-P. <epy...@fo...>]

We have a problem with our MIB module when accessing it with snmpwalk and
doing iteration through the tree i.e. with getNextRequests.
When using direct access of OIDs with getRequest, everything works fine.

I have already debugged it quite a lot so I can give my idea of what
happens, but what I don't know is should it be fixed in snmpd or
our module.

We have fwCpuName table which SHOULD look like this with 2 cpus
fwCpuName.0 = STRING: Cpu(s)
fwCpuName.1 = STRING: cpu1
fwCpuName.2 = STRING: cpu2

Internally the function is simple, it just excepts that the index (0, 1, 2)
is available inside the function so we can fetch the cpu name with it.

The module expects that the index is passed in the netsnmp_table_request_info
struct as per net-snmp examples, and then accessed with
i = *(table_info->indexes->val.integer);

But this is not what happens when iterating the table with snmpwalk.
This is what happens:

snmpwalk -c public -v 1 192.168.206.172:161 SNMPv2-SMI::enterprises.47565.1.1.1.11.1.1.2
fwCpuName.0 = STRING: dummy
fwCpuName.1 = STRING: Cpu(s)
fwCpuName.2 = STRING: cpu1

So the net-snmp code call our module, but the table_info struct is wrong.
Here are some traces:

2023-05-03 19:38:51.777 syslog info: snmpd: table_helper_handler(): helpers/table.c, 243:
2023-05-03 19:38:51.777 syslog info: snmpd: helper:table:req:
2023-05-03 19:38:51.777 syslog info: snmpd: Got GETNEXT (161) mode request for handler table: base oid:
2023-05-03 19:38:51.777 syslog info: snmpd: SNMPv2-SMI::enterprises.47565.1.1.1.11.1
2023-05-03 19:38:51.777 syslog info: snmpd: SNMPv2-SMI::enterprises.47565.1.1.1.11.1.1.2

So here we get a getNextRequest for the cpu table, without the index as it should be, because we want the next from 11.1.1.2, i.e. 11.1.1.2.0.

2023-05-03 19:38:51.777 syslog info: snmpd: table_helper_handler(): helpers/table.c, 532:
2023-05-03 19:38:51.777 syslog info: snmpd: helper:table:
2023-05-03 19:38:51.777 syslog info: snmpd:     not enough for indexes

And here another trace where it says that the OID is not long enough for
indexes, which is correct. But since this is a getNextRequest, the code
should be able to figure out that the next OID in line is the .0 index, and
that should be passed to our module, but instead this happens:

2023-05-04 12:57:39.063 syslog info: snmpd: netsnmp_call_handler(): agent_handler.c, 542:
2023-05-04 12:57:39.063 syslog info: snmpd: handler:calling:
2023-05-04 12:57:39.063 syslog info: snmpd: calling handler fwCpuStatsTable for mode GET
2023-05-04 12:57:39.064 syslog info: snmpd: colnum=2 number_indexes=0 i=0 ti=0

So here it calls our handler fwCpuStatsTable for GET. The last line is
my own debug where the problem is that the table_info->number_indexes is zero.
So net-snmp didn't add the index zero to table_info and therefore we can't
fetch the correct string in our module.

Then net-snmp sends this out as UDP

2023-05-04 12:57:39.068 syslog info: snmpd: SNMPv2-SMI::enterprises.47565.1.1.1.11.1.1.2.0 = STRING: "dummy"

So here the OID is correct with the .0 in the end, but since the module was
called without the .0, the string remains as dummy.

Then the next request comes:

2023-05-04 12:57:39.080 syslog info: snmpd: Got GETNEXT (161) mode request for h
2023-05-04 12:57:39.080 syslog info: snmpd: SNMPv2-SMI::enterprises.47565.1.1.1.11.1.1.2.0

So this is the correct request since we want the next OID from the .0 i.e. .1.

But here it seems that again net-snmp sends the .0 index to our module instead
of .1

2023-05-04 12:57:39.082 syslog info: snmpd: colnum=2 number_indexes=1 i=0 index_oid_len=1 .0
2023-05-04 12:57:39.084 syslog info: snmpd: SNMPv2-SMI::enterprises.47565.1.1.1.11.1.1.2.1 = STRING: "Cpu(s)"

Here the number_indexes is 1 as is expected, but the integer is 0 (i=0) instead of 1. Then it outputs the .1 index as "Cpu(s)", which is wrong.

So as a summary the problem is that for GETNEXT requests, net-snmp
puts the actual OID index to table_info, instead of the NEXT.

Esa-Pekka

net-snmp-5.9.4.pre3 published for testing

[Wes H. <har...@us...>]

Version 5.9.4.pre3 has been released and published to:

https://sourceforge.net/projects/net-snmp/files/net-snmp/5.9.4-pre-releases/

Please test away and report any critical issues.  Ideally, this should
be the last pre-release and we'll publish a release candidate in a
couple of weeks if activity on publishing patches to this branch
appropriately declines.

-- 
Wes Hardaker
Please mail all replies to net...@li...

Re: snmptrap v3 authentication

[Niels B. <ni...@ba...>]

Den 25-04-2023 kl. 17:46 skrev Simon Chamlian:
> Something else.
>
> I tried with SimpleMib browser as well as MGSOFT Mib browser.

In that case you should direct your question towards them, why they 
accept a trap with unknown credentials.

Note, that you have asked to send the trap in the clear, so there is no 
problem interpreting it.

/Niels

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

Re: snmptrap v3 authentication

[Simon C. <sim...@mp...>]

Something else.

I tried with SimpleMib browser as well as MGSOFT Mib browser.




On Tue, Apr 25, 2023 at 10:30 AM Niels Baggesen via Net-snmp-coders <
net...@li...> wrote:

> Which trap receiver are you using? snmptrapd, or something else?
>
> /Niels
> Den 25-04-2023 kl. 15:10 skrev Simon Chamlian:
>
> I tried the command:
>
> snmptrap -v 3 -u  Simon  -a MD5 -A  SimonPass -l authNoPriv 172.27.37.227
> "" coldStart.0
>
> (with  security name  : Simon and   authentication password  : SimonPass ).
>
> These parameters are not set in any config files anywhere.
>
> On another PC with IP 172.27.37.227, I have a MIB browser and trap
> receiver. The trap receiver is receiving the trap even when it is not
> configured with the  security name  : Simon and   authentication password
> : SimonPass .
>
> I was not expecting to receive the trap until I configured the trap
> receiver with the same security name and authentication password!?!
>
> Simon
>
>
>
>
> On Tue, Apr 25, 2023 at 3:17 AM Craig Small via Net-snmp-coders <
> net...@li...> wrote:
>
>> On Sat, 15 Apr 2023 at 11:12, Simon Chamlian <sim...@mp...>
>> wrote:
>>
>>>
>>> snmptrap -v 3 -u  Simon  -a MD5 -A  SimonPass -l authNoPriv
>>> 172.27.37.227 "" coldStart.0
>>>
>>> I do receive the trap on my Trap Receiver even if I didn't specify a
>>> Username and Authentication password in the MIB browser (on 172.27.37.227 )
>>> !
>>>
>> Do you mean the security name instead of the username?
>> The -u sets the security name, -A sets the authentication password.
>> They're set in the example you gave.
>>
>> Or are you saying that you tried that command without the username and
>> authentication password?
>> If so, are you sure that you don't have those parameters set in an snmp
>> configuration file?
>>
>> Trying the command with -Dread_config:line may help here.
>>
>> I tried snmptrap 5.9.3 with no -u and -A flags and with/without a
>> configuration file and it only worked with the configuration file.
>>
>>  - Craig
>>
>> _______________________________________________
>> Net-snmp-coders mailing list
>> Net...@li...
>> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>>
>
>
> _______________________________________________
> Net-snmp-coders mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>
> --
> Niels Baggesen -- @home -- Århus -- Denmark -- nb...@us...
>    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
>

Re: snmptrap v3 authentication

[Niels B. <nb...@us...>]

Which trap receiver are you using? snmptrapd, or something else?

/Niels

Den 25-04-2023 kl. 15:10 skrev Simon Chamlian:
> I tried the command:
>
> snmptrap -v 3 -u  Simon  -a MD5 -A  SimonPass -l authNoPriv 
> 172.27.37.227 "" coldStart.0
>
> (with security name  : Simon and  authentication password  : SimonPass ).
>
> These parameters are not set in any config files anywhere.
>
> On another PC with IP 172.27.37.227, I have a MIB browser and trap 
> receiver. The trap receiver is receiving the trap even when it is not 
> configured with the security name  : Simon and  authentication 
> password  : SimonPass .
>
> I was not expecting to receive the trap until I configured the trap 
> receiver with the same security name and authentication password!?!
>
> Simon
>
>
>
>
> On Tue, Apr 25, 2023 at 3:17 AM Craig Small via Net-snmp-coders 
> <net...@li...> wrote:
>
>     On Sat, 15 Apr 2023 at 11:12, Simon Chamlian
>     <sim...@mp...> wrote:
>
>
>         snmptrap -v 3 -u  Simon  -a MD5 -A  SimonPass -l authNoPriv
>         172.27.37.227 "" coldStart.0
>
>         I do receive the trap on my Trap Receiver even if I didn't
>         specify a Username and Authentication password in the MIB
>         browser (on 172.27.37.227 ) !
>
>     Do you mean the security name instead of the username?
>     The -u sets the security name, -A sets the authentication
>     password. They're set in the example you gave.
>
>     Or are you saying that you tried that command without the username
>     and authentication password?
>     If so, are you sure that you don't have those parameters set in an
>     snmp configuration file?
>
>     Trying the command with -Dread_config:line may help here.
>
>     I tried snmptrap 5.9.3 with no -u and -A flags and with/without a
>     configuration file and it only worked with the configuration file.
>
>      - Craig
>
>     _______________________________________________
>     Net-snmp-coders mailing list
>     Net...@li...
>     https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>
>
>
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

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

Re: snmptrap v3 authentication

[Simon C. <sim...@mp...>]

I tried the command:

snmptrap -v 3 -u  Simon  -a MD5 -A  SimonPass -l authNoPriv 172.27.37.227
"" coldStart.0

(with  security name  : Simon and   authentication password  : SimonPass ).

These parameters are not set in any config files anywhere.

On another PC with IP 172.27.37.227, I have a MIB browser and trap
receiver. The trap receiver is receiving the trap even when it is not
configured with the  security name  : Simon and   authentication password
: SimonPass .

I was not expecting to receive the trap until I configured the trap
receiver with the same security name and authentication password!?!

Simon




On Tue, Apr 25, 2023 at 3:17 AM Craig Small via Net-snmp-coders <
net...@li...> wrote:

> On Sat, 15 Apr 2023 at 11:12, Simon Chamlian <sim...@mp...>
> wrote:
>
>>
>> snmptrap -v 3 -u  Simon  -a MD5 -A  SimonPass -l authNoPriv 172.27.37.227
>> "" coldStart.0
>>
>> I do receive the trap on my Trap Receiver even if I didn't specify a
>> Username and Authentication password in the MIB browser (on 172.27.37.227 )
>> !
>>
> Do you mean the security name instead of the username?
> The -u sets the security name, -A sets the authentication password.
> They're set in the example you gave.
>
> Or are you saying that you tried that command without the username and
> authentication password?
> If so, are you sure that you don't have those parameters set in an snmp
> configuration file?
>
> Trying the command with -Dread_config:line may help here.
>
> I tried snmptrap 5.9.3 with no -u and -A flags and with/without a
> configuration file and it only worked with the configuration file.
>
>  - Craig
>
> _______________________________________________
> Net-snmp-coders mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>

Re: snmptrap v3 authentication

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

On Sat, 15 Apr 2023 at 11:12, Simon Chamlian <sim...@mp...> wrote:

>
> snmptrap -v 3 -u  Simon  -a MD5 -A  SimonPass -l authNoPriv 172.27.37.227
> "" coldStart.0
>
> I do receive the trap on my Trap Receiver even if I didn't specify a
> Username and Authentication password in the MIB browser (on 172.27.37.227 )
> !
>
Do you mean the security name instead of the username?
The -u sets the security name, -A sets the authentication password. They're
set in the example you gave.

Or are you saying that you tried that command without the username and
authentication password?
If so, are you sure that you don't have those parameters set in an snmp
configuration file?

Trying the command with -Dread_config:line may help here.

I tried snmptrap 5.9.3 with no -u and -A flags and with/without a
configuration file and it only worked with the configuration file.

 - Craig

Fwd: snmptrap v3 authentication

[Simon C. <sim...@mp...>]

Hi,

The snmptrap v3 authentication does not seem to be working.

I am using Version:  5.9.1

>From my agent, I issue:

snmptrap -v 3 -u  Simon  -a MD5 -A  SimonPass -l authNoPriv 172.27.37.227
"" coldStart.0

I do receive the trap on my Trap Receiver even if I didn't specify a
Username and Authentication password in the MIB browser (on 172.27.37.227 )
!

I was NOT expecting to receive any traps until I set up the Username and
Authentication!?!

Any explanation?

Thanks,
S

Re: Timeout and Retry values for snmpinforms

[Wes H. <har...@us...>]

Pushpa Thimmaiah <pus...@gm...> writes:

> When snmpv2c/snmpv3 informs sent via 'snmptrap -Ci' command  and what should be
> ideal timeout and retry values to be considered

That's very network dependent.  I'd suggest a 1s timeout should be good
for most networks, as you should never be sending SNMP outside your
local network generally.  Retries depends on locally seen packet loss.
Probably something like 3-ish is about the right value even in most cases.
-- 
Wes Hardaker
Please mail all replies to net...@li...

Timeout and Retry values for snmpinforms

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

Hi ,

When snmpv2c/snmpv3 informs sent via 'snmptrap -Ci' command  and what
should be ideal timeout and retry values to be considered

Regards,
Pushpa.T

net-snmp 5.9.4.pre1 available for testing

[Wes H. <har...@us...>]

We've started the process of creating a 5.9.4 release.  Please test and
file pull requests when you run into problems you can fix.

tar/zips are available here:

https://sourceforge.net/projects/net-snmp/files/net-snmp/5.9.4-pre-releases/

-- 
Wes Hardaker
Please mail all replies to net...@li...