esp8266 calling out to micropython.org

General discussions and questions abound development of code with MicroPython that is not hardware specific.
Target audience: MicroPython Users.
Post Reply
jrichard82
Posts: 9
Joined: Sat Mar 28, 2020 4:56 pm

esp8266 calling out to micropython.org

Post by jrichard82 » Sat Mar 28, 2020 5:01 pm

I am seeing some strange behavior on my esp8266. At random hours the board (flashed with the latest version of MicroPython )is calling out to MicroPython.org and sending data to servers in Linode. What is the purpose of this? Is there and option to disable this?

User avatar
jimmo
Posts: 2754
Joined: Tue Aug 08, 2017 1:57 am
Location: Sydney, Australia
Contact:

Re: esp8266 calling out to micropython.org

Post by jimmo » Mon Mar 30, 2020 1:01 am

That's quite surprising?

micropython.org is hosted at Linode, and the only thing I can think of is that upip will look for packages at micropython.org. But this would definitely not be happening in the background.

Any chance you have any additional information about what the payloads look like? i.e. is it HTTP, what's the path, subdomain, content?

jrichard82
Posts: 9
Joined: Sat Mar 28, 2020 4:56 pm

Re: esp8266 calling out to micropython.org

Post by jrichard82 » Mon Mar 30, 2020 4:53 am

jimmo, thanks for the response. I think you solved the mystery. I dug through the sources and the only place I saw that was hitting micropython was upip. I went back through my logs and the activity *may* have been associated with a upip install but I can't remember. I havent been seeing the activity today....

Thanks again.

.[2020-03-27 12:37:17,010] INFO in server: wlan1 : 75 B xx:xx:xx:xx:xx:xx => xx:xx:xx:xx:xx:xx [IPv4] 192.168.2.12 => 192.168.2.1 [UDP] 4096 => 53 [DNS QUERY] micropython.org
[2020-03-27 12:37:17,034] INFO in server: wlan1 : 91 B xx:xx:xx:xx:xx:xx => xx:xx:xx:xx:xx:xx [IPv4] 192.168.2.1 => 192.168.2.12 [UDP] 53 => 4096 [DNS RESPONSE]
[2020-03-27 12:37:17,047] INFO in server: wlan1 : 58 B xx:xx:xx:xx:xx:xx => xx:xx:xx:xx:xx:xx [IPv4] 192.168.2.12 => 176.58.119.26 [TCP] 21439 => 443 => (Linode, LLC)
[2020-03-27 12:37:17,182] INFO in server: wlan1 : 58 B xx:xx:xx:xx:xx:xx => xx:xx:xx:xx:xx:xx [IPv4] 176.58.119.26 => 192.168.2.12 [TCP] 443 => 21439 <= (Linode, LLC)
[2020-03-27 12:37:17,189] INFO in server: wlan1 : 54 B xx:xx:xx:xx:xx:xx => xx:xx:xx:xx:xx:xx [IPv4] 192.168.2.12 => 176.58.119.26 [TCP] 21439 => 443 => (Linode, LLC)
[2020-03-27 12:37:17,231] INFO in server: wlan1 : 150 B xx:xx:xx:xx:xx:xx => xx:xx:xx:xx:xx:xx [IPv4] 192.168.2.12 => 176.58.119.26 [TCP] 21439 => 443 => (Linode, LLC)
[2020-03-27 12:37:17,392] INFO in server: wlan1 : 54 B xx:xx:xx:xx:xx:xx => xx:xx:xx:xx:xx:xx [IPv4] 176.58.119.26 => 192.168.2.12 [TCP] 443 => 21439 <= (Linode, LLC)
[2020-03-27 12:37:17,399] INFO in server: wlan1 : 590 B xx:xx:xx:xx:xx:xx => xx:xx:xx:xx:xx:xx [IPv4] 176.58.119.26 => 192.168.2.12 [TCP] 443 => 21439 <= (Linode, LLC)
[2020-03-27 12:37:17,406] INFO in server: wlan1 : 590 B xx:xx:xx:xx:xx:xx => xx:xx:xx:xx:xx:xx [IPv4] 176.58.119.26 => 192.168.2.12 [TCP] 443 => 21439 <= (Linode, LLC)

Post Reply