Re: Disabling engineID Probe for Informs

2007-02-26 Thread Dave Shield
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

Re: Disabling engineID Probe for Informs

2007-02-26 Thread Andrew Hood
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

RE: Disabling engineID Probe for Informs

2007-02-26 Thread Makavy, Erez (Erez)
Hi, Looking into it a bit futher, maybe a good place to set a fixed source port would be in get_target_sessions(). What if I set the thissess->localname to my agent's IP address and the thissess->local_port to my specified port (32800 for example)? thanks, Erez. -Original Message

RE: Disabling engineID Probe for Informs

2007-02-26 Thread Makavy, Erez (Erez)
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).