IDS 10.00.UC8 on AIX 5.3

Comparing "netstat" output on AIX and Linux, it's clear that whether
dynamic or static ports are used is platform dependent. I need to help
someone apply QOS rules on a WAN link, which they can't do without
specifying the port numbers. Is there a way to force them to be
static?

Regards,
Doug Lawry

I don't think so.

Art

Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art (AT) iiug (DOT) org)

Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.



On Thu, Sep 16, 2010 at 8:26 AM, Doug Lawry <lawry (AT) nildram (DOT) co.uk> wrote:

On Sep 16, 5:26*am, Doug Lawry <la... (AT) nildram (DOT) co.uk> wrote:
Can you clarify what you mean by IDS using static destination TCP port
numbers?

IDS will listen for connections on a well known (because advertised
via sqlhosts) port number.

When a CSDK client connects, it will be using an ephemeral port on its
system to connect to the well known port.
The overall connection has, as I understand, the unique source address/
port and target address/port consisting of <client IP address>/<client
ephemeral port>, <IDS IP address>/<IDS listener port> which is present
in the TCP/IP headers after the connection is established.

What different behaviour are you seeking?

Thanks,

Jonathan Leffler

Hi Jonathan.

Thanks for picking this up. If you have access to an AIX system
running IDS and run "netstat -a", you will see what I mean: the port
number on the target system is presumably used only for the initial
connection, after which the TCP traffic is moved to another port, so
you can't identify it by looking for the IDS listerner port number or
service name any longer.

Regards,
Doug