Sponsored Content
Top Forums Shell Programming and Scripting Telnet using port and execute cmd Post 302861121 by sea on Tuesday 8th of October 2013 07:06:12 AM
Old 10-08-2013
Something like this?
Code:
ip=127.0.0.1
port=47

telnet $ip $port<EOF
?
EOF

 

10 More Discussions You Might Find Interesting

1. Solaris

disabled telnet now need port 23 or port 22

we disabled telnet on solaris 9 via previous a thread. We use CMS (call management system) supervisor which used port 23 (telnet). We cannot use telnet via local directive and it was shut down as stated when we shut down telnet in the inetd file. I cannot now log into the CMS box since port 23 is... (3 Replies)
Discussion started by: panzerkw
3 Replies

2. Shell Programming and Scripting

telnet shell script on red hat 9 cmd line only

i would like to make a shell script (red hat 9 cmd line only) to telnet to my local isp's webmail server on port 25 and send it commands such as helo :) help would be much appreciated, and i found no posts similar that answered my question... the closest i've gotten to an answer from about 8... (3 Replies)
Discussion started by: kypeswith
3 Replies

3. AIX

Telnet to port

can some one help me ? what happens when we telnet to a port ? example telnet 192.168.0.xx 1234 where 1234 is a port number Thank you (5 Replies)
Discussion started by: anwesh
5 Replies

4. Cybersecurity

Can't telnet to port 25 on the host.

Hi, we have recently setup a new UNIX server with solaris 10 and I am having issue with with SMTP/sendmail. telnet localhost 25 --- works telnet hostname.domain.com 25 -- does not work. # telnet hostname.domain.com 25 Trying 10.122.1.111... telnet: Unable to connect to remote host:... (1 Reply)
Discussion started by: esmgr
1 Replies

5. Red Hat

telnet port 23

My linux version is 2.6.18-194.e14 (Oracle enterprise linux). Could you please tell me how to enable telnet on the server. When I try to connect the server through another pc using telnet it is throwing error. Connecting To <ip address>...Could not open connection to the host, on port 23.... (3 Replies)
Discussion started by: oradba_arun
3 Replies

6. UNIX for Dummies Questions & Answers

Unable to execute the complete cmd - using find command

Hi, I'm unable to execute the below command completely ; it's not allowing me to type the complete command. It is allowing till "xargs" and i cannot even press enter after that. I'm using Solaris. Let me know if anything needs to be added so as to execute the complete command. Appreciate... (12 Replies)
Discussion started by: venkatesht
12 Replies

7. Linux

How to execute nohup cmd

Hi, nohup sar -u 10 $COUNT | awk 'NR>2 {$2=$4=$7="";}1' | tr -s ' ' '\t' 2>/dev/null >sar.out & i have execute above line from shell script .. but sar.out is created with ZERO bite size.. Help on that what is the problem here Thx, Mani (0 Replies)
Discussion started by: Mani_apr08
0 Replies

8. IP Networking

telnet for port 5433 is not working while it works for port 22

Hi, I am trying to set up a dev environment and I have Ubuntu server (10.16.1.92) and a CentOS VM (10.16.3.235) on this. On the CentOS I have a program running on port 5433. Now my problem is that I am unable to telnet this port from another Windows server whereas I can telnet port 22 from... (5 Replies)
Discussion started by: rishav
5 Replies

9. Shell Programming and Scripting

Different cmd to execute and based on some pattern parse it and then store result in xlx format

Hi I have a different requirement, I need to run some application on my device from a file app_name.txt one by one which is like this: /usr/apps/email /usr/apps/message /usr/apps/settings after each app while it is running I need to execute again one cmd like ps -ef |grep... (2 Replies)
Discussion started by: Sanjeev Roy
2 Replies

10. Shell Programming and Scripting

Execute command using ssh server 'cmd'

Hi The command below does not work as it require to take command in the breakers But If I do so the variable values get lost ssh testserver01 'dsmc q b "${ARCHIVE_DIR}*" -sub=yes -querysummary -inactive -fromd="${BACKUP_DATE}"' Thank you. (3 Replies)
Discussion started by: zam
3 Replies
ipsec_policy(1M)														  ipsec_policy(1M)

