Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Help in parsing expect command's output and remove new lines EXPECT scripting
Top Forums UNIX for Beginners Questions & Answers Help in parsing expect command's output and remove new lines EXPECT scripting Post 303045880 by Chubler_XL on Thursday 16th of April 2020 07:09:40 PM
Old 04-16-2020
Your RE is matching the local echo of hostname -i\r sent earlier. Try this RE .*\r\n(.*)\r\n#

For example:
Code:
set timeout 3
log_user 0
expect "# " {send "hostname -i\r"}
expect {
   -re ".*\r\n(.*)\r\n# " {set addr1 $expect_out(1,string)}
   timeout { puts "Timeout looking for TCP/IP address\n"; }
}
send "exit\r"

puts "TCP/IP address is: $addr1"

 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Expect: Parsing/evaluating lines of numbers

There *has* to be an elegant way to do this in Expect... I have a command that returns lines of numbers. Like: prompt% mycommand --loop=5 9 4956 4951 4951 4956 9 4960 4951 4951 4956 9 4956 4951 4951 4956 9 4956 4951 4951 4956 9 4956 4951 4951 4956 prompt% All numbers must be... (0 Replies)
Discussion started by: kajkaj
0 Replies

2. Shell Programming and Scripting

strange expect script behavior, or am i misunderstanding expect scripting?

Hello to all...this is my first post (so please go easy). :) I feel pretty solid at expect scripting, but I'm running into an issue that I'm not able to wrap my head around. I wrote a script that is a little advanced for logging into a remote Linux machine and changing text in a file using sed.... (2 Replies)
Discussion started by: v1k0d3n
2 Replies

3. Shell Programming and Scripting

Need help with Expect script for Cisco IPS Sensors, Expect sleep and quoting

This Expect script provides expect with a list of IP addresses to Cisco IPS sensors and commands to configure Cisco IPS sensors. The user, password, IP addresses, prompt regex, etc. have been anonymized. In general this script will log into the sensors and send commands successfully but there are... (1 Reply)
Discussion started by: genewolfe
1 Replies

4. Shell Programming and Scripting

Expect scripting

Hi I have a working expect script below. The script continues to log cisco router configurations until all the ip addresses in the "routerlist1" has been read. Problem will start to happen when one of the ip address is not reacheable via ssh or telnet. The script will stop to read the rest of the... (2 Replies)
Discussion started by: yano1o14
2 Replies

5. Shell Programming and Scripting

Parsing expect_out using regex in expect script

Hi, I am trying to write an expect script. Being a newbie in expect, maybee this is a silly doubt but i am stuck here. So essentially , i want the o/p of one router command to be captured . Its something like this Stats Input Rx : 1234 Input Bytes : 3456 My expect script looks ... (5 Replies)
Discussion started by: ashy_g
5 Replies

6. Shell Programming and Scripting

Expect scripting

Hello, I tried to use expect to catch information from my nagios and send me a call but i have nothing when i execute the script : 0 - add : account SIP 1 - trext : information from nagios text2wav : conversion text to wav ( text to speech ) pjsua : connection thru the SIP ... (0 Replies)
Discussion started by: acidozik
0 Replies

7. Shell Programming and Scripting

Expect scripting.

I was wondering if I could do this a bit better. another script calls this script and logs into a device, does the relavant "show commands" and then saves those to a file. My problem is that the buffer isn't large enough to the output of some of the commands. here is an excerpt of what i'm... (0 Replies)
Discussion started by: gen1mx6
0 Replies

8. IP Networking

IP and expect scripting

Hi I am new to IP configuration and using expect script I have a requirement like I need to write a expect script that can ssh to a remote machine(linux1) using password which already has IP, once logged inside machine need to reboot remote machine(linux1) and again login to same remote... (1 Reply)
Discussion started by: Priya Amaresh
1 Replies

9. Programming

Expect script returning string following a found expect.

I'm fairly new to scripting so this might not be possible. I am using Expect with Cisco switches and need to capture the string after finding the expect request. For example, when I issue "show version" on a Nexus switch, I'm looking to capture the current firmware version: #show version ... (0 Replies)
Discussion started by: IBGaryA
0 Replies

LEARN ABOUT DEBIAN

vanessa_socket_pipe

VANESSA_SOCKET_PIPE(1)					      General Commands Manual					    VANESSA_SOCKET_PIPE(1)

NAME

       vanessa_socket_pipe - Trivial TCP/IP pipe based on libvanessa_socket

SYNOPSIS

       vanessa_socket_pipe [options]

DESCRIPTION

       A  TCP/IP  pipe	is a user space programme that listens for TCP/IP connections on port on the local host and when a client connects makes a
       connection to a TCP port, possibly on another host. Once both connections are established data sent on one connection  is  relayed  to  the
       other, hence forming a bi-directional pipe.

       Uses include enabling connections to specific ports on hosts behind a packet filter.

       This code is intended primarily as an example of how many of the features of libvanessa_socket work.

OPTIONS

       -c|--connection_limit:
	      Maximum  number  of  connections	to accept simultaneously. A value of zero sets no limit on the number of simultaneous connections.
	      (default 0)

       -d|--debug:
	      Turn on verbose debuging to stderr.

       -h|--help:
	      Display this message.

       -L|--listen_port:
	      Port to listen on. (mandatory)

       -l|--listen_host:
	      Address to listen on. May be a hostname or an IP address.  If not defined then listen on all local addresses.

       -n|--no_lookup:
	      Turn off lookup of hostnames and portnames. That is, hosts must be given as IP addresses and ports must be given as numbers.

       -O|--outgoing_port:
	      Define a port to connect to. If not specified -l|--listen_port will be used.

       -o|--outgoing_host:
	      Define host to connect to.  May be a hostname or an IP address. (mandatory)

       -q|--quiet:
	      Only log errors. Overriden by -d|--debug.

       -t|--timeout:
	      Idle timeout in seconds.	Value of zero sets infinite timeout.  (default 1800)

       Notes: Default value for binary flags is off.
	      -L|--listen_port and -o|--outgoing_host must be defined.

AUTHOR

       Simon Horman <horms@verge.net.au>

								12th February 2001					    VANESSA_SOCKET_PIPE(1)
All times are GMT -4. The time now is 06:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy