Looking for advice on TCP/IP socket identification.

[Jason Alexander]

We’re doing TCP/IP connectivity for most of our threads and want to implement IP checking for our servers.

Does anyone have experience with any kind of solution which can reliably check the IP address of the host connecting to a server process before any other action is taken.  We’re not partial to any specific solution (PDL, TCP, etc.) but want a solution which is internal to the Cloverleaf engine.

(We are aware of host-based firewall options but have some issues with that solution and so are looking for potential configuration/software solutions in the Cloverleaf engine.)

Topic

[Jim Kosloskey]

Jason,

As far as I know on current releases all one can do is recognize the IP address of a client AFTER the connection has been made.

You probably could then close the connection and email/page someone but whoever connected has sent a message and that will be lost. That system might have simply made a mistake and would like to know about it.

I think a request has been made to add the ability to reject connections based on IP Address. However, usually that is the reason one employs a firewall which has more capability than is likely to be deployed in something like Cloverleaf.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Charlie Bursell]

Jason:

You can do this easily with Multi-Server.  Read up on it in the docs.

Charlie

[Author]

Replies