Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: Sprint 4.1.2
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:Spain
Description
Dear Jose,
please find the tcptraceroute at the bottom of the email.
There is even the NAT table thay apply on their FW.
The "public" ip from which their calls are originated is:
129.192.96.203
May you try to help us in sorting the issue out?
They keep on saying thay cannot reach 130.206.85.6
Might we organize a sort of "joint" session where you sniff the incoming
traffic on 130.206.85.6 (originated by 129.192.96.203)?
We are stuck!
Thank you in advance for your cooperation.
Regards,
Massimiliano
-------- Messaggio Inoltrato --------
Oggetto: R: R: Re: [FINESCE WP4] Problems faced by external partners in
connecting to a VM in FI-LAB
Data: Fri, 31 Oct 2014 16:29:21 +0000
Mittente: MASSIMILIANO LILI <massimiliano.lili@ericsson.com>
A: Massimiliano Nigrelli <massimiliano.nigrelli@eng.it>
CC: Daniele Piferi <daniele.piferi@ericsson.com>,
Pasquale.Andriani@eng.it <Pasquale.Andriani@eng.it>, Leandro Lombardo
<Leandro.Lombardo@eng.it>, dar >> Pellegrino Dario
<Dario.Pellegrino@eng.it>
Ciao Massimiliano
I pacchetti di rete escono, ecco il traceroute :
traceroute to 130.206.85.6 (130.206.85.6), 30 hops max, 60 byte packets
1 172.30.5.17 (172.30.5.17) 0.285 ms 0.216 ms 0.248 ms
2 172.30.1.97 (172.30.1.97) 0.680 ms 0.837 ms 0.991 ms
3 129.192.96.3 (129.192.96.3) 2.845 ms 2.909 ms 2.866 ms
4 89.97.247.13 (89.97.247.13) 2.996 ms 3.080 ms 3.040 ms
5 93.61.0.1 (93.61.0.1) 3.140 ms 3.209 ms 3.167 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 89.97.200.186 (89.97.200.186) 3.701 ms 89.97.200.190
(89.97.200.190) 3.780 ms 3.763 ms
11 89.97.200.254 (89.97.200.254) 13.208 ms 89.96.200.1 (89.96.200.1)
14.078 ms 89.97.200.254 (89.97.200.254) 11.383 ms
12 62.101.124.65 (62.101.124.65) 11.200 ms 89.96.200.126
(89.96.200.126) 11.306 ms 89.96.200.26 (89.96.200.26) 12.241 ms
13 * * *
14 129.250.4.169 (129.250.4.169) 58.174 ms 57.429 ms 58.155 ms
15 129.250.2.146 (129.250.2.146) 27.566 ms 28.446 ms 28.176 ms
16 129.250.2.235 (129.250.2.235) 61.781 ms 58.101 ms 58.042 ms
17 129.250.2.42 (129.250.2.42) 59.603 ms 55.311 ms 59.042 ms
18 129.250.4.104 (129.250.4.104) 57.114 ms 61.773 ms 61.940 ms
19 193.149.1.26 (193.149.1.26) 65.362 ms 66.078 ms 71.563 ms
20 130.206.245.46 (130.206.245.46) 68.211 ms 66.253 ms 65.467 ms
21 130.206.192.158 (130.206.192.158) 67.450 ms 61.682 ms 61.462 ms
22 130.206.85.6 (130.206.85.6) 74.730 ms 74.831 ms 75.393 ms
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Ed il NAT che facciamo verso di voi :
014-10-31 17:22:12
172.30.5.18:34482
130.206.85.6:80
129.192.96.203:51818
130.206.85.6:80
HTTP
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:21:28
172.30.5.18:44539
130.206.85.6:33523
129.192.96.203:51817
130.206.85.6:33523
UDP PORT 33523
64 sec.
142
0
Close - AGE OUT
2014-10-31 17:21:28
172.30.5.18:45044
130.206.85.6:33522
129.192.96.203:51816
130.206.85.6:33522
UDP PORT 33522
64 sec.
142
0
Close - AGE OUT
2014-10-31 17:21:28
172.30.5.18:40417
130.206.85.6:33521
129.192.96.203:51815
130.206.85.6:33521
UDP PORT 33521
64 sec.
142
0
Close - AGE OUT
2014-10-31 17:19:18
172.30.5.18:32910
130.206.85.6:443
129.192.96.203:51814
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:18
172.30.5.18:32909
130.206.85.6:443
129.192.96.203:51813
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32908
130.206.85.6:443
129.192.96.203:51812
130.206.85.6:443
HTTPS
22 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32906
130.206.85.6:443
129.192.96.203:51810
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32907
130.206.85.6:443
129.192.96.203:51811
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32903
130.206.85.6:443
129.192.96.203:51808
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32904
130.206.85.6:443
129.192.96.203:51809
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:14
172.30.5.18:32902
130.206.85.6:443
129.192.96.203:51807
130.206.85.6:443
HTTPS
22 sec.
262
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:36034
130.206.85.6:33513
129.192.96.203:51799
130.206.85.6:33513
UDP PORT 33513
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:46684
130.206.85.6:33512
129.192.96.203:51798
130.206.85.6:33512
UDP PORT 33512
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:43916
130.206.85.6:33519
129.192.96.203:51805
130.206.85.6:33519
UDP PORT 33519
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:48269
130.206.85.6:33518
129.192.96.203:51804
130.206.85.6:33518
UDP PORT 33518
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:35146
130.206.85.6:33517
129.192.96.203:51803
130.206.85.6:33517
UDP PORT 33517
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:37619
130.206.85.6:33516
129.192.96.203:51802
130.206.85.6:33516
UDP PORT 33516
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:47742
130.206.85.6:33515
129.192.96.203:51801
130.206.85.6:33515
UDP PORT 33515
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:49698
130.206.85.6:33514
129.192.96.203:51800
130.206.85.6:33514
UDP PORT 33514
65 sec.
142
0
Close - AGE OUT
QUESTO è il nostro indirizzo Pubblico : 129.192.96.203
dovreste verificare sulla vostra rete come vengono processate queste
richieste.
Grazie
M.
*Da:*Massimiliano Nigrelli massimiliano.nigrelli@eng.it
Inviato: venerdì 31 ottobre 2014 16:48
A: MASSIMILIANO LILI
Cc: Daniele Piferi; Pasquale.Andriani@eng.it; Leandro Lombardo; dar >>
Pellegrino Dario
Oggetto: Re: R: Re: [FINESCE WP4] Problems faced by external partners
in connecting to a VM in FI-LAB
Ciao Massimiliano,
il mio numero di telefono +39 091.75.11.847.
Disponbile per una telefonata (anche se non sono un sistemista!) fino
alle 17:15.
In ogni caso questa non è una trace route. Questo è il log del Juniper
(un firewall).
Nella trace route ci sono i vari HOPS, punti di passaggio che i
pacchetti attraversano nel raggiunger l'host di destinazione.
Saluti,
M.
Il 31/10/2014 16:29, MASSIMILIANO LILI ha scritto:
Ciao Massimiliano,
già mandato ieri (se mi dai il tuo telefono ti faccio chiamare dal
sistemista):
2014-10-30 16:00:32
172.30.5.18:43419
130.206.85.6:443
129.192.96.203:48484
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:32
172.30.5.18:43424
130.206.85.6:443
129.192.96.203:48485
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:30
172.30.5.18:43416
130.206.85.6:443
129.192.96.203:48483
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:24
172.30.5.18:43412
130.206.85.6:443
129.192.96.203:48482
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43405
130.206.85.6:443
129.192.96.203:48479
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43404
130.206.85.6:443
129.192.96.203:48478
130.206.85.6:443
HTTPS
25 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43408
130.206.85.6:443
129.192.96.203:48481
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43407
130.206.85.6:443
129.192.96.203:48480
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:12
172.30.5.18:43401
130.206.85.6:443
129.192.96.203:48477
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
Visto che per mandare le richieste utilizziamo un vostro client
“metering-input-client-0.0.9.jar”
Ci servirebbe che generasse il LOG, per esempio per vedere quanto
tempo di timeout aspetta per ricevere la risposta ed eventuali altre
cose.
potete abilitare questo sul vostro client e rimandarlo ?
Grazie
M.
*Da:*Massimiliano Nigrelli massimiliano.nigrelli@eng.it
Inviato: venerdì 31 ottobre 2014 15:41
A: MASSIMILIANO LILI
Cc: Daniele Piferi; Pasquale.Andriani@eng.it
<Pasquale.Andriani@eng.it>; Leandro Lombardo; dar >>
Pellegrino Dario
Oggetto: Fwd: Re: [FINESCE WP4] Problems faced by external
partners in connecting to a VM in FI-LAB
Ciao Massimiliano,
mi hanno risposto, come puoi vedere in calce.
Il nostro IP dovrebbe essere raggiungibile da qualsiasi parte del
mondo (lui ha provato con un cellulare dal posto in cui si
trova...........Spagna?).
Mi conferma che 130.206.85.6 non è raggiungibile da 172.30.5.18 e
suggerisce di fare un tcptraceroute dalla macchina dove gira
l'applicativo (quella che non raggiunge 130.206.85.6 per intenderci).
Last, but not least (the 2nd png) I'm aware that you can't access
130.206.85.6 from your private IP 172.30.5.18. But I don't know what is
the last step in the route to that host. So I can't reproduce that
error, may be some tcptraceroute output to that port could be helpful.
Tu ci hai mandato il tracelog del FW, ma non si vedono i vari punti
di passaggio (HOPs).
Continuo a pensare che i pacchetti non escono dalla vostra LAN.
Aspetto di avere il "tcptraceroute" in maniera tale da girarlo a
Josè il prima possibile.
Saluti,
Massimiliano
-------- Messaggio Inoltrato --------
*Oggetto: *
Re: [FINESCE WP4] Problems faced by external partners in connecting
to a VM in FI-LAB
*Data: *
Fri, 31 Oct 2014 14:29:05 +0000
*Mittente: *
JOSE IGNACIO CARRETERO GUARDE
<joseignacio.carreteroguarde@telefonica.com>
<joseignacio.carreteroguarde@telefonica.com>
*A: *
Massimiliano Nigrelli <massimiliano.nigrelli@eng.it>
<massimiliano.nigrelli@eng.it>,
fiware-lab-help@lists.fi-ware.org
<fiware-lab-help@lists.fi-ware.org>
<fiware-lab-help@lists.fi-ware.org>
<fiware-lab-help@lists.fi-ware.org>
*CC: *
Pasquale.Andriani@eng.it <Pasquale.Andriani@eng.it>
<Pasquale.Andriani@eng.it> <Pasquale.Andriani@eng.it>,
Leandro Lombardo <Leandro.Lombardo@eng.it>
<Leandro.Lombardo@eng.it>, Pellegrino Dario
<Dario.Pellegrino@eng.it> <Dario.Pellegrino@eng.it>
Dear Massimiliano,
The first .png file is a screenshot I've taken in my phone.... – My
phone using its 3G network connection, not Wifi or anything like that.
This means that the servicer with IP 130.206.85.6 is accessible from
everywhere.
—
I've seen in your email some "error messages": CLOSE AGE OUT — This is
a Juniper error message. May I ask what do your Juniper experts say
about this message? Sorry, but I don't know much about that software nor
the way you are using it to stablish your VPNs.
—
Last, but not least (the 2nd png) I'm aware that you can't access
130.206.85.6 from your private IP 172.30.5.18. But I don't know what is
the last step in the route to that host. So I can't reproduce that
error, may be some tcptraceroute output to that port could be helpful.
Thank you for forwarding your message to the list, that's the best way
to contact us.
Best regards,
José Ignacio.
El 31/10/14 a las #4, Massimiliano Nigrelli escribió:
> Dear Jose, dear all,
> I have not received any reply to the email I sent you yesterday.
>
> It would be nice to be contacted and advised on what might have caused
> the issue we described on our last email.
>
> In order to help you sorting out the issue, I attach the tracelog
> captured at the FW level from our external partners.
>
> Please, we are really stuck and we have a review in two weeks time.
>
> Regards,
>
> Massimiliano
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
–
===============================================================
Massimiliano Nigrelli - R&D Lab
Viale Regione Siciliana 7275 - 90146 Palermo (Italy)
Phone: +39 091.75.11.847
============================================================
_______________________________________________
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: Massimiliano Nigrelli <massimiliano.nigrelli@eng.it>]
Activity
Dear Josè, dear all,
from this morning we are not able to authenticate on our wirecloud
instance located at http://130.206.82.217/
Is there any issue? Or is there any "unscheduled" maintenance activity?
Could you please let us know the "state-of-the-art"?
As I have just told you via email, we are going to have a review in two
weeks time (where we are going to show our "live" stuff) and, as you can
understand, we are a bit worried that we will not be able to access our
application in the review days.
Regards,
Massimiliano
Dear Massimiliano,
the account.lab.fi-ware.org service is currently down due to an unexpected
problem, the IdM team is working on fixing it as soon as possible. Sorry
for the inconveniences.
Best regards,
Álvaro
On 3 November 2014 11:09, Massimiliano Nigrelli <
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
Hi,
It is working again.
Best regards,
José Ignacio.
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
I'm sniffing this traffic: host 129.192.96.203 or host 130.206.85.6
Best regards,
José Ignacio.
El 03/11/14 a las #4, Massimiliano Nigrelli escribió:
Dear Jose,
any news regarding the issue we reported on Friday?
What about a "joint" session where our external partners try to connect to 130.206.85.6 so to let you see if they are able to "reach" the cloud at least?
Regards,
Massimiliano
Il 31/10/2014 17:39, Massimiliano Nigrelli ha scritto:
Dear Jose,
please find the tcptraceroute at the bottom of the email.
There is even the NAT table thay apply on their FW.
The "public" ip from which their calls are originated is:
129.192.96.203
May you try to help us in sorting the issue out?
They keep on saying thay cannot reach 130.206.85.6
Might we organize a sort of "joint" session where you sniff the incoming traffic on 130.206.85.6 (originated by 129.192.96.203)?
We are stuck!
Thank you in advance for your cooperation.
Regards,
Massimiliano
-------- Messaggio Inoltrato --------
Oggetto: R: R: Re: [FINESCE WP4] Problems faced by external partners in connecting to a VM in FI-LAB
Data: Fri, 31 Oct 2014 16:29:21 +0000
Mittente: MASSIMILIANO LILI <massimiliano.lili@ericsson.com><massimiliano.lili@ericsson.com>
A: Massimiliano Nigrelli <massimiliano.nigrelli@eng.it><massimiliano.nigrelli@eng.it>
CC: Daniele Piferi <daniele.piferi@ericsson.com><daniele.piferi@ericsson.com>, Pasquale.Andriani@eng.it<Pasquale.Andriani@eng.it> <Pasquale.Andriani@eng.it><Pasquale.Andriani@eng.it>, Leandro Lombardo <Leandro.Lombardo@eng.it><Leandro.Lombardo@eng.it>, dar >> Pellegrino Dario <Dario.Pellegrino@eng.it><Dario.Pellegrino@eng.it>
Ciao Massimiliano
I pacchetti di rete escono, ecco il traceroute :
traceroute to 130.206.85.6 (130.206.85.6), 30 hops max, 60 byte packets
1 172.30.5.17 (172.30.5.17) 0.285 ms 0.216 ms 0.248 ms
2 172.30.1.97 (172.30.1.97) 0.680 ms 0.837 ms 0.991 ms
3 129.192.96.3 (129.192.96.3) 2.845 ms 2.909 ms 2.866 ms
4 89.97.247.13 (89.97.247.13) 2.996 ms 3.080 ms 3.040 ms
5 93.61.0.1 (93.61.0.1) 3.140 ms 3.209 ms 3.167 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 89.97.200.186 (89.97.200.186) 3.701 ms 89.97.200.190 (89.97.200.190) 3.780 ms 3.763 ms
11 89.97.200.254 (89.97.200.254) 13.208 ms 89.96.200.1 (89.96.200.1) 14.078 ms 89.97.200.254 (89.97.200.254) 11.383 ms
12 62.101.124.65 (62.101.124.65) 11.200 ms 89.96.200.126 (89.96.200.126) 11.306 ms 89.96.200.26 (89.96.200.26) 12.241 ms
13 * * *
14 129.250.4.169 (129.250.4.169) 58.174 ms 57.429 ms 58.155 ms
15 129.250.2.146 (129.250.2.146) 27.566 ms 28.446 ms 28.176 ms
16 129.250.2.235 (129.250.2.235) 61.781 ms 58.101 ms 58.042 ms
17 129.250.2.42 (129.250.2.42) 59.603 ms 55.311 ms 59.042 ms
18 129.250.4.104 (129.250.4.104) 57.114 ms 61.773 ms 61.940 ms
19 193.149.1.26 (193.149.1.26) 65.362 ms 66.078 ms 71.563 ms
20 130.206.245.46 (130.206.245.46) 68.211 ms 66.253 ms 65.467 ms
21 130.206.192.158 (130.206.192.158) 67.450 ms 61.682 ms 61.462 ms
22 130.206.85.6 (130.206.85.6) 74.730 ms 74.831 ms 75.393 ms
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Ed il NAT che facciamo verso di voi :
014-10-31 17:22:12
172.30.5.18:34482
130.206.85.6:80
129.192.96.203:51818
130.206.85.6:80
HTTP
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:21:28
172.30.5.18:44539
130.206.85.6:33523
129.192.96.203:51817
130.206.85.6:33523
UDP PORT 33523
64 sec.
142
0
Close - AGE OUT
2014-10-31 17:21:28
172.30.5.18:45044
130.206.85.6:33522
129.192.96.203:51816
130.206.85.6:33522
UDP PORT 33522
64 sec.
142
0
Close - AGE OUT
2014-10-31 17:21:28
172.30.5.18:40417
130.206.85.6:33521
129.192.96.203:51815
130.206.85.6:33521
UDP PORT 33521
64 sec.
142
0
Close - AGE OUT
2014-10-31 17:19:18
172.30.5.18:32910
130.206.85.6:443
129.192.96.203:51814
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:18
172.30.5.18:32909
130.206.85.6:443
129.192.96.203:51813
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32908
130.206.85.6:443
129.192.96.203:51812
130.206.85.6:443
HTTPS
22 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32906
130.206.85.6:443
129.192.96.203:51810
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32907
130.206.85.6:443
129.192.96.203:51811
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32903
130.206.85.6:443
129.192.96.203:51808
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32904
130.206.85.6:443
129.192.96.203:51809
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:14
172.30.5.18:32902
130.206.85.6:443
129.192.96.203:51807
130.206.85.6:443
HTTPS
22 sec.
262
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:36034
130.206.85.6:33513
129.192.96.203:51799
130.206.85.6:33513
UDP PORT 33513
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:46684
130.206.85.6:33512
129.192.96.203:51798
130.206.85.6:33512
UDP PORT 33512
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:43916
130.206.85.6:33519
129.192.96.203:51805
130.206.85.6:33519
UDP PORT 33519
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:48269
130.206.85.6:33518
129.192.96.203:51804
130.206.85.6:33518
UDP PORT 33518
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:35146
130.206.85.6:33517
129.192.96.203:51803
130.206.85.6:33517
UDP PORT 33517
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:37619
130.206.85.6:33516
129.192.96.203:51802
130.206.85.6:33516
UDP PORT 33516
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:47742
130.206.85.6:33515
129.192.96.203:51801
130.206.85.6:33515
UDP PORT 33515
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:49698
130.206.85.6:33514
129.192.96.203:51800
130.206.85.6:33514
UDP PORT 33514
65 sec.
142
0
Close - AGE OUT
QUESTO è il nostro indirizzo Pubblico : 129.192.96.203
dovreste verificare sulla vostra rete come vengono processate queste richieste.
Grazie
M.
Da: Massimiliano Nigrelli massimiliano.nigrelli@eng.it
Inviato: venerdì 31 ottobre 2014 16:48
A: MASSIMILIANO LILI
Cc: Daniele Piferi; Pasquale.Andriani@eng.it<Pasquale.Andriani@eng.it>; Leandro Lombardo; dar >> Pellegrino Dario
Oggetto: Re: R: Re: [FINESCE WP4] Problems faced by external partners in connecting to a VM in FI-LAB
Ciao Massimiliano,
il mio numero di telefono +39 091.75.11.847.
Disponbile per una telefonata (anche se non sono un sistemista!) fino alle 17:15.
In ogni caso questa non è una trace route. Questo è il log del Juniper (un firewall).
Nella trace route ci sono i vari HOPS, punti di passaggio che i pacchetti attraversano nel raggiunger l'host di destinazione.
Saluti,
M.
Il 31/10/2014 16:29, MASSIMILIANO LILI ha scritto:
Ciao Massimiliano,
già mandato ieri (se mi dai il tuo telefono ti faccio chiamare dal sistemista):
2014-10-30 16:00:32
172.30.5.18:43419
130.206.85.6:443
129.192.96.203:48484
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:32
172.30.5.18:43424
130.206.85.6:443
129.192.96.203:48485
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:30
172.30.5.18:43416
130.206.85.6:443
129.192.96.203:48483
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:24
172.30.5.18:43412
130.206.85.6:443
129.192.96.203:48482
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43405
130.206.85.6:443
129.192.96.203:48479
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43404
130.206.85.6:443
129.192.96.203:48478
130.206.85.6:443
HTTPS
25 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43408
130.206.85.6:443
129.192.96.203:48481
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43407
130.206.85.6:443
129.192.96.203:48480
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:12
172.30.5.18:43401
130.206.85.6:443
129.192.96.203:48477
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
Visto che per mandare le richieste utilizziamo un vostro client “metering-input-client-0.0.9.jar”
Ci servirebbe che generasse il LOG, per esempio per vedere quanto tempo di timeout aspetta per ricevere la risposta ed eventuali altre cose.
potete abilitare questo sul vostro client e rimandarlo ?
Grazie
M.
Da: Massimiliano Nigrelli massimiliano.nigrelli@eng.it
Inviato: venerdì 31 ottobre 2014 15:41
A: MASSIMILIANO LILI
Cc: Daniele Piferi; Pasquale.Andriani@eng.it<Pasquale.Andriani@eng.it>; Leandro Lombardo; dar >> Pellegrino Dario
Oggetto: Fwd: Re: [FINESCE WP4] Problems faced by external partners in connecting to a VM in FI-LAB
Ciao Massimiliano,
mi hanno risposto, come puoi vedere in calce.
Il nostro IP dovrebbe essere raggiungibile da qualsiasi parte del mondo (lui ha provato con un cellulare dal posto in cui si trova...........Spagna?).
Mi conferma che 130.206.85.6 non è raggiungibile da 172.30.5.18 e suggerisce di fare un tcptraceroute dalla macchina dove gira l'applicativo (quella che non raggiunge 130.206.85.6 per intenderci).
Last, but not least (the 2nd png) I'm aware that you can't access
130.206.85.6 from your private IP 172.30.5.18. But I don't know what is
the last step in the route to that host. So I can't reproduce that
error, may be some tcptraceroute output to that port could be helpful.
Tu ci hai mandato il tracelog del FW, ma non si vedono i vari punti di passaggio (HOPs).
Continuo a pensare che i pacchetti non escono dalla vostra LAN.
Aspetto di avere il "tcptraceroute" in maniera tale da girarlo a Josè il prima possibile.
Saluti,
Massimiliano
-------- Messaggio Inoltrato --------
Oggetto:
Re: [FINESCE WP4] Problems faced by external partners in connecting to a VM in FI-LAB
Data:
Fri, 31 Oct 2014 14:29:05 +0000
Mittente:
JOSE IGNACIO CARRETERO GUARDE <joseignacio.carreteroguarde@telefonica.com><joseignacio.carreteroguarde@telefonica.com>
A:
Massimiliano Nigrelli <massimiliano.nigrelli@eng.it><massimiliano.nigrelli@eng.it>, fiware-lab-help@lists.fi-ware.org<fiware-lab-help@lists.fi-ware.org> <fiware-lab-help@lists.fi-ware.org><fiware-lab-help@lists.fi-ware.org>
CC:
Pasquale.Andriani@eng.it<Pasquale.Andriani@eng.it> <Pasquale.Andriani@eng.it><Pasquale.Andriani@eng.it>, Leandro Lombardo <Leandro.Lombardo@eng.it><Leandro.Lombardo@eng.it>, Pellegrino Dario <Dario.Pellegrino@eng.it><Dario.Pellegrino@eng.it>
Dear Massimiliano,
The first .png file is a screenshot I've taken in my phone.... – My
phone using its 3G network connection, not Wifi or anything like that.
This means that the servicer with IP 130.206.85.6 is accessible from
everywhere.
—
I've seen in your email some "error messages": CLOSE AGE OUT — This is
a Juniper error message. May I ask what do your Juniper experts say
about this message? Sorry, but I don't know much about that software nor
the way you are using it to stablish your VPNs.
—
Last, but not least (the 2nd png) I'm aware that you can't access
130.206.85.6 from your private IP 172.30.5.18. But I don't know what is
the last step in the route to that host. So I can't reproduce that
error, may be some tcptraceroute output to that port could be helpful.
Thank you for forwarding your message to the list, that's the best way
to contact us.
Best regards,
José Ignacio.
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
–
===============================================================
Massimiliano Nigrelli - R&D Lab
Viale Regione Siciliana 7275 - 90146 Palermo (Italy)
Phone: +39 091.75.11.847
============================================================
–
===============================================================
Massimiliano Nigrelli - R&D Lab
Viale Regione Siciliana 7275 - 90146 Palermo (Italy)
Phone: +39 091.75.11.847
============================================================
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
traffic originated by 129.192.96.203 towards "your"
130.206.85.6
I am telling our external partners to try right now.
M.
–
===============================================================
Massimiliano Nigrelli - R&D Lab
Viale Regione Siciliana 7275 - 90146 Palermo (Italy)
Phone: +39 091.75.11.847
============================================================
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
No.
All traffic from / to both hosts.
We'll set the addecuate filters later when doing the analisys.
Best regards
José Ignacio.
El 03/11/14 a las #4, Massimiliano Nigrelli escribió:
traffic originated by 129.192.96.203 towards "your"
130.206.85.6
I am telling our external partners to try right now.
M.
Il 03/11/2014 11:35, JOSE IGNACIO CARRETERO GUARDE ha scritto:
I'm sniffing this traffic: host 129.192.96.203 or host 130.206.85.6
Best regards,
José Ignacio.
El 03/11/14 a las #4, Massimiliano Nigrelli escribió:
Dear Jose,
any news regarding the issue we reported on Friday?
What about a "joint" session where our external partners try to connect to 130.206.85.6 so to let you see if they are able to "reach" the cloud at least?
Regards,
Massimiliano
Il 31/10/2014 17:39, Massimiliano Nigrelli ha scritto:
Dear Jose,
please find the tcptraceroute at the bottom of the email.
There is even the NAT table thay apply on their FW.
The "public" ip from which their calls are originated is:
129.192.96.203
May you try to help us in sorting the issue out?
They keep on saying thay cannot reach 130.206.85.6
Might we organize a sort of "joint" session where you sniff the incoming traffic on 130.206.85.6 (originated by 129.192.96.203)?
We are stuck!
Thank you in advance for your cooperation.
Regards,
Massimiliano
-------- Messaggio Inoltrato --------
Oggetto: R: R: Re: [FINESCE WP4] Problems faced by external partners in connecting to a VM in FI-LAB
Data: Fri, 31 Oct 2014 16:29:21 +0000
Mittente: MASSIMILIANO LILI <massimiliano.lili@ericsson.com><massimiliano.lili@ericsson.com>
A: Massimiliano Nigrelli <massimiliano.nigrelli@eng.it><massimiliano.nigrelli@eng.it>
CC: Daniele Piferi <daniele.piferi@ericsson.com><daniele.piferi@ericsson.com>, Pasquale.Andriani@eng.it<Pasquale.Andriani@eng.it> <Pasquale.Andriani@eng.it><Pasquale.Andriani@eng.it>, Leandro Lombardo <Leandro.Lombardo@eng.it><Leandro.Lombardo@eng.it>, dar >> Pellegrino Dario <Dario.Pellegrino@eng.it><Dario.Pellegrino@eng.it>
Ciao Massimiliano
I pacchetti di rete escono, ecco il traceroute :
traceroute to 130.206.85.6 (130.206.85.6), 30 hops max, 60 byte packets
1 172.30.5.17 (172.30.5.17) 0.285 ms 0.216 ms 0.248 ms
2 172.30.1.97 (172.30.1.97) 0.680 ms 0.837 ms 0.991 ms
3 129.192.96.3 (129.192.96.3) 2.845 ms 2.909 ms 2.866 ms
4 89.97.247.13 (89.97.247.13) 2.996 ms 3.080 ms 3.040 ms
5 93.61.0.1 (93.61.0.1) 3.140 ms 3.209 ms 3.167 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 89.97.200.186 (89.97.200.186) 3.701 ms 89.97.200.190 (89.97.200.190) 3.780 ms 3.763 ms
11 89.97.200.254 (89.97.200.254) 13.208 ms 89.96.200.1 (89.96.200.1) 14.078 ms 89.97.200.254 (89.97.200.254) 11.383 ms
12 62.101.124.65 (62.101.124.65) 11.200 ms 89.96.200.126 (89.96.200.126) 11.306 ms 89.96.200.26 (89.96.200.26) 12.241 ms
13 * * *
14 129.250.4.169 (129.250.4.169) 58.174 ms 57.429 ms 58.155 ms
15 129.250.2.146 (129.250.2.146) 27.566 ms 28.446 ms 28.176 ms
16 129.250.2.235 (129.250.2.235) 61.781 ms 58.101 ms 58.042 ms
17 129.250.2.42 (129.250.2.42) 59.603 ms 55.311 ms 59.042 ms
18 129.250.4.104 (129.250.4.104) 57.114 ms 61.773 ms 61.940 ms
19 193.149.1.26 (193.149.1.26) 65.362 ms 66.078 ms 71.563 ms
20 130.206.245.46 (130.206.245.46) 68.211 ms 66.253 ms 65.467 ms
21 130.206.192.158 (130.206.192.158) 67.450 ms 61.682 ms 61.462 ms
22 130.206.85.6 (130.206.85.6) 74.730 ms 74.831 ms 75.393 ms
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Ed il NAT che facciamo verso di voi :
014-10-31 17:22:12
172.30.5.18:34482
130.206.85.6:80
129.192.96.203:51818
130.206.85.6:80
HTTP
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:21:28
172.30.5.18:44539
130.206.85.6:33523
129.192.96.203:51817
130.206.85.6:33523
UDP PORT 33523
64 sec.
142
0
Close - AGE OUT
2014-10-31 17:21:28
172.30.5.18:45044
130.206.85.6:33522
129.192.96.203:51816
130.206.85.6:33522
UDP PORT 33522
64 sec.
142
0
Close - AGE OUT
2014-10-31 17:21:28
172.30.5.18:40417
130.206.85.6:33521
129.192.96.203:51815
130.206.85.6:33521
UDP PORT 33521
64 sec.
142
0
Close - AGE OUT
2014-10-31 17:19:18
172.30.5.18:32910
130.206.85.6:443
129.192.96.203:51814
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:18
172.30.5.18:32909
130.206.85.6:443
129.192.96.203:51813
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32908
130.206.85.6:443
129.192.96.203:51812
130.206.85.6:443
HTTPS
22 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32906
130.206.85.6:443
129.192.96.203:51810
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32907
130.206.85.6:443
129.192.96.203:51811
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32903
130.206.85.6:443
129.192.96.203:51808
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:16
172.30.5.18:32904
130.206.85.6:443
129.192.96.203:51809
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-31 17:19:14
172.30.5.18:32902
130.206.85.6:443
129.192.96.203:51807
130.206.85.6:443
HTTPS
22 sec.
262
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:36034
130.206.85.6:33513
129.192.96.203:51799
130.206.85.6:33513
UDP PORT 33513
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:46684
130.206.85.6:33512
129.192.96.203:51798
130.206.85.6:33512
UDP PORT 33512
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:43916
130.206.85.6:33519
129.192.96.203:51805
130.206.85.6:33519
UDP PORT 33519
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:48269
130.206.85.6:33518
129.192.96.203:51804
130.206.85.6:33518
UDP PORT 33518
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:35146
130.206.85.6:33517
129.192.96.203:51803
130.206.85.6:33517
UDP PORT 33517
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:37619
130.206.85.6:33516
129.192.96.203:51802
130.206.85.6:33516
UDP PORT 33516
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:47742
130.206.85.6:33515
129.192.96.203:51801
130.206.85.6:33515
UDP PORT 33515
65 sec.
142
0
Close - AGE OUT
2014-10-31 17:18:34
172.30.5.18:49698
130.206.85.6:33514
129.192.96.203:51800
130.206.85.6:33514
UDP PORT 33514
65 sec.
142
0
Close - AGE OUT
QUESTO è il nostro indirizzo Pubblico : 129.192.96.203
dovreste verificare sulla vostra rete come vengono processate queste richieste.
Grazie
M.
Da: Massimiliano Nigrelli massimiliano.nigrelli@eng.it
Inviato: venerdì 31 ottobre 2014 16:48
A: MASSIMILIANO LILI
Cc: Daniele Piferi; Pasquale.Andriani@eng.it<Pasquale.Andriani@eng.it>; Leandro Lombardo; dar >> Pellegrino Dario
Oggetto: Re: R: Re: [FINESCE WP4] Problems faced by external partners in connecting to a VM in FI-LAB
Ciao Massimiliano,
il mio numero di telefono +39 091.75.11.847.
Disponbile per una telefonata (anche se non sono un sistemista!) fino alle 17:15.
In ogni caso questa non è una trace route. Questo è il log del Juniper (un firewall).
Nella trace route ci sono i vari HOPS, punti di passaggio che i pacchetti attraversano nel raggiunger l'host di destinazione.
Saluti,
M.
Il 31/10/2014 16:29, MASSIMILIANO LILI ha scritto:
Ciao Massimiliano,
già mandato ieri (se mi dai il tuo telefono ti faccio chiamare dal sistemista):
2014-10-30 16:00:32
172.30.5.18:43419
130.206.85.6:443
129.192.96.203:48484
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:32
172.30.5.18:43424
130.206.85.6:443
129.192.96.203:48485
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:30
172.30.5.18:43416
130.206.85.6:443
129.192.96.203:48483
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:24
172.30.5.18:43412
130.206.85.6:443
129.192.96.203:48482
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43405
130.206.85.6:443
129.192.96.203:48479
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43404
130.206.85.6:443
129.192.96.203:48478
130.206.85.6:443
HTTPS
25 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43408
130.206.85.6:443
129.192.96.203:48481
130.206.85.6:443
HTTPS
23 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:18
172.30.5.18:43407
130.206.85.6:443
129.192.96.203:48480
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
2014-10-30 16:00:12
172.30.5.18:43401
130.206.85.6:443
129.192.96.203:48477
130.206.85.6:443
HTTPS
24 sec.
262
0
Close - AGE OUT
Visto che per mandare le richieste utilizziamo un vostro client “metering-input-client-0.0.9.jar”
Ci servirebbe che generasse il LOG, per esempio per vedere quanto tempo di timeout aspetta per ricevere la risposta ed eventuali altre cose.
potete abilitare questo sul vostro client e rimandarlo ?
Grazie
M.
Da: Massimiliano Nigrelli massimiliano.nigrelli@eng.it
Inviato: venerdì 31 ottobre 2014 15:41
A: MASSIMILIANO LILI
Cc: Daniele Piferi; Pasquale.Andriani@eng.it<Pasquale.Andriani@eng.it>; Leandro Lombardo; dar >> Pellegrino Dario
Oggetto: Fwd: Re: [FINESCE WP4] Problems faced by external partners in connecting to a VM in FI-LAB
Ciao Massimiliano,
mi hanno risposto, come puoi vedere in calce.
Il nostro IP dovrebbe essere raggiungibile da qualsiasi parte del mondo (lui ha provato con un cellulare dal posto in cui si trova...........Spagna?).
Mi conferma che 130.206.85.6 non è raggiungibile da 172.30.5.18 e suggerisce di fare un tcptraceroute dalla macchina dove gira l'applicativo (quella che non raggiunge 130.206.85.6 per intenderci).
Last, but not least (the 2nd png) I'm aware that you can't access
130.206.85.6 from your private IP 172.30.5.18. But I don't know what is
the last step in the route to that host. So I can't reproduce that
error, may be some tcptraceroute output to that port could be helpful.
Tu ci hai mandato il tracelog del FW, ma non si vedono i vari punti di passaggio (HOPs).
Continuo a pensare che i pacchetti non escono dalla vostra LAN.
Aspetto di avere il "tcptraceroute" in maniera tale da girarlo a Josè il prima possibile.
Saluti,
Massimiliano
-------- Messaggio Inoltrato --------
Oggetto:
Re: [FINESCE WP4] Problems faced by external partners in connecting to a VM in FI-LAB
Data:
Fri, 31 Oct 2014 14:29:05 +0000
Mittente:
JOSE IGNACIO CARRETERO GUARDE <joseignacio.carreteroguarde@telefonica.com><joseignacio.carreteroguarde@telefonica.com>
A:
Massimiliano Nigrelli <massimiliano.nigrelli@eng.it><massimiliano.nigrelli@eng.it>, fiware-lab-help@lists.fi-ware.org<fiware-lab-help@lists.fi-ware.org> <fiware-lab-help@lists.fi-ware.org><fiware-lab-help@lists.fi-ware.org>
CC:
Pasquale.Andriani@eng.it<Pasquale.Andriani@eng.it> <Pasquale.Andriani@eng.it><Pasquale.Andriani@eng.it>, Leandro Lombardo <Leandro.Lombardo@eng.it><Leandro.Lombardo@eng.it>, Pellegrino Dario <Dario.Pellegrino@eng.it><Dario.Pellegrino@eng.it>
Dear Massimiliano,
The first .png file is a screenshot I've taken in my phone.... – My
phone using its 3G network connection, not Wifi or anything like that.
This means that the servicer with IP 130.206.85.6 is accessible from
everywhere.
—
I've seen in your email some "error messages": CLOSE AGE OUT — This is
a Juniper error message. May I ask what do your Juniper experts say
about this message? Sorry, but I don't know much about that software nor
the way you are using it to stablish your VPNs.
—
Last, but not least (the 2nd png) I'm aware that you can't access
130.206.85.6 from your private IP 172.30.5.18. But I don't know what is
the last step in the route to that host. So I can't reproduce that
error, may be some tcptraceroute output to that port could be helpful.
Thank you for forwarding your message to the list, that's the best way
to contact us.
Best regards,
José Ignacio.
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
–
===============================================================
Massimiliano Nigrelli - R&D Lab
Viale Regione Siciliana 7275 - 90146 Palermo (Italy)
Phone: +39 091.75.11.847
============================================================
–
===============================================================
Massimiliano Nigrelli - R&D Lab
Viale Regione Siciliana 7275 - 90146 Palermo (Italy)
Phone: +39 091.75.11.847
============================================================
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
–
===============================================================
Massimiliano Nigrelli - R&D Lab
Viale Regione Siciliana 7275 - 90146 Palermo (Italy)
Phone: +39 091.75.11.847
============================================================
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
| Field | Original Value | New Value |
|---|---|---|
| Assignee | José Ignacio Carretero Guarde [ jicg ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Component/s | FIWARE-LAB-HELP [ 10279 ] |
The external user is sending TCP Packets badly ordered – This makes the connection to be marked as "invalid" in Openstack Firewall and the packets are droped.
I've sent a .pcap file to them so they can see the problems.
The routes are working from everywhere in the internet.
| Resolution | Done [ 10000 ] | |
| Status | In Progress [ 3 ] | Done [ 10000 ] |
| Fix Version/s | Sprint 4.1.2 [ 10738 ] |
| Workflow | FW eRequest Workflow [ 18254 ] | FW extRequest Workflow-II [ 41099 ] |
| Status | Done [ 10000 ] | Closed [ 6 ] |
| Issue Type | eRequest [ 10101 ] | extRequest [ 10104 ] |
| FI-WARE Environment | FI-LAB [ 10100 ] |
| Sender Email | massimiliano.lili@ericsson.com |
| Summary | [Fiware-lab-help] Fwd: R: R: Re: [FINESCE WP4] Problems faced by external partners in connecting to a VM in FI-LAB | FIWARE.Request.Lab.Fwd: R: R: Re: Problems faced by external partners in connecting to a VM in FI-LAB. |
| HD-Node | Spain [ 10846 ] |
| Summary | FIWARE.Request.Lab.Fwd: R: R: Re: Problems faced by external partners in connecting to a VM in FI-LAB. | FIWARE.Request.Lab.Spain.Fwd: R: R: Re: Problems faced by external partners in connecting to a VM in FI-LAB. |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
2d 19h 35m | 1 | José Ignacio Carretero Guarde | 03/Nov/14 1:15 PM | |||||
|
9d 8h 16m | 1 | José Ignacio Carretero Guarde | 12/Nov/14 9:31 PM | |||||
|
425d 11h 39m | 1 | Manuel Escriche | 12/Jan/16 9:10 AM |
Dear Jose,
any news regarding the issue we reported on Friday?
What about a "joint" session where our external partners try to connect
to 130.206.85.6 so to let you see if they are able to "reach" the cloud
at least?
Regards,
Massimiliano
–
===============================================================
Massimiliano Nigrelli - R&D Lab
Viale Regione Siciliana 7275 - 90146 Palermo (Italy)
Phone: +39 091.75.11.847
============================================================
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help