01-04-2010
How to know which application is connecting to a remote host
From a host A an application is trying to connect to host B.
From firewall side I can see packets dropped coming from host A to host B.
I've access to host A: how can I know which "application" is trying to connect to host B?
Thanks,
Marco
Last edited by marcopb; 01-04-2010 at 09:35 AM..
Reason: mistyping
10 More Discussions You Might Find Interesting
1. Solaris
Hi all,
i am copying .gz files from production server to development server using
"scp" command.my requirement is after copying .gz files i want to delete old
.gz files(two days back) in development server from production server.
like this way i need to delelte .log ,.z and .dmp files... (3 Replies)
Discussion started by: krishna176
3 Replies
2. Shell Programming and Scripting
I want to write a script which would run from one host say A and connect to other remote host B and then run rest of commands in that host. I tried connecting from A host to B with SSH but after connecting to host B it just getting me inside Host B command prompt. Rest of the script is not running... (6 Replies)
Discussion started by: SN2009
6 Replies
3. Shell Programming and Scripting
Gurus/Experts
We have a centralized UNIX/Solaris server from where we can actually ssh to all other UNIX/Solaris servers...I need to write a script that reside on this centerlized server and do FileSystem monitoring (basically run df -h or -k) of other remote servers and then send an email to me... (6 Replies)
Discussion started by: anjum.suri
6 Replies
4. UNIX for Advanced & Expert Users
Suppose host B does not allow public/private key authentication - only secureID authentication. I already have a master ssh connection from host A to host B. Host A does allow public/private key authentication. Is there any way to connect from host C to host B by way of the master ssh connection... (2 Replies)
Discussion started by: cpp6f
2 Replies
5. UNIX for Advanced & Expert Users
I do a ssh to remote host(A1) from local host(L1). I then ssh to another remote(A2) from A1.
When I do a who -m from A2, I see the "connected from" as "A1".
=> who -m
userid pts/2 2010-03-27 08:47 (A1)
I want to identify who is the local host who initiated the connection to... (3 Replies)
Discussion started by: gomes1333
3 Replies
6. Solaris
Hi All,
I want to print a privacy statement for e.g. "Users must be authorized to login into this host" .... of this kind of message when the users tries to connect to a Solaris host. i.e. before the user key's in credentials.
Is there any command that i can use to print this kind of... (1 Reply)
Discussion started by: sudharma
1 Replies
7. Shell Programming and Scripting
Checking crontab job entry in 3 different hosts Hi Gurus,
I am trying to connect to remote host from current host to check crontab entries. I have started like this
ssh -n -l db2psp 205.191.156.17 ". ~/.profile >/dev/null 2>/dev/null; cd log ;ls | wc -l"
I got this error ?
ssh:... (1 Reply)
Discussion started by: rocking77
1 Replies
8. Shell Programming and Scripting
Hi,
Given addresses of 2 remote machines, using a shell script is it possible to
get the state of running processes in "src"
stop all the processes in "src"
exit out of "src"
ssh into "dest"
resume the state of executing processes captured in step 1 in "dest"
Assumption:
"src" is... (3 Replies)
Discussion started by: Saeya Darsan
3 Replies
9. UNIX for Dummies Questions & Answers
I was wondering why does ssh store the fingerprints of remote host when connecting for the first time?
I will appreciate a detailed response, can't figure it out. (2 Replies)
Discussion started by: ChiefGandalf
2 Replies
10. Shell Programming and Scripting
Geeks,
Could you please help me out in my script and identify the missing piece. I need to check/get the exit status of a remote command executed on remote host through script and send out an email when process/processes is/are not running on any/all server(s).
Here's the complete... (5 Replies)
Discussion started by: lovesaikrishna
5 Replies
LEARN ABOUT MOJAVE
curlopt_connect_to
CURLOPT_CONNECT_TO(3) curl_easy_setopt options CURLOPT_CONNECT_TO(3)
NAME
CURLOPT_CONNECT_TO - Connect to a specific host and port instead of the URL's host and port
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_CONNECT_TO,
struct curl_slist *connect_to);
DESCRIPTION
Pass a pointer to a linked list of strings with "connect to" information to use for establishing network connections with this handle. The
linked list should be a fully valid list of struct curl_slist structs properly filled in. Use curl_slist_append(3) to create the list and
curl_slist_free_all(3) to clean up an entire list.
Each single string should be written using the format HOST:PORT:CONNECT-TO-HOST:CONNECT-TO-PORT where HOST is the host of the request, PORT
is the port of the request, CONNECT-TO-HOST is the host name to connect to, and CONNECT-TO-PORT is the port to connect to.
The first string that matches the request's host and port is used.
Dotted numerical IP addresses are supported for HOST and CONNECT-TO-HOST. A numerical IPv6 address must be written within [brackets].
Any of the four values may be empty. When the HOST or PORT is empty, the host or port will always match (the request's host or port is
ignored). When CONNECT-TO-HOST or CONNECT-TO-PORT is empty, the "connect to" feature will be disabled for the host or port, and the
request's host or port will be used to establish the network connection.
This option is suitable to direct the request at a specific server, e.g. at a specific cluster node in a cluster of servers.
The "connect to" host and port are only used to establish the network connection. They do NOT affect the host and port that are used for
TLS/SSL (e.g. SNI, certificate verification) or for the application protocols.
In contrast to CURLOPT_RESOLVE(3), the option CURLOPT_CONNECT_TO(3) does not pre-populate the DNS cache and therefore it does not affect
future transfers of other easy handles that have been added to the same multi handle.
The "connect to" host and port are ignored if they are equal to the host and the port in the request URL, because connecting to the host
and the port in the request URL is the default behavior.
If an HTTP proxy is used for a request having a special "connect to" host or port, and the "connect to" host or port differs from the
requests's host and port, the HTTP proxy is automatically switched to tunnel mode for this specific request. This is necessary because it
is not possible to connect to a specific host or port in normal (non-tunnel) mode.
When this option is passed to curl_easy_setopt(3), libcurl will not copy the entire list so you must keep it around until you no longer use
this handle for a transfer before you call curl_slist_free_all(3) on the list.
DEFAULT
NULL
PROTOCOLS
All
EXAMPLE
CURL *curl;
struct curl_slist *connect_to = NULL;
connect_to = curl_slist_append(NULL, "example.com::server1.example.com:");
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_CONNECT_TO, connect_to);
curl_easy_setopt(curl, CURLOPT_URL, "http://example.com");
curl_easy_perform(curl);
/* always cleanup */
curl_easy_cleanup(curl);
}
curl_slist_free_all(connect_to);
AVAILABILITY
Added in 7.49.0
RETURN VALUE
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
SEE ALSO
CURLOPT_URL(3), CURLOPT_RESOLVE(3), CURLOPT_FOLLOWLOCATION(3), CURLOPT_HTTPPROXYTUNNEL(3),
libcurl 7.54.0 May 20, 2016 CURLOPT_CONNECT_TO(3)