Can't communicate with 44.0.0.1 from 44-space? - 44net

10 Apr 2014

Hi,

I have a couple traces to share:

[eo@Seattle-ER1] > /tool traceroute address=44.0.0.1 
src-address=209.189.196.68
  # ADDRESS                          LOSS SENT    LAST     AVG BEST   
WORST STD-DEV STATUS
  1 209.189.196.65                     0%   10   1.9ms     0.8 0.4     
1.9 0.5
  2 209.189.202.195                    0%   10   0.7ms    73.1 0.4     
261 108.6
  3 206.81.80.99                       0%   10   0.7ms     5.1 0.5    
10.7 3.9
  4 69.28.171.145                      0%   10    28ms    26.6 20    
38.1 5.2
  5 69.28.171.210                      0%   10  22.8ms    21.4 18.6    
31.9 3.9
  6 198.32.176.33                      0%   10  21.6ms    19.5 19.1    
21.6 0.7
  7 137.164.47.19                      0%   10  21.4ms    24.1 21.4      
29 2
  8 137.164.46.67                      0%   10  25.1ms    25.1 23.6    
27.1 0.9
  9 137.164.46.244                     0%   10  34.7ms    33.5 32.4    
35.6 1.2
10 137.164.47.15                      0%   10  39.4ms    39.7 39.3    
41.5 0.6
11 137.164.23.54                      0%   10  39.7ms    40.2 39.5    
43.2 1
12 132.239.254.163                    0%   10  40.5ms    41.5 39.7    
49.1 2.7
13 132.239.255.131                    0%   10  39.6ms    40.2 39.6    
43.1 1
14 44.0.0.1                          10%   10  39.7ms    39.9 39.6    
40.5 0.3

[eo@Seattle-ER1] > /tool traceroute address=44.0.0.1 
src-address=44.24.242.22
  # ADDRESS                          LOSS SENT    LAST     AVG BEST   
WORST STD-DEV STATUS
  1 209.189.196.65                     0%    5   0.7ms     1.3 0.5     
2.5 0.7
  2 209.189.201.195                    0%    5   3.5ms     1.5 0.5     
3.5 1.2
  3 206.81.80.99                       0%    4   0.4ms     4.1 0.4     
8.1 3.5
  4 69.28.171.145                      0%    4  25.7ms    24.7 19.6    
29.6 3.6
  5 69.28.171.210                      0%    4  34.7ms    25.3 21.5    
34.7 5.5
  6 198.32.176.33                      0%    4  19.5ms    20.4 19.3    
23.2 1.6
  7 137.164.47.19                      0%    4  23.7ms    23.6 21.9    
25.4 1.3
  8 137.164.46.1                       0%    4  24.4ms    26.3 24.4    
27.5 1.2
  9 137.164.46.248                     0%    4  36.1ms    33.8 32.1    
36.1 1.5
10 137.164.47.111                     0%    4  42.9ms    40.3 39.1    
42.9 1.6
11 137.164.23.54                      0%    4  41.2ms    45.8 39.8    
61.6 9.1
12                                  100%    4 timeout
13                                  100%    4 timeout
14                                  100%    4 timeout
15                                  100%    4 timeout
16                                  100%    4 timeout

They'll look like crap without monospace font, and I don't wanna use 
HTML cuz the content of my message will be torn out of the email and 
replaced with a web link.  So, adjust your fonts + screen size 
accordingly to properly view the traces.

The only difference between them is the source address.  Both addresses 
are bound to that router.  That router holds IPIP tunnels to every 
ENCAP.txt network.  Since 44.0.0.1 is not one of these networks, there 
is no tunnel that covers that IP, so the packets go over the regular 
internet.  We BGP announce 44.24.242.22, so the trace from that IP 
should succeed in theory.

Can someone explain what's breaking here and how to fix it?

Thanks,

--Bart