Tinysvcmdns invisible from chrome app mdns-browser #5

New Issue

df · 2020-07-18T22:29:52Z

df commented

2020-07-18 22:29:52 +00:00

b6i6o6 (2015-07-15) reporter

I've been trying to advertise a _http._tcp.local service using tinysvcmdns and retrieve it from the chrome app mdns-browser. (https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/mdns-browser)

Unfortunately, my service is invisible in mdns-browser.

I am unable to figure out if the issue comes from tinysvcmdns or from the mdns-browser chrome app, since the tinysvcmdns service is visible from Safari, but my network printer is visible from mdns-browser, so both seem to be working to an extent.

I have enabled the debug mode in tinysvcmdns so I see that tinysvcmdns is responding to the mdns query as it says "added 1 answers" in the debug output, but I also added a simple console.log to display the ip addresses of each packet received by mdns-browser (console.log(info.remoteAddress) at https://github.com/GoogleChrome/chrome-app-samples/blob/master/samples/mdns-browser/main.js#L132), and it seems mdns-browser never receives the answer packet sent by tinysvcmdns.

What would point more to tinysvcmdns than mdns-browser is that if I install avahi-utils and register a service using avahi, it is then visible in mdns-browser. I thought "maybe mdns-browser is too picky on the answers or whatever", but again, it doesn't even see the answer from tinysvcmdns so I don't think the issue is the chrome app.

I have been looking into this issue for three days now, I don't know where to look at anymore. Do you have any idea that might help me ?

My setup is an old Linux Mint 12 (2011) running tinysvcmdns and a Mac OS X Montain Lion running mdns-browser.

Thank you, David

# b6i6o6 (2015-07-15) reporter I've been trying to advertise a _http._tcp.local service using tinysvcmdns and retrieve it from the chrome app mdns-browser. (https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/mdns-browser) Unfortunately, my service is invisible in mdns-browser. I am unable to figure out if the issue comes from tinysvcmdns or from the mdns-browser chrome app, since the tinysvcmdns service is visible from Safari, but my network printer is visible from mdns-browser, so both seem to be working to an extent. I have enabled the debug mode in tinysvcmdns so I see that tinysvcmdns is responding to the mdns query as it says "added 1 answers" in the debug output, but I also added a simple console.log to display the ip addresses of each packet received by mdns-browser (console.log(info.remoteAddress) at https://github.com/GoogleChrome/chrome-app-samples/blob/master/samples/mdns-browser/main.js#L132), and it seems mdns-browser never receives the answer packet sent by tinysvcmdns. What would point more to tinysvcmdns than mdns-browser is that if I install avahi-utils and register a service using avahi, it is then visible in mdns-browser. I thought "maybe mdns-browser is too picky on the answers or whatever", but again, it doesn't even see the answer from tinysvcmdns so I don't think the issue is the chrome app. I have been looking into this issue for three days now, I don't know where to look at anymore. Do you have any idea that might help me ? My setup is an old Linux Mint 12 (2011) running tinysvcmdns and a Mac OS X Montain Lion running mdns-browser. Thank you, David

df commented

2020-07-18 22:30:43 +00:00

philippe44 (2017-05-26)

I realize it's a very old comment, but I had a similar issue sir mdns-scan and it was due to the fact that tinysvcmdns does not set TTL to 255 ont the multicast interface used to respond to query. Some mDNS searcher refuse to handle responses that might have travelled through a router

# philippe44 (2017-05-26) I realize it's a very old comment, but I had a similar issue sir mdns-scan and it was due to the fact that tinysvcmdns does not set TTL to 255 ont the multicast interface used to respond to query. Some mDNS searcher refuse to handle responses that might have travelled through a router

df referenced this issue from a commit

2020-07-19 03:03:37 +00:00

Set multicast IP TTL to 255 in case a receiver demands an unrouted packet Fixing #5 Tinysvcmdns invisible from chrome app mdns-browser

df referenced this issue

2020-07-23 10:26:14 +00:00

Set multicast IP TTL to 255 in case a receiver demands an unrouted packet #13

df referenced this issue from a commit

2020-07-23 10:44:37 +00:00

Fixing #5 Tinysvcmdns invisible from chrome app mdns-browser (IP-TTL-255-patch)

Sign in to join this conversation.