On Tue, 31 Oct 2017 15:17:05 +0100 chetan wrote:
C> Im using SNMP4j and Bouncy Castle DTLS implementation for
C> requesting and querying snmp messages over DTLS protocol towards
C> net SNMP Service running as Agent with configured SNMPv3 over
C> DTLS
C> 
C> During handshake, Bouncy is able to send Client hello, netSNMP
C> replies with helloverifyrequest, Bouncy would read the cookie
C> and add it to client hello and send it back to Agent, netSNMP
C> would verify the cookie and reply with *Server
C> hello, Certificate (fragment)..,Certificate Reqeuest and Server
C> Hello Done.* [image: Inline image 1]
C> Here these messages are grouped into one single clustered
C> message by netSNMP.
C> 
C> Because of which the Bouncy castle acting as Manager/Client is
C> only able to read Server hello message but not other messages
C> with it. Which is creating SocketTimeoutException and Bouncy is
C> sending new Client Hello messages.
C> 
C> So I want to know if the net SNMP service could be configured to
C> send the handshake messages individually like these
C> [image: Inline image 1]
C> 
C> 
C> ​Can we avoid clustering of messages sent by netSNMP service.

We are using OpenSSL for handling DTLS. I poked around a bit, and
found some similar reports:

https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/14561214/
http://openssl.6102.n7.nabble.com/Query-regarding-DTLS-handshake-td70421.html
https://github.com/openssl/openssl/issues/3251

I skimmed them and didn't see any obvious change we could make.
Have you tried building with different versions of OpenSSL?

Regards,
Robert

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to