Commit e6a8942a authored by Francesc Guasch's avatar Francesc Guasch
Browse files

docs(feature): ports and machine exposing

parent bbac26f8
......@@ -36,3 +36,9 @@ HTTP Forwarding
HTTP forwarding can be configured in a web server in the host to access internal web
services from outside.
Expose Ports
Ports from the virtual machine can be exposed to outside with this new feature
introduced in release 0.5.
Exposing Ports from a Virtual Machine
Since release 0.5 ports from the internal virtual machine can be
exposed to outside.
Ports exposing works with Linux Kernel *iptables* so it requires the
host to have it installed in properly configured.
The virtual machine must have a way to tell the host what is the
internal IP to the host, so the `qemu guest agent <qemu_ga.html>` must be installed.
Configure Expose
From the virtual machine settings there is a new menu item **Ports**.
There you can add new ports to be exposed.
There you must add the number of the internal port to be exposed and
an optional name. If you set this port to *restricted* it will only
be allowed to the remote client IP.
- *Port*: internal port in the virtual machine
- *Name*: optional short description of the service to expose
- *Restricted*: restrict the port to the remote client if set
.. image:: images/ports_expose.png
When the virtual machine gets started Ravada searches for a free
port in the host to expose the port through.
In this example the user can connect to the IP port 5954
to access the SSH server inside the virtual machine.
.. image:: images/ports_expose_run.png
Ports redirection requires the internal IP of the virtual machine
to be active. So it retries for a while trying to redirect until
an IP is detected or it fails.
......@@ -102,6 +102,8 @@ Do you feel like giving us a hand? Here you have all the information you need as
.. _guest-docs:
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment