# exp_internal 1 # Can enable this line for debugging. The script I wrote/ran is: #!/usr/bin/expect -f In order for me to connect, I have to unplug the ethernet cable from the switch, and reconnect.Īnyone know why I have the two above issues? I know this because when I launch a new terminal and try to connect to the switch using Minicom, I can not connect. /usr/bin/expect -f expinternal 1 can enable this line for debugging. Two, after running the commands, the serial port becomes busy. The terminal still shows expect1.1> and every time I use a new command like "ls", "cd" or another environment command I get an incremental value such as "expect1.2", "expect1.3", etc. I then entered "#!/usr/bin/bash" as well as "#!/usr/bin/env bash" I thought the default shell changed, so I tried "chsh /usr/bin/bash" with no luck. This is now permanent on my Kali Linux RPi box. One, the shell now shows me expect1.1> and not root> The script sends the single line commands, though I have ran into two problems. I wrote a simple TCL/Expect script to automate some commands to a Cisco Switch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |