I use a web server to configure my application over WiFi. Normally it works fine with Core2 and Core3SE but not with Core2 AWS. Trying with both the old Core2 API and the new Unified.
Symptoms:
Launch config web server with my own SSID with IP address 192.168.5.1.
The laptop (Linux Mint) connects and acquires 192.168.5.2.
Connect with Firefox to http://192.168.5.1 and the config page appears. So far so good.
Fill out the config page parameters and submit the form.
The page never comes back.
A quick check of networking shows that the linux arp layer seems to have lost the hardware address. At first, I get the right answer, but after the form submission, the HW address comes back as <incomplete>.
This is observed with both the original Core2 API and with the new unified API.
Any suggestions? Other experiments?
Thanks
Subcategories
-
49
Topics235
Posts -
82
Topics326
Posts -
62
Topics223
Posts -
M5 Stick/StickC
M5Stack's little brother. Discuss M5 Stick hardware and software related issues here
374
Topics1.5k
Posts -
17
Topics70
Posts -
27
Topics114
Posts -
47
Topics127
Posts -
316
Topics1.4k
Posts