@jobstfel wrote:
Hi,
Question posed by @walbert about TCP ports used by VIRL:
VIRL uses the following inbound TCP ports:
SSH access to server - 22
STD - 19399
UWM - 19400
AutoNetkit - 19401
Live Visualization - 19402
VM Console ports - 17000-18000If the console port range is problematic (particularly when it comes to security filters, VPN clients etc.) - you can set a static port which will be used for SSH access to the VMs inside your simulation.
You must set your topology to use the LXC management node as per below
Image may be NSFW.
Clik here to view.
Then create an 'extensions' key/value pair with key named 'lxc.host.tcp_port' and the value set to the TCP port that you'd like to use.
Image may be NSFW.
Clik here to view.When the simulation is spun up, you're then able to ssh to the IP address of your VIRL server but using the port value that you've specified (30123 in the example above). When you do this, your ssh connection will be forwarded by your VIRL server and will land you on the LXC. Your username and password will be set to that of the username/password under which you've started your simulation (guest/guest by default).
From the LXC, you're then able to telnet to the Mgmt interface of your VMs, assuming that you've configured the interface of course!
Posts: 1
Participants: 1