NAME
ipsec_policy - HP-UX IPSec policy tester SYNOPSIS
src_ip_addr] dst_ip_addr] src_port] dst_port] DESCRIPTION
is a utility program that allows the HP-UX IPSec Administrator to query the active policy database to determine which host IPsec Policy will be used for an IP packet based on a packet descriptor, or 5-tuple, and the direction. The packet descriptor consists of a source IP address, source port number, destination IP address, destination port number, and network protocol. If the host policy uses dynamic key Security Associations, also displays the authentication record and IKE policy selected. If the authentication record contains two values for the IKE (KMP) version, uses the first value and selects the IKE policy according to this value. If the host policy uses a tunnel pol- icy, also displays the tunnel policy used. requires the optional HP-UX IPSec software. You must have superuser capabilities to run the utility. Command-Line Arguments recognizes the following command-line options and arguments: Specifies the source IP address (src_ip_addr) of the packet. If the direction is out, this is the local IP address. If the direction is in, this is the remote IP address. Acceptable values: An IPv4 address in dotted-decimal notation or an IPv6 address in colon-hexadecimal notation. Default: If you omit the source address and destination address uses the wildcard IPv4 address If you omit the source address but specify the destination address, uses the wildcard IPv4 address or wildcard IPv6 address according to the type of IP address you specify for the destination address. Specifies the source port number (src_port) of the packet. If the direction is out, this is the local port number. If the direction is in, this is the remote port number. Range: An unsigned integer in the range 1 - 65535. Default: Any port number(0). If you are making a query for an outbound client-server application where the source port number can be any user-space port, specify a "dummy" user-space port number for the source port, such as 65535. Specifies the destination IP address (dst_ip_addr) of the packet. If the direction is out, this is the remote IP address. If the direction is in, this is the local IP address. Acceptable values: An IPv4 address in dotted-decimal notation or an IPv6 address in colon-hexadecimal notation. Default: If you omit the source address and destination address uses the wildcard IPv4 address If you omit the destination address but specify the source address, uses the wildcard IPv4 address or wildcard IPv6 address according to the type of IP address you specify for the source address. Specifies the destination port number (dst_port) of the packet. If the direction is out, this is the remote port number. If the direction is in, this is the local port number. Range: An unsigned integer in the range 1 - 65535. Default: If omitted, any port number is assumed. If you are making a query for an inbound client-server application where the client port number can be any user-space port, specify a "dummy" user-space port number for the destination (server) port such as 65535. Specifies the network_protocol of the packet. Acceptable values: (Mobile IPv6 Mobility Header), or Default: Any network protocol(0). Specifies the direction for the packet specification. Acceptable values: or Default: RETURN VALUE
Upon successful completion, returns 0; otherwise it returns 1. ERRORS
fails if any of the following conditions is encountered: o Command used incorrectly - Usage message is returned. o HP-UX IPSec subsystem is not running - returns the following message: EXAMPLES
IPv4 Example On system A you want to determine which host IPsec policy will be used for outbound telnet traffic to system B or when local users telnet to system B. Since the telnet clients on system A will use any unused user-space TCP port and the telnet daemons on system B will use TCP port 23, you could use the following command: On system A you want to determine which host IPsec policy will be used for inbound telnet traffic from system B or when users on system B telnet to the local system. Since the local telnet daemons will use TCP port 23 and clients on system B will use any unused user-space TCP port, you could use the following command: IPv6 example On system A you want to determine which host IPsec policy will be used for outbound telnet traffic to system B or when local users telnet to system B. Since the telnet clients on system A will use any unused user-space TCP port and the telnet daemons on system B will use TCP port 23, you could use the following command: On system A you want to determine which host IPsec policy will be used for inbound telnet traffic from system B or when users on system B telnet to the local system. Since the local telnet daemons will use TCP port 23 and clients on system B will use any unused user-space TCP port, you could use the following command: WARNINGS
requires the optional HP-UX IPSec software. AUTHOR
was developed by HP. SEE ALSO
ipsec_admin(1M), ipsec_config(1M), ipsec_config_add(1M), ipsec_config_batch(1M), ipsec_config_delete(1M), ipsec_config_export(1M), ipsec_config_show(1M), ipsec_migrate(1M), ipsec_report(1M). HP-UX IPSec Software Required ipsec_policy(1M)
All times are GMT -4. The time now is 10:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy