This page documents the experience of implementing [[SNMP]] over [[DTLS]] as described by documents being developed for the [[ISMS]] working group.  A large section of this is relevant only to SNMP developers (Net-SNMP or otherwise) and some of this is relevant to anyone who is implementing a DTLS solution using [[OpenSSL]].  In particular, there are a number of tricks that need to be employed to make [[OpenSSL]] properly handle multiple clients. The implementation and this document were done by [[User:Wes|Wes Hardaker]]

This page documents the experience of implementing [[SNMP]] over [[DTLS]] as described by documents being developed for the [[ISMS]] working group.  A large section of this is relevant only to SNMP developers (Net-SNMP or otherwise) and some of this is relevant to anyone who is implementing a DTLS solution using [[OpenSSL]].  In particular, there are a number of tricks that need to be employed to make an [[OpenSSL]] based DTLS server properly handle multiple clients.

 

(The Net-SNMP DTLS implementation and this document were done by [[User:Wes|Wes Hardaker]])

== Net-SNMP Background ==

== Net-SNMP Background ==

Net-SNMP implements the [[transport|transports]] over which SNMP messages can be sent using a pluggable architecture.  This architecture defines hooks that allow implemented transports to handle opening, sending and receiving packets through "something or other".

Net-SNMP implements the [[transport|transports]] over which SNMP messages can be sent using a pluggable architecture.  This architecture defines hooks that allow implemented transports to handle opening, sending and receiving packets through "something or other".  The "something or other" can be pretty much anything and Net-SNMP has support for IPv4/UDP, IPv6/TCP, UnixDomain Sockets, IPX, and internal pipe()s to name just a few of the diverse examples.