Skip to content

Updated the sed command#30

Merged
cbrand merged 1 commit intocbrand:mainfrom
joncard1:docker-rp2-fix
Jan 19, 2025
Merged

Updated the sed command#30
cbrand merged 1 commit intocbrand:mainfrom
joncard1:docker-rp2-fix

Conversation

@joncard1
Copy link
Copy Markdown

Without the "-i" switch, the underlying file is not affected, and the "$" introduced a typo in the C file.

Without the "-i" switch, the underlying file is not affected, and the "$" introduced a typo in the C file.
@joncard1
Copy link
Copy Markdown
Author

I tested this on my Pico in version 1.22, 1.23, and 1.24, with some complicated results. My test application doesn't simplify well; it creates an access point, advertises a service over mDNS, then starts a simple HTTP server. In version 1.22 and 1.23, I was able to connect my Windows 11 desktop to the AP and open a web browser to the hostname of the Pico and it retrieved the page. In 1.24, I was able to run the application with getting an error, but the desktop was not able to connect at the name, but was able to connect to web server at the IP address. However, I was able to verify port 5353 was open, but I'm not knowledgeable enough about mDNS to actually see why the Windows desktop wasn't able to resolve the name. I can keep looking, but please let me know if you have a better way of confirming the behavior of a Pico running this library on Micropython 1.24.

@cbrand
Copy link
Copy Markdown
Owner

cbrand commented Jan 19, 2025

Hey thank you for the patch and testing.

I do by now have a raspberry pi pico and try 1.24 out with your patch to see if I run in the same problem.
What you could do is to see on Wireshark on your windows device the mdns packets by filtering for port 5353 and could see if the pico at all sends any mdns data or not.

@cbrand cbrand merged commit 6791b3e into cbrand:main Jan 19, 2025
@cbrand
Copy link
Copy Markdown
Owner

cbrand commented Jan 19, 2025

After playing a bit around with 1.24 it seems like something in the network stack changed.

Binding to a socket without an IP address does no longer work / allow to send packages to the network respectively.

After updating the bind parameters it does work with 1.24 but not on an ESP32 before 1.22.

Realistically nobody needs any build without the newest version though, so I am doing a release an dropping support for everything before 1.24 and not adding a backwards compatibility check / hack into the codebase.

cbrand added a commit that referenced this pull request Jan 19, 2025
As reported in #30 there were issues even after the patches wtih the 1.24 version of resolving MDNS. This was due to the socket binding not being bound to the MDNS address. Both on the ESP32 and the RP2 with 1.24 binding works now again.

To not have a backwards issue with the code base, dropping support for anything older than 1.24 in this commit and in the next release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants