[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Monit default port for protocol testes

From: Jan-Henrik Haukeland
Subject: Re: Monit default port for protocol testes
Date: Wed, 8 Nov 2006 18:38:03 +0100

If I understood the original poster correct he need the client port number, i.e. the ephemeral port assigned to monit and then need to change the packet sent to the SIP server and insert this info(!). For this to work you must write your own SIP protocol test for monit and use getsockname(2) to get the local port number. I don't think we should set the local port number explicit which can give us problems, such as "address already in use" errors.

On 8. nov. 2006, at 16.57, Martin Pala wrote:

There is currently no support for setting the client source port of the network test (you can set just the target port) => kernel will choose dynamicaly from the pool.

To support this feature, it will be needed to implement optional specific bind on the source port, which probably should be quite easy.

Possible syntax for example (to check the server/target port 5000 with client/outgoing port 10000):

 check host myhost with address
   if failed port 5000 with sourceport 10000 then alert


Jose Silva wrote:
Hi I'm doing some testing to see if I can use monit to test a SIP
server at the protocol level.
But I haven't found what is the default port for the monit client or
if I can force a default port, or if I can have acess by some form to
the port monit is using.
I need this port because for the SIP protocol it is necessary to
insert this info on some of it's headers, this so the response can
come back to the port that request went out from.
Is this possible or any idea how I can do this?
Thanks in advance

To unsubscribe:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]