Re: SNMP Informs sent from snmpd do not work if firewall is enabled on the machine

snmptrapd (version 5.3) does respond back from port 162 itself. So
even the following rules work fine for me:

-A INPUT -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT
-A OUTPUT -o eth0 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT

This is good, since I do not know have to rely on the IP or port
information of the trap receiver.

But, does the SNMP standard specify that the reply should be sent from
port 162 (which MG-Soft is not following) ? Or is the SNMP
implementation free to decide on which port should be used for the
response packet?

-Datta.

On Fri, Jun 17, 2011 at 9:59 AM, Dattaram Porob
<[email protected]> wrote:
> I am using MG-SOFT MIB Browser and it is replying back on a random
> port; will try with snmptrapd and let you know.
>
> -Datta.
>
> On Wed, Jun 15, 2011 at 9:13 PM, Dave Shield <[email protected]> wrote:
>> On 15 June 2011 15:05, Dattaram Porob <[email protected]> wrote:
>>> Even if we do assume that the receivers are listening on 162, the
>>> rules about specifying source port as 162 will not work because the
>>> ack for the Inform request is sent by the receiver from a random port
>>> again (and not 162) :(.
>>
>> What software are you using to receive the notifications?
>> If snmptrapd, then what version?
>>
>> 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