-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS(LabelIsNotAscii) #13
Comments
What error message/source location do you get from the panic? I am surprised that UTF-8 has issues. |
I'm also running into this, but it's only panicing since I have an
|
I suspect this will have to be fixed in the upstream Either:
I suspect the first one is more likely. As far as I can see in |
Sort of related to this, but on the other end of the spectrum; while probing for elgato lights ( https://github.com/dylanmckay/mdns/blob/master/src/mdns.rs#L101
I appreciate that discovery doesn't completely give up for these because I do occasionally get proper responses from this, but I wonder if we can do something to control this unconditional output? Two ideas come to mind:
what do you think? |
Make the data integrity check how the data is interpreted; the check is for ascii only, but we can deal with UTF8, so relax a little and allow that. refs: dylanmckay/mdns#13
I forked dns-parser to make it handle utf8 in labels and that cured my immediate problem; the commits are referenced above |
Your wish is my command: 2.0.0...2.0.2 If you have any patches to send my way related to the other things, they are welcome :) |
Make the data integrity check how the data is interpreted; the check is for ascii only, but we can deal with UTF8, so relax a little and allow that. refs: dylanmckay/mdns#13
Make the data integrity check how the data is interpreted; the check is for ascii only, but we can deal with UTF8, so relax a little and allow that. refs: dylanmckay/mdns#13
Make the data integrity check how the data is interpreted; the check is for ascii only, but we can deal with UTF8, so relax a little and allow that. refs: dylanmckay/mdns#13
Make the data integrity check how the data is interpreted; the check is for ascii only, but we can deal with UTF8, so relax a little and allow that. refs: dylanmckay/mdns#13
Make the data integrity check how the data is interpreted; the check is for ascii only, but we can deal with UTF8, so relax a little and allow that. refs: dylanmckay/mdns#13
using the chromecast example but switching to
compantion-link._tcp.local
, some names panic. Not sure what the best course of action is, to support UTF-8 maybe?The text was updated successfully, but these errors were encountered: