TECTED] On
Behalf Of Dave Shield
Sent: Tuesday, February 27, 2007 1:28 AM
To: Makavy, Erez (Erez)
Cc: Wes Hardaker; [email protected]
Subject: Re: Disabling engineID Probe for Informs
On 26/02/07, Makavy, Erez (Erez) <[EMAIL PROTECTED]> wrote:
> It then seems that th
On 26/02/07, Makavy, Erez (Erez) <[EMAIL PROTECTED]> 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 outgoin
Makavy, Erez (Erez) wrote:
> 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 fire
---Original Message-
From: Makavy, Erez (Erez)
Sent: Monday, February 26, 2007 6:55 PM
To: 'Wes Hardaker'
Cc: [email protected]
Subject: RE: Disabling engineID Probe for Informs
Hi,
It then seems that the only solution for supporting informs in a
"firewalled"
es 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 In
> "EM" == Erez Makavy writes:
EM> Before an inform is sent, an automatic engineID probe is sent to the
EM> manager-station,
EM> because of the firewall blocking unknown incoming UDP port,
EM> the probe response is not received, and the inform is not sent.
I actually thought it was possible
Hi,
Problem:
-
Sending Informs (using the snmpNotificationMIB, and snmpTargetMIB) does
not work when firewall is active.
[Version: Net-Snmp-5.3.1, Linux , PPC]
Analysis:
-
Before an inform is sent, an automatic engineID probe is sent to the
manager-station,
because of
