Another v1 endpoint

[MitchBradley]

FYI, we discovered that a Google Wifi network was issuing the URI /api/v1/interap-communications periodically, interfering with a device that listens for requests on port 80. That is all we know about it.

[knwpsk]

Just a dumb, curious question:
What do you mean, "issuing the uri... periodically" ?
Do you mean that the google wifi node is publishing some sort of message?
Or do you mean that that uri is available, but only available sometimes, not all the time?

[MitchBradley]

I mean that the Google Wifi node is trying to access a web page on the FluidNC device, as if the node were a browser. Using pseudo-web-pages like that is a modern form of inter-device communication. It is often called a "REST API", although, strictly speaking "REST" means something slightly more specific.

In this case, what is probably happening is that the Google Wifi nodes are trying to find each other, or more specifically are periodically checking to see if another such node might have joined the network. It is like they are saying "hi, could you by any chance be another one of us? If so, we can add you to our mesh.".

[knwpsk]

Now I see.
What's "the FluidNC device" ?

[MitchBradley]

Oh, sorry, I wasn't paying attention and thought that this was a corresponding issue on our FluidNC repo. FluidNC is CNC machine control firmware that runs on an ESP32 wifi microcontroller. It exposes a web server on port 80 that is used as a control panel for the CNC machine. We were having problems caused by the unexpected URI /api/v1/interap-communication that was coming in from who-knows-where. One of our users tracked the request source to a Google Wifi node.