New subject: 44 net connectivity problems ?

16 Jun 2017

I concur with Charles.

Exactly the same I obswerve on my Windows 7/64b __NOT 44-net aware__

Cable ISP Vectra, Poland.

Tracing route to net.vk2hff.ampr.org [44.136.24.60]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1 
  2     5 ms     6 ms     7 ms  10.149.64.1 
  3     6 ms     7 ms     8 ms  172.20.253.1 
  4    12 ms    13 ms    13 ms  172.17.0.249 
  5    12 ms    11 ms    14 ms  172.17.0.250 
  6    14 ms    12 ms    18 ms  172.17.0.133 
  7    12 ms    14 ms    13 ms  172.17.28.238 
  8    13 ms    13 ms    13 ms  172.17.28.238 
  9    27 ms    14 ms    12 ms  ae48-48.r7.poland-rs.thinx.atman.pl [212.91.0.10] 
 10    40 ms    42 ms    46 ms  limelight.plix.pl [195.182.218.35] 
 11   148 ms   147 ms   149 ms  lag23.fr4.ord.llnw.net [68.142.88.56] 
 12   166 ms   171 ms   167 ms  68.142.88.147 
 13   187 ms   187 ms   188 ms  68.142.88.155 
 14   187 ms   187 ms   188 ms  lag7.fr4.aza1.llnw.net [68.142.64.50] 
 15   189 ms   188 ms   189 ms  tge1-1.fr3.aza1.llnw.net [69.164.62.16] 
 16   198 ms   201 ms   198 ms  lag16.fr3.lax.llnw.net [69.28.189.233] 
 17   201 ms   197 ms   197 ms  198.32.251.189 
 18   200 ms   198 ms   199 ms  dc-tus-agg3--lax-agg6-100ge.cenic.net [137.164.11.7] 
 19   201 ms   201 ms   202 ms  dc-sdg-agg4--tus-agg3-100ge.cenic.net [137.164.11.9] 
 20   226 ms   202 ms   203 ms  dc-ucsd-1--sdg-agg4.cenic.net [137.164.23.54] 
 21   202 ms   202 ms   203 ms  nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 
 22   203 ms   203 ms   203 ms  rci-nodem-p2p.ucsd.edu [132.239.254.177] 
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Next test with IP address 44.139.11.30 assigned from AMPRNet VPN:

Tracing route to net.vk2hff.ampr.org [44.136.24.60]
over a maximum of 30 hops:

  1    57 ms    57 ms    57 ms  dyn1.oh-vpn.ampr.org [44.139.11.1] 
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20   474 ms   478 ms   470 ms  net.vk2hff.ampr.org [44.136.24.60] 

Trace complete.

Yet another test, with IP address 44.165.15.17 assigned from SP2L VPN:

Tracing route to net.vk2hff.ampr.org [44.136.24.60]
over a maximum of 30 hops:

  1    74 ms    77 ms    71 ms  avpn1.sp2l.ampr.org [44.165.15.1] 
  2   565 ms   549 ms   549 ms  net.vk2hff.ampr.org [44.136.24.60] 

Trace complete.

One more test, with IP address 44.137.40.185 assigned from Netherland's VPN:

Tracing route to net.vk2hff.ampr.org [44.136.24.60]
over a maximum of 30 hops:

  1    42 ms    44 ms    43 ms  gw-44-137.pi9noz.ampr.org [44.137.0.1] 
  2   467 ms   474 ms   475 ms  vk2hff.ampr.org [44.136.24.60] 

Trace complete.

Best regards.
Tom - SP2L

Re: [44net] 44 net connectivity problems ?