-
Notifications
You must be signed in to change notification settings - Fork 14
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
Service Discovery returns garbage data #20
Comments
ah, the randomness was because our arrays were never initialized
changing them to
gives me port "0" instead of randomness, so indeed the packet parsing code is broken somewhere... |
I think I found the source of the bug now. There is simply no code at all that populates ptrPorts or servTxt until we get to the "additional records" part of the packet. But, port and text are not "additional records". They are "query answers". This is a pretty big control flow problem and I am not sure how to fix it yet since the code is so hard to understand still. |
After spending 12 hours digging into the code, I don't think there is any way for an arduino to ask for TXT query. I was watching the raw packet data coming in through the UDP buffer and nothing seemed to me like a txt response. --wait--, I just saw the strings. i'll try writing a packet filter to capture it |
When I use one arduino to generate an MDNS service, and another arduino to listen to the service...
It seems like adding the service record is OK, as on my host computer, I don't have issues reading the text data,
...but the service discovery on arduino is very broken?
The text was updated successfully, but these errors were encountered: