13.0.6 SSH sometimes gets stuck at commands, pressing a key like space fixes it

Hi,
I will assign this to one of our developers but don't expect an answer before our return to the office next week.

Sorry for the delay

Hi,

any news on this ?

We are in the process of setting up a testing environment in order to reproduce your bug. As soon as the environment is ready, I will begin working on a solution.

Regards,

Hi..

I found another Bug.
When I connect a Cisco Device (in my case a ASA) and issue "ping 1.2.3.4" the SSH Session crashes:
Disconnected: Server protocoll violation: unexpected SSH2_MSG_UNIMPLEMENTED packet

Hi,

We finally got our setup right, and I just tried doing a "ping 1.2.3.4" on a cisco ASA switch and it worked. I mean by that the terminal did not crash. The ping failed to resolve any host and aborted normally. I think we will need more info on your setup in order to reproduce this weird bug.

Regards

Ive recorded a Video, but that does not show the Error Message that appeared.
Can you give me an email ? Then I'll send it to you.
You can see that the terminal crashes after the ping command on different systems.

Hi,

I am beginning to understand a little bit better what is happening. Right now, I think it could be caused by localisation. It would be great if you could send me a video of another terminal that works. This could give me a clue about what makes the terminal close. Another thing that could help me is if you could enable verbose and logging in the advanced tab and send me the logs of the faulty terminals.

For the "sh run" command, when I do it on our system, it displays a "<--- More --->" at the bottom of the screen, for which it is normal to press a key to make it continue. Yours seems to behave differently (it outputs more than a page before stopping). This might be a setting on the cisco asa. If you know about it, it would be helpful if you could tell me which setting to change.

Thanks for your help

Hi..

the command is "pager"

conf t
no pager
exit

The ping problem seems to happen only on two ASAs in a failover Cluster

Hi,

I've been able to reproduce the "sh run" problem, but intermittently and outside of my debugging setup. Based on these observations, I made a fix which I think should resolve your issues. This fix will be available in our next beta release.

Regards,

Cool thanks