help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unidentified outbound traffic to Fitbit.com on WiFi

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎04-11-2020 08:43 - last edited on ‎10-27-2020 12:40 by Fitbit Moderator

‎04-11-2020 08:43 - last edited on ‎10-27-2020 12:40 by Fitbit Moderator

I am trying to identify the device/source of outbound traffic for the following endpoint on my home WiFi/router.

1. Established outbound connections from this source:
    a. 162.159.192.6:2408      UDP 2408 Cloudflair
    b. 104.16.66.50:443
    c. 104.16.65.50:443          api.fitbit.com.cdn.cloudflare.net
2. 192.168.X.117 = source IP, random DHCP assignment (all other internal nodes on WiFi are statically defined by their respective MAC address)
3. b2:93:a0:ed:b4:6f = source MAC for this endpoint, this is an unregistered MAC not found on any web lookup resource to identify manufacturer or OEM
4. I have two Versa Fitbits in this household, one is an SE and one is a 2
    a. both are paired to Android phones that have their own static IPs assigned to each, not .117
    b. neither Versa has WiFi enabled
5. The endpoint at 192.168.X.117 responds to Ping, but port scanning comes up with no response to any requests for connection, effectively stealth other than Echo Reply

 

Anyone have an insight for what this internal-home-network endpoint might be?

Thanks

Dave

 

Moderator Edit: Clarified subject

Best Answer
Labels:
0 Votes
0 REPLIES 0