Birdseye & Geocaching.com not working
Posted: Fri Nov 12, 2021 8:27 am
Hi,
First I have to say that I already submitted this information to Garmin, so this message is just to hear from others if they experience the same problems and making my information available to them.
The problem is that the Birdseye Imagery has never worked since I bought the device last week. Reset done, no solution, different networks, no solution ...
The second problem is that I never managed to get a registration code for the Geocaching.com site. When I try it from my device, i always get a 'Registration Failed' message.
So after trying a lot of things and submitting my problem to Garmin Tech Support, they weren't able to help me so far. Since i'm working in the IT business, I was able to capture the network traffic between my Garmin and the servers, and guess what, both Birdseye & Geocaching are hosted on the same Akamai infrastructure, so the same server is used for both. That makes sense as both items are not working for me.
So I captured the traffic, and i'll explain shortly what's happening here so everyone can see the problem :
Birdseye Imagery Problem :
Connection is tried to : (Hostname: a88-221-180-177.deploy.static.akamaitechnologies.com)
1 0.000000 10.10.10.44 88.221.180.177 TCP 109 50627 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
Connection is acknowledged to the garmin device :
2 0.024421 88.221.180.177 10.10.10.44 TCP 109 443 → 50627 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 WS=128
Garmin device acknowledges the answer from the server :
3 0.026076 10.10.10.44 88.221.180.177 TCP 107 50627 → 443 [ACK] Seq=1 Ack=1 Win=262140 Len=0
Garmin device sends a 'hello' to let the server know the data can be transferred :
4 0.404111 10.10.10.44 88.221.180.177 TLSv1 259 Client Hello
Server sends first packet :
5 0.411774 88.221.180.177 10.10.10.44 TCP 101 443 → 50627 [ACK] Seq=1 Ack=159 Win=64128 Len=0
Server sends a handshake failure error :
6 0.413347 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
devices acknowledges the error and sends the necessary acks and finishes the connection
This time the device sets up a new connection :
10 0.468903 10.10.10.44 88.221.180.177 TCP 109 50628 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
The server acknowledges the connection request :
11 0.493720 88.221.180.177 10.10.10.44 TCP 101 443 → 50627 [ACK] Seq=9 Ack=160 Win=64128 Len=0
The server acknowledges the connection setup and the garmin too
The garmin sends a new message that it is ready for data transfer, this time in TLSv1.2 as the TLSv1 did not work :
14 1.022909 10.10.10.44 88.221.180.177 TLSv1.2 259 Client Hello
Again, the server sends a handshake failure message, so also TLSv1.2 doesn't work :
16 1.023155 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
From this point, the same process goes on and on, every time a new connection is tried with TLSv1.2 but the server returns a handshake failure.
Geocaching.com problem :
Connection is tried to the same Akamai server as the birdseye :
1 0.000000 10.10.10.44 88.221.180.177 TCP 109 50705 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
The same handshake failure as with the birdseye is happening :
6 0.614230 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
As you can see, there is definitely a problem with the handshaking, a protocol issue, certificate issue in the garmin devices .... ????
Regards,
Bart
First I have to say that I already submitted this information to Garmin, so this message is just to hear from others if they experience the same problems and making my information available to them.
The problem is that the Birdseye Imagery has never worked since I bought the device last week. Reset done, no solution, different networks, no solution ...
The second problem is that I never managed to get a registration code for the Geocaching.com site. When I try it from my device, i always get a 'Registration Failed' message.
So after trying a lot of things and submitting my problem to Garmin Tech Support, they weren't able to help me so far. Since i'm working in the IT business, I was able to capture the network traffic between my Garmin and the servers, and guess what, both Birdseye & Geocaching are hosted on the same Akamai infrastructure, so the same server is used for both. That makes sense as both items are not working for me.
So I captured the traffic, and i'll explain shortly what's happening here so everyone can see the problem :
Birdseye Imagery Problem :
Connection is tried to : (Hostname: a88-221-180-177.deploy.static.akamaitechnologies.com)
1 0.000000 10.10.10.44 88.221.180.177 TCP 109 50627 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
Connection is acknowledged to the garmin device :
2 0.024421 88.221.180.177 10.10.10.44 TCP 109 443 → 50627 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 MSS=1460 WS=128
Garmin device acknowledges the answer from the server :
3 0.026076 10.10.10.44 88.221.180.177 TCP 107 50627 → 443 [ACK] Seq=1 Ack=1 Win=262140 Len=0
Garmin device sends a 'hello' to let the server know the data can be transferred :
4 0.404111 10.10.10.44 88.221.180.177 TLSv1 259 Client Hello
Server sends first packet :
5 0.411774 88.221.180.177 10.10.10.44 TCP 101 443 → 50627 [ACK] Seq=1 Ack=159 Win=64128 Len=0
Server sends a handshake failure error :
6 0.413347 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
devices acknowledges the error and sends the necessary acks and finishes the connection
This time the device sets up a new connection :
10 0.468903 10.10.10.44 88.221.180.177 TCP 109 50628 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
The server acknowledges the connection request :
11 0.493720 88.221.180.177 10.10.10.44 TCP 101 443 → 50627 [ACK] Seq=9 Ack=160 Win=64128 Len=0
The server acknowledges the connection setup and the garmin too
The garmin sends a new message that it is ready for data transfer, this time in TLSv1.2 as the TLSv1 did not work :
14 1.022909 10.10.10.44 88.221.180.177 TLSv1.2 259 Client Hello
Again, the server sends a handshake failure message, so also TLSv1.2 doesn't work :
16 1.023155 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
From this point, the same process goes on and on, every time a new connection is tried with TLSv1.2 but the server returns a handshake failure.
Geocaching.com problem :
Connection is tried to the same Akamai server as the birdseye :
1 0.000000 10.10.10.44 88.221.180.177 TCP 109 50705 → 443 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=4
The same handshake failure as with the birdseye is happening :
6 0.614230 88.221.180.177 10.10.10.44 TLSv1.2 108 Alert (Level: Fatal, Description: Handshake Failure)
As you can see, there is definitely a problem with the handshaking, a protocol issue, certificate issue in the garmin devices .... ????
Regards,
Bart