Ramu, Nmap's snmp-sysdescr script currently uses a 5-second timeout and attempts only once to send the SNMPv1 request. We agree that this could be improved to provide better reliability. I will investigate further and respond again with specific suggestions.
Dan On Wed, Oct 30, 2024 at 7:09 AM Ramu Burra <ramu.bu...@ivanti.com> wrote: > Hi NAMP team, > > A gentle reminder… > > Could you please answer below at your earliest convenience. > > > > Regards, > > Ramu B. > > > > *From:* Ramu Burra > *Sent:* 28 October 2024 20:36 > *To:* Daniel Miller <dmil...@nmap.com>; dev@nmap.org; supp...@nmap.com > *Cc:* Viral Shah <viral.s...@ivanti.com>; Krishnakanth Kambaladinne < > krishnakanth.kambaladi...@ivanti.com>; Ashok Kumar Jena < > ashokkumar.j...@ivanti.com>; Haresh Narwani <haresh.narw...@ivanti.com> > *Subject:* Regarding NMAP Retrigger for snmp-sysdescr > > > > Hi Daniel & NMAP team, > > > > I hope this email finds you well. > > > > I'm writing to inquire about the specific behaviour of Nmap's > SNMP-SYSDescr query in situations where the target device responds > intermittently. > > > > I'm particularly interested in knowing if there are any specific > configuration options or techniques that can be employed to increase the > likelihood of successful SNMP-SYSDescr queries, especially when dealing > with unreliable network conditions or slow-responding devices. > > > > Any insights or recommendations would be greatly appreciated. > > > > Thank you for your time and consideration. > > > > Regards, > > Ramu B >
_______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at https://seclists.org/nmap-dev/
