SSH Bypasses Netonix CLI depending on SSH client

[Garnet]

Hello,

We've been testing what can be done with SSH on Netonix switch's. The test unit for this is a WS-12-250-DC running firmware version 1.5.8.

The Issue:
SSH via "normal clients" such as OpenSSH connect to the normal Netonix CLI, while clients that are Python Based (e.g. programmatic SSH) connect directly to the Linux CLI.

I verified this by running the help command via both clients while in the Linux CLI and both returned the same result. I attempted to simply exit the Linux Shell on the Python client (since the expected result of exit is to re-enter the Netonix CLI) however this had no effect (e.g. Client still had a Linux CLI).

Is this an issue that has come up before? I was only able to find one other post on the forums of someone attempting this (and I can't find the post anymore).

[Garnet]

Is there a command in the linux CLI to enter the Netonix CLI? It seems this is what the 'switch' command does however it only seems to work if you initially had access to the Netonix CLI. The same is true for the 'return' and 'exit' commands which will only return to the last shell you were in and have no effect when connecting directly to the linux CLI.

[Garnet]

Update: the switch command does work for dropping into the Netonix CLI, however it appears the piece of code that checks each character (e.g. to see if '?' has been pressed) also throws errors on every character.

EDIT: On every character two errors throw:
1. tcsetattr(): Invalid Argument
2. tcsetattr ICANON: Invalid argument