RE: Disabling engineID Probe for Informs

This is a discussion on RE: Disabling engineID Probe for Informs within the SNMP Coders forums, part of the Networking and Network Related category; Hi, I'm trying to find a generic solution that would comply with standard 3rd party SNMP trap receivers (HP ...


Go Back   Usenet Forums > Networking and Network Related > SNMP Coders

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 05-07-2007
Makavy, Erez
 
Posts: n/a
Default RE: Disabling engineID Probe for Informs

Hi,

I'm trying to find a generic solution that would comply with standard
3rd party SNMP trap receivers (HP openview, MG-SOFT MIB Browser,...).

Currently the only solution I see is to have net-snmp send the informs
from constant ports, and open those UDP ports in the Firewall.

Regarding your suggestions:
1) It seems that allowing all UDP traffic from a certain IP address is
not secure enough for my needs.
2) The MG-SOFT MIB Browser I'm working with sends the inform ACKs from a
random port (not 162).



Erez.

-----Original Message-----
From: dave.shield@googlemail.com [mailto:dave.shield@googlemail.com] On
Behalf Of Dave Shield
Sent: Tuesday, February 27, 2007 1:28 AM
To: Makavy, Erez (Erez)
Cc: Wes Hardaker; net-snmp-coders@lists.sourceforge.net
Subject: Re: Disabling engineID Probe for Informs

On 26/02/07, Makavy, Erez (Erez) <makavy@avaya.com> wrote:
> 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,


For a TCP-based transport, this sort of response to an outgoing request
would presumably be recognised as relating to the
original (authorised) request, so would be allowed. I'm presuming
that the problem here arises because SNMP notifications are usually sent
over UDP, and the firewall can't automatically make the connection
between the two packets.

So one possible workaround might be to send the INFORM request over TCP
rather than UDP.

An alternative would be to configure the firewall to accept notification
responses based on the source address (i.e.
the notification receiver) rather than the destination (the agent).
That would naturally be a fixed UDP port (typically 162), so it would be
straightforward to configure the firewall accordingly.

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 10:54 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0