Skip to main content
Accessibility Resource Center Skip to main content
Have a phone you love? Get up to $500 when you bring your phone.
end of navigation menu
Jetpack MHS291LVW blocking access to Amazon Elastic IPs used for AWS
TerryRayHumphries

The Jetpack blocks access to 54.67.38.190 a traceroute vener gets past 192.168.1.1

I can access the IP from other computer that connect to the Internet via other means.

0 Likes
Re: Jetpack MHS291LVW blocking access to Amazon Elastic IPs used for AWS
John_Getzke
Champion

I don't think the VZW network is blocking you.  I was able to hit that IP address from my Novatel 4510L.  Ping and tracert worked fine for me.  Anyone else out there able to confirm?

If for some reason VZW felt the need to block Amazon Web Services then the work around would be to setup a VPN to a network that doesn't.  That or pay for a static IP address from Verizon.

Are you getting any kind of application or browser error when trying to hit this particular IP?  Ping and tracert commonly communicate over ICMP which is blocked from responding on servers. Not being able to ping something does not mean there is actually a problem, just a clue that something is going on.

Re: Re: Jetpack MHS291LVW blocking access to Amazon Elastic IPs used for AWS
7e18n1
Specialist

YES, it works!

Pinging 54.67.38.190 with 32 bytes of data:
Reply from 54.67.38.190: bytes=32 time=276ms TTL=45
Reply from 54.67.38.190: bytes=32 time=122ms TTL=45
Reply from 54.67.38.190: bytes=32 time=131ms TTL=45
Reply from 54.67.38.190: bytes=32 time=123ms TTL=45

Ping statistics for 54.67.38.190:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 122ms, Maximum = 276ms, Average = 163ms

Tracing route to ec2-54-67-38-190.us-west-1.compute.amazonaws.com [54.67.38.190]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.2.1]
  2     1 ms     1 ms     1 ms  my.jetpack [192.168.1.1]
  3   324 ms    54 ms    58 ms  229.sub-66-174-115.myvzw.com [66.174.115.229]
  4    78 ms    53 ms    50 ms  36.sub-69-83-26.myvzw.com [69.83.26.36]
  5    67 ms    61 ms    49 ms  33.sub-69-83-27.myvzw.com [69.83.27.33]
  6    65 ms    57 ms    59 ms  66.sub-69-83-27.myvzw.com [69.83.27.66]
  7    62 ms    65 ms    52 ms  196.sub-69-83-17.myvzw.com [69.83.17.196]
  8     *        *        *     Request timed out.
  9    49 ms    42 ms    72 ms  129.sub-66-174-9.myvzw.com [66.174.9.129]
10    71 ms    60 ms    56 ms  TenGigE0-0-2-0.GW5.DCA5.ALTER.NET [152.179.65.73]
11    70 ms    83 ms    56 ms  0.ae2.BR1.IAD8.ALTER.NET [140.222.229.165]
12   204 ms   196 ms   178 ms  dcp-brdr-03.inet.qwest.net [63.146.26.105]
13   173 ms   118 ms   127 ms  snj-edge-04.inet.qwest.net [67.14.34.82]
14   116 ms   121 ms   111 ms  65.113.42.246
15     *        *        *     Request timed out.
16   131 ms   122 ms   120 ms  72.21.222.17
17   321 ms   129 ms   129 ms  ec2-54-67-38-190.us-west-1.compute.amazonaws.com [54.67.38.190]

Trace complete.

0 Likes