Update with mDNS support #20
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A simple deployment of mDNS allows accessing OnStep controller in a network with a user friendly DNS name instead of IP address. The host mDNS name is configurable while domain part depends on the network - usually it would be .local. Avahi / Bonjour daemons in Windows 10/11, Mac OS X and most Linux distributions work fine with this mDNS implementation.
Smart Web Server works well in both modes (access point and station) - tested on ESP32 and ESP32C3 in version 2.06k with Windows 10, Windows 11, Mac OS X and Ubuntu 22.04.
(known issue) Unfortunately, this deployment of mDNS doesn't work properly in SWS based on ESP8266 - as of now unsupported, might need to be further investigated.