[Fiware-robotics] Robotics in FIWARE-LAB: public IP addresses

Álvaro Arranz aarranz at fi.upm.es
Wed Jul 15 14:43:46 CEST 2015


Hi Gianmario,

the Wirecloud instance on FIWARE Lab is hosted by Red.es, so it cannot use,
directly, the internal IPs provided in FIWARE Lab. However, we can deploy a
VPN service if required, what region of FIWARE Lab are you using?

Cross domain is not a problem for Wirecloud (as it provides a proxy), the
only thing that cannot go through the proxy are the connections to the
websockets created by the Kurento Application, but in that case is very
easy to use the access control headers. Here we can have a problem if we
are going to use the Mashup portal of FIWARE Lab, as it is running over
HTTPS, so the ideal is to also use certificates on the websockets created
by the Kurento Applicaition to avoid some security alerts from the browser.
I think is feasible to ask for certificates and for domain names for the
services we are going to make public for the demo... Anyway, this is not
going to be a serious problem, as the demo can work without those domain
names and certificates (the drawback is that the user will have to accept
connecting with the kurento application server).

Best regards,
Álvaro

On 15 July 2015 at 12:23, Luis López Fernández <luis.lopez at urjc.es> wrote:

> Kurento Media Server does not require a public IP address if you configure
> a STUN server for it.
>
> However, the Kurento Application server needs to be reachable from the
> external world (i.e. needs to accept HTTP requests coming from browsers).
> You can use the same IP for this application server and for the wirecloud
> one, but this may generate XSS problems and the browser, you'll need to
> check and to architect appropriately the applications for avoiding them.
>
> Best regards.
>
> El 14/07/2015, a las 12:26, Bollano Gianmario <
> gianmario.bollano at telecomitalia.it> escribió:
>
> Dear Alvaro and others,
> we have successfully asked for the creation of an account for the Robotics
> Live Demo.
> We are now facing a major issue: it seems we can only have one public IP
> address.
>
> We would like to ask you an important question: using Wirecloud instance
> in FIWARE, can Widgets access to VMs hosted in FIWARE-LAB (through piping)
> using their private addresses?
> Or do we need a public IP address for each VM?
>
> For instance, we’ll have one VM for Kurento, one VM  for ContextBroker,
> one VM for Robotics, and widgets will access each of them: can we do this
> using their private IP addresses if we’ll only have one public IP address
> for all Robotics environment?
>
> Gianmario
>
>
>
> ------------------------------------------------------------------------------------
>
> *Telecom Italia*Gianmario Bollano
> Innovation - Mobile Devices & Sim Applications
> Via Reiss Romoli, n° 274
> Cap 10151 Torino
> Phone 011 228 7103
> Cell Phone 3316015048
>
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
> persone indicate. La diffusione, copia o qualsiasi altra azione derivante
> dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora
> abbiate ricevuto questo documento per errore siete cortesemente pregati di
> darne immediata comunicazione al mittente e di provvedere alla sua
> distruzione, Grazie.
>
> *This e-mail and any attachments** is **confidential and may contain
> privileged information intended for the addressee(s) only. Dissemination,
> copying, printing or use by anybody else is unauthorised. If you are not
> the intended recipient, please delete this message and any attachments and
> advise the sender by return e-mail, Thanks.*
> *<logo Ambiente_foglia2.jpg>Rispetta l'ambiente. Non stampare questa mail
> se non è necessario.*
>
> <logo Ambiente_foglia2.jpg>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150715/d711c140/attachment.html>


More information about the Fiware-robotics mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy