This is probably very simple, but is there a way to stop a trace in progress as opposed to waiting for all 30 hops to be tried (and timed out?). I know that there are two "adjacent" routers, connected via tunnels, but when I trace to interfaces "inside' the tunnels I have to wait for all 30 hops when troubleshooting failed connections, but wrking connections get through with 2 hops.
Actually it is not necessary to type the "x" to stop a ping or trace. And in your case typing the x causes your issue.
All you really need to stop a ping or trace is the shirt CTRL 6. In my experience of telnet to a router and then telnet to another router if I just type shift CTRL 6 and type the key combination several times it will stop the ping or trace.
What you need is the interrupt character represented by shift CTRL 6. If you type it and then type x it will suspend the telnet. But if you type it without the x then it just interrupts the ping or trace.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...