-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
parsing multicast-dns responses results in unreachable device #32
Comments
I added this code, which seems to make it work for me: if (a.type === 'A') {
var aName = name.replace('.local', '');
Object.keys(casts).forEach(function (castName) {
if (castName.indexOf(aName) > -1) {
casts[castName].host = a.data;
}
});
} |
I have also encountered this issue.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I use this module, I get an
ETIMEDOUT
error connecting to a strange IP address198.105.244.228
. The real IP of my chromecast on my network, however, is192.168.1.105
. I did a bit of investigation and found that the host which is parsed from the multicast-dns results is072d136d-9716-69e2-2758-36bf56482f43.local
, and when I do adns.lookup()
on it, sure enough, it resolves to that strange IP address.Looking a bit further, I saw what appears to be the issue in the multicast-dns responses. On my network, the answers and additionals that I get are these:
Looks like there is an A type additional that has the correct IP address. However, this additional is never even looked at. The SRV additional which is used has
data.target
strange address which resolves to the strange IP.When I overload the
player.host
with the correct IP, the module works well and can cast media. However, since the A additional uses differentname
than the one in the rest of the additionals (and the one used to store cast devices), I am not totally sure how to fix it, since I don't know what other dns responses look like (since I assume this works well on other people's networks).The text was updated successfully, but these errors were encountered: