The curl telnet support is basic and very easy to use. Curl passes all data passed to it on stdin to the remote server. Connect to a remote telnet server using a command line similar to: curl telnet://remote.server.com And enter the data to pass to the server on stdin. The result will be sent to stdout or to the file you specify with -o. Method 2: curl -v telnet://: By using above two methods, we can easily check the listening status of port from source server to destination server. Also please make sure that source server IP/host name is able to ping in the target server before performing above methods. Curl, netcat, telnet. You can easily upload your files to our service using a Unix/Linux command-line interface. We allow HTTP PUT for curl -T and some TCP ports for uploads using netcat/telnet. All the ports described below are available via our Tor hidden service as well - oshiatwowvdbshka.onion. Using curl (PUT method).
You can monitor, test, and troubleshoot network problems such as firewall and connection issues from your Unified Access Gateway instance with various tools and commands such as tcpdump and curl.
Install and Run tcpdump
tcpdump is a command-line tool that you can use to analyze TCP packets for troubleshooting and testing purposes.
If you have not installed tcpdump on your Unified Access Gateway instance, run the following command from the command-line to install tcpdump:
/etc/vmware/gss-support/install.sh
The following examples show tcpdump usage:
Run the following commands to monitor traffic over specific ports.
Note: If you specify port 8443, ensure that UDP 8443 is not blocked by an outer firewall.- tcpdump -i eth0 -n -v udp port 8443
- tcpdump -i eth0 -n -v tcp port 8443
- tcpdump -i any -n -v port 22443
Run the following commands to trace the packets that are coming to and from the RADIUS server to Unified Access Gateway:
Run the following commands to trace the packets that are coming to and from the RSA SecurID server to Unified Access Gateway.
Using the curl command
You can also use the curl command to retrieve information about network connections.
Run the following command to test the connection to a back end connection server or a web server:
curl -v -k https://<hostname-or-ip-address>:443/
You can view the back end server connection issues in the esmanager.log file:You cannot test connections to back end virtual desktops such as PCoIP 4172 and Blast 22443 using tcpdump as the desktops do not listen on these port numbers until a session is ready. See the logs to look at possible connection failures on these ports.
Run the following command for Horizon Framework Channel TCP connection:
curl -v telnet://<virtualdesktop-ip-address>:32111
Run the following command for Horizon MMR/CDR TCP connection:
curl -v telnet://<virtualdesktop-ip-address>:9427
- Run the following command to test port connectivity from Unified Access Gateway to the virtual desktop. Ensure that the session to the virtual desktop is active before running this command.
curl -v telnet://<virtualdesktop-ip-address>:22443
PowerShell Commands
Curl Telnet Close Connection
Run the following commands from the PowerShell command-line to monitor connectivity for specific ports:
- Test-NetConnection <uag-hostname-or-ip-address> -port 443
- Test-NetConnection <uag-hostname-or-ip-address> -port 8443
- Test-NetConnection <uag-hostname-or-ip-address> -port 4172
- This message:[ Message body ] [ More options ]
- Related messages:[ Next message ][ Previous message ][ Next in thread ] [ Replies ]
Date: Tue, 20 Dec 2005 12:19:09 +0100
hi
curl allows telnet functionnality
syntax is curl telnet://<remote>
curl doesn t manage the user password, and it is to user to catch the
prompt and send the user identification.
why?
interest of curl is i think a complete protocal connect management from
just a command line, as it does for http, ftp,.
with telnet, this advantage is not implemented, and a simple script
including telnet command seems to do the same
i have done some test, and can t find a solution , from a script
including curl telnet, to pass automaticaly the user/id to continue the
telnet connexion
Flat package editor mac download.
so should be possible to have an improvement of telnet in curl including
the management of user identificatin while connection (even if it is
not in the protocol and can t be treated directly)
as
curl telnet://<remote> -u <user/pass>
curl will do the telnet connexion, will cath the return prompt, send the
user/id , test the results, etc , to return finaly the command result
it should be nice for me, because i should have a telnet command
inheriting of curl benefits( (proxy management, ..)
in it is not, how can i from a shell script including curl telnet
syntax, provide the user/id in continue
thanks for an answer
Received on 2005-12-20
Curl Telnet With Proxy
- This message: [ Message body ]
- Next message: Samuel Díaz García: 'Re: curl and telnet'
- Previous message: Philippe Baudry: 'Philippe.Baudry@evidian.com'
- Next in thread: Samuel Díaz García: 'Re: curl and telnet'
- Reply: Samuel Díaz García: 'Re: curl and telnet'
- Reply: Daniel Stenberg: 'Re: curl and telnet'
- Reply: Jake Peavy: 'Re: curl and telnet'
Curl Telnet Https
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]