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

[Jan Kundrát]

On Monday, 19 May 2014 12:32:37 CEST, José Ignacio Carretero Guarde wrote:
> It seems that somewhere in the european Backbone (62.40.102.15) didn't
> find FI-LAB's 10.0.0.1

I don't think that the problem is in the GEANT's infrastructure because the 
CESNET node can reach 10.0.0.1 just fine:

[root at potemkin02 ~]# tracepath 10.0.0.1
 1:  10.0.96.132 (10.0.96.132)                              0.102ms pmtu 
9100
 1:  no reply
 2:  62.40.124.41 (62.40.124.41)                            1.117ms 
 3:  62.40.124.41 (62.40.124.41)                            0.951ms pmtu 
1488
 3:  no reply
 4:  ae2.mx1.fra.de.geant.net (62.40.98.53)                34.688ms asymm 
17 
 5:  ae1.mx1.ams.nl.geant.net (62.40.98.129)               35.294ms asymm 
16 
 6:  ae2.mx1.lon.uk.geant.net (62.40.98.80)                34.594ms asymm 
15 
 7:  ae7.mx1.dub.ie.geant.net (62.40.98.92)                35.314ms asymm 
14 
 8:  ae1.mx2.dub.ie.geant.net (62.40.98.91)                34.577ms asymm 
13 
 9:  62.40.102.15 (62.40.102.15)                           34.417ms asymm 
11 
10:  10.0.0.1 (10.0.0.1)                                   34.288ms reached
     Resume: pmtu 1488 hops 10 back 246

In fact, 10.0.0.1 is visible within the trace towards 10.0.3.45 -- see hop 
#10:

[root at potemkin02 ~]# tracepath 10.0.3.45
 1:  10.0.96.132 (10.0.96.132)                              0.142ms pmtu 
9100
 1:  no reply
 2:  62.40.124.41 (62.40.124.41)                            1.060ms 
 3:  62.40.124.41 (62.40.124.41)                            1.006ms pmtu 
1488
 3:  no reply
 4:  ae2.mx1.fra.de.geant.net (62.40.98.53)                34.700ms asymm 
17 
 5:  ae1.mx1.ams.nl.geant.net (62.40.98.129)               34.593ms asymm 
16 
 6:  ae2.mx1.lon.uk.geant.net (62.40.98.80)                34.572ms asymm 
15 
 7:  ae7.mx1.dub.ie.geant.net (62.40.98.92)                34.771ms asymm 
14 
 8:  ae1.mx2.dub.ie.geant.net (62.40.98.91)                34.544ms asymm 
13 
 9:  62.40.102.15 (62.40.102.15)                           34.359ms asymm 
11 
10:  10.0.0.1 (10.0.0.1)                                   34.424ms 
11:  no reply

Despite that, I cannot ping 10.0.3.45 from 10.0.96.132. I can ping 
10.0.0.1, though.

With kind regards,
Jan

-- 
Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/