Re: SNMP Informs sent from snmpd do not work if firewall is enabled on the machine
Dave Shield <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 20 June 2011 08:36, Dattaram Porob <[email protected]> wrote: > > But, does the SNMP standard specify that the reply should be sent from > port 162 (which MG-Soft is not following) ? No. It just recommends (rather than requiring) that the trap receiver should *listen* on port 162. [RFC 3417, section 3.2] It doesn't say anything about the source port to be used for the response. > Or is the SNMP > implementation free to decide on which port should be used for the > response packet? As far as the SNMP specs are concerned, yes. It's left open. General good practise for network protocols (not specifically SNMP) dictates that responses should normally use the same socket-pair used for the original request, but I'm not aware of anything that states this explicitly. Most netowrk protocols are connection-based (i.e. TCP rather than UDP), so this would happen automatically. All I can suggest is that you put in a request to MG-Soft to adopt this behaviour. Dave ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users