Hi, It then seems that the only solution for supporting informs in a "firewalled" system, is to use a fixed port (or range of ports) as the source port for the sent informs, so that the returned acknowledgements can be accepted (by adding rule to the firewall, accpeting the pre-defined UDP port).
Can you give a pointer to where to do that in net-snmp's code? I guess it's somewhere in the UDP transport f_send function... Oh, I'm assuming that there would be no problem that a few sessions would use the same UDP port to receive the ACKs, and that net-snmp uses the SNMP message ID to correlate the ACK to the inform. thanks, Erez. -----Original Message----- From: Wes Hardaker [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 12:37 AM To: Makavy, Erez (Erez) Cc: [email protected] Subject: Re: Disabling engineID Probe for Informs >>>>> "EM" == Erez Makavy <Makavy> writes: EM> Before an inform is sent, an automatic engineID probe is sent to the EM> manager-station, because of the firewall blocking unknown incoming EM> UDP port, the probe response is not received, and the inform is not EM> sent. I actually thought it was possible to specify the engineID already (but I didn't actually double check) so the probe wouldn't happen. Note: since an inform *requires* a response in the first place, you'll have a similar issue with the firewall blocking the inform response and you should consider using "traps" instead which don't solicit a response from the manager. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
