In CMU and UCD SNMP I used to be able to open a session (with no peer
specified on the session structure) to get a socket opened and ready, and
then create PDU's with specific remote addresses on each.

In this way I could send and receive to multiple different remote hosts
over the same socket, with a minimum of overhead in allocated sessions and
so forth.

I see this has been replaced by some kind of transport abstraction layer,
which is good, but I can't for the life of me figure out how to set the
opaque transport_data field at PDU-create time to select different remote
addresses other than to just bodge it by hand...

I gather from a few places that you can use a copy of transport_data off a
PDU you receive - provided you get a packet from the peer to start with -
and put that on outgoing PDU's, which is a mechanism intended for replies.

How do you prime that pump with a peer you've never yet contacted?

-- 
Network Tools & Automation
Twitter, Inc.
------------------------------------------------------------------------------
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to