The latest beta notes that the remote terminal is no longer set up out
of the box. Previously I've been using a custom deployment system that
started the VM and then used SSH to configure iptables to do some NAT
and routing things. How do you suggest I do something like this with
the latest WANem beta?
Andrew Sayman
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Remote terminal option is available but remote login, SSH etc. are disabled. Remote terminal option is available via WANem GUI. It uses ajaxterm to perform SSH to WANem. The default prompt that opens up is WANem console prompt. You can do a 'exit2shell' to go to the root prompt and perform the desired tasks.
However, please be aware that 'vi' editor does not work properly in Ajaxterm's current version. There is no way to switch between command and edit mode inside the vi editor.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The latest beta notes that the remote terminal is no longer set up out
of the box. Previously I've been using a custom deployment system that
started the VM and then used SSH to configure iptables to do some NAT
and routing things. How do you suggest I do something like this with
the latest WANem beta?
Andrew Sayman
Remote terminal option is available but remote login, SSH etc. are disabled. Remote terminal option is available via WANem GUI. It uses ajaxterm to perform SSH to WANem. The default prompt that opens up is WANem console prompt. You can do a 'exit2shell' to go to the root prompt and perform the desired tasks.
However, please be aware that 'vi' editor does not work properly in Ajaxterm's current version. There is no way to switch between command and edit mode inside the vi editor.