Forum Moderators: phranque

Message Too Old, No Replies

Does FB interact with IOT devices?

Using MQTT? I think they do...

         

SumGuy

2:41 pm on Apr 20, 2021 (gmt 0)

5+ Year Member Top Contributors Of The Month



I'm not quite sure what I'm seeing here. Today I see 15 attempts from a Fecebook IP to contact something on my office LAN I think around 10 pm local time last night (and looking back, also seeing 8 attempts on April 13, but no others).

The source IP was 69.171.250.34 which is edge-mqtt-mini-shv-01-any2.facebook.com.

Seeing mqtt in the host name is interesting.

The source port was 443. The destination port was 43160 (on April 13 it was 40388).

The destination ports may have no bearing on this if this was an attempt to get through a router using a NAT keep-alive strategy. My router blocked these as a WAN-IN drop (I think an unsolicited packet).

I don't run an mqtt server, but I do have a couple of devices that I've flashed with Tasmota but don't have them configured to use MQTT. There is possibly 1 user at the office that may interact with FB on their desktop computer or phone, but otherwise interacting with FB on any device in the office is going to be pretty rare (reinforced through host-file entries on most PC's).

Those of you that look strictly at web logs (ports 80 and 443) wouldn't see traffic like this, it would only be seen in your router.

Does FB indeed have mqtt interoperability with user devices? And if so, how or why would FB be knocking on my door this way?

lammert

3:06 pm on Apr 20, 2021 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



MQTT is used by Facebook messenger.

SumGuy

11:32 pm on Apr 20, 2021 (gmt 0)

5+ Year Member Top Contributors Of The Month



Alright, this was a false alarm. An apple guy at the office has a backup android phone that he misplaced a week ago, one that has the FB app that he can't delete (apparently) and has never been used but this phone nonetheless must have periodic contact with FB / messenger and what I saw in the logs were fragments of broken exchanges with the messenger server. At least that's the best explanation so far.