-
Notifications
You must be signed in to change notification settings - Fork 34
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
Couldn't parse packet type 47 is invalid #19
Comments
Hm, atm we're vendoring an old version dns-parser, probably about time we switched, to something maintained. Candidates are probably: https://crates.io/crates/trust-dns-proto and https://crates.io/crates/dns-message-parser I might also investigate using a higher-level library like https://crates.io/crates/trust-dns-client making libmdns be a completely minimal wrapper to simplify usage. |
Ah, I was under the impression it was a written by @plietar back in the day, but now see it's actually a fork of Wouldn't it be less work to just add this record into libmdns/src/dns_parser/enums.rs Lines 7 to 10 in e63275f
And since we ( |
I'll have to check but I'd assumed we already ignoring this packet, so all that would do is stop the logging (which is probably helpful anyway). The original issue is about a failure in the discovery of the librespot service, which implies this 47 might be something to respond to. |
@willstott101 i may have misdiagnosed the issue, as i thought this message was breaking things for me. |
I am still getting these error messages.
|
So do I. Those messages started when I moved my snapserver, which uses librespot, to another VLAN/subnet. |
I got rid of the problem by switching to avahi in librespot. |
@2opremio could you explain how? |
Enable the |
@2opremio Thank you in advance |
It’s a Cargo feature. There are lots of tutorials about how to build Rust projects on the web. |
I've not confirmed this is fixed - didn't intend github to auto close it. |
I would appreciate it if someone affected by this could test that the current If that doesn't work, a copy of one of these packets would also be very helpful. |
Hi there, I'm using librespot, a Spotify API player, that communicates to other devices via mdns. If I compile the package with libmdns version=0.6 I'm getting spammed with warnings, as other devices (smart IOT power plugs in my case) use this packet type 47. If I compile it with version=0.7 I get no warnings at all, while previously about >1000 daily warning messages ended in my journal :)) |
That's great. Thanks for confirming, and for the librespot PR. |
This should fix issues with libmdns not being able to resolve packages from other network subnets. As described here librespot-org/libmdns#19
This should fix issues with libmdns not being able to resolve packages from other network subnets. As described here librespot-org/libmdns#19
Creating bug at request of: librespot-org/librespot#545
running librespot separately like:
/usr/bin/librespot --name Snapcast --bitrate 320 --backend pipe --initial-volume 100 --verbose
Yields:
this currently breaks librespot and should be addressed. From @ashthespy:
The text was updated successfully, but these errors were encountered: