Details
-
Type:
extRequest
-
Status: Closed
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:Budapest
Description
Dear madam/sir,
I made Ubuntu instance on lab.fiware.org, I allocated and associated IP,
but on every server where I tried to that (Spain2, Madrid, Prague, etc),
public IP is unreachable (I tried with, ping and tracert commands, and with
Putty) so I can't manage my Instance using SSH.
Few month ago, I done the same and everything was OK. Am I doing something
wrong or it is current problem with fi-ware?
I noticed that there are few IP pools, e.g. net8300, public-ext-net-1,
federation-ext-net-1, etc. Where can I read more about it, is there any
differences between them etc.?
Best regards,
Vladan
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Vladan Minic <vladan.minic.ns@gmail.com>]
Activity
- All
- Comments
- History
- Activity
- Transitions
Answered on 14th March, 2015:
Dear Vladan,
The naming of different IP pools will be harmonized soon. The ones with "public" in their name represents addresses that can be reached from outside. So please use e.g. public-ext-net-1. After assigning a public IP, you should also add a security rule, enabling TCP port 22 so that you could ssh to the VM.
The "federation" or "mdvpn" networks can be used to interconnect VMs in different regions through a private network, thus these IPs cannot be reached from outside...
I hope this helps. If you still have this issue, don't hesitate to write us again.
Best,
Sandor