[Fiware-lab-help] MD-VPN issues at FI-LAB 10.0.3.45/21

José Ignacio Carretero Guarde jicg at tid.es
Mon May 19 12:32:37 CEST 2014


Hi,

It seems that somewhere in the european Backbone (62.40.102.15) didn't
find FI-LAB's 10.0.0.1

Best regards,
José Ignacio.

El 19/05/14 12:03, Jan Kundrát escribió:
> Hi,
> I created a testing VM in the FI-LAB region. The VM got assigned a
> private IPv4 address of 10.0.3.45, and I also added a floating IP
> 130.206.83.11. I can access the public IPv4 just fine, but it seems
> that the private, XIFI-federated IPv4 range is having some troubles.
>
> Here's how a tracepath looks from one of our nodes at CESNET:
>
> [root at potemkin02 ~]# tracepath 10.0.3.45                     1:
> 10.0.96.132 (10.0.96.132)                              0.138ms pmtu
> 9100                             1:  no reply
> 2:  62.40.124.41 (62.40.124.41)                            1.049ms
>                          3:  62.40.124.41
> (62.40.124.41)                            0.983ms pmtu 1488
>                             3:  no reply                          4:
> ae2.mx1.fra.de.geant.net (62.40.98.53)                34.677ms asymm
> 17                            5:  ae1.mx1.ams.nl.geant.net
> (62.40.98.129)               34.591ms asymm 16
>                            6:  ae2.mx1.lon.uk.geant.net
> (62.40.98.80)                34.565ms asymm 15
>                            7:  ae7.mx1.dub.ie.geant.net
> (62.40.98.92)                34.530ms asymm 14
>                            8:  ae1.mx2.dub.ie.geant.net
> (62.40.98.91)                34.546ms asymm 13
>                            9:  62.40.102.15
> (62.40.102.15)                           34.323ms asymm 11
>                            10:  10.0.0.1
> (10.0.0.1)                                   34.403ms
>                          11:  no reply                          12:
> no reply                          13:  no reply
>                          14:  no reply                          15:
> no reply                          16:  no reply
>                          17:  no reply                          18:
> no reply                          19:  no reply
>                          20:  no reply                          21:
> no reply                          22:  no reply
>                          23:  no reply                          24:
> no reply                          25:  no reply
>                          26:  no reply                          27:
> no reply
>
> In contrast, this is how a testing tracepath looks from the VM I
> launched:
>
> [root at test-el6-1 ~]# traceroute 10.0.96.1
> traceroute to 10.0.96.1 (10.0.96.1), 30 hops max, 60 byte packets
> 1  10.0.0.1 (10.0.0.1)  20.300 ms  20.272 ms  20.243 ms
> 2  130.206.82.1 (130.206.82.1)  29.885 ms  29.851 ms  29.832 ms
> 3  130.206.82.1 (130.206.82.1)  2936.241 ms !H  2936.227 ms !H
> 2936.205 ms !H
>
> Could you please confirm that this is expected to work? Unfortunately,
> the information about the allocation and utilization of the XIFI-wide
> federated IPv4 space is rather scarce in varioud public deliverables.
> It's well possible that this use case is not supposed to work at all.
> Could you please clarify that?
>
> With kind regards,
> Jan
>


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx



More information about the Fiware-lab-help mailing list

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