Clive_A wrote

Hi @doublemac 

Thanks for posting in our business forum.

mDNS Repeater on the Router Doesn't Take Effect

  @Clive_A Thanks for the link. Is it better if I reply in that thread?

 

Since I am able to ping by hostname (LGwebOSTV.local) between vlans with the mDNS enabled, isn't that an indication that the mDNS repeater is working? I will investigate with Wireshark if I have time tonight.

 

But if the mDNS repeater is ok, the question remains as of why I am not able to cast to the TV when I am on different vlans? Again, note that I have implemented and enabled the _googlecast._tcp.local service, as well as tried disabled any ACL rules.

 

When I have this working, the plan is to give the tv a fixed IP and setup specific rules allowing vlan30->vlan10 communication for the required chromecast ports.

  @Clive_A 

Clive_A wrote

Hi @doublemac 

Thanks for posting in our business forum.

doublemac wrote

Clive_A wrote

Hi @doublemac 

Thanks for posting in our business forum.

mDNS Repeater on the Router Doesn't Take Effect

  @Clive_A Thanks for the link. Is it better if I reply in that thread?

 

Since I am able to ping by hostname (LGwebOSTV.local) between vlans with the mDNS enabled, isn't that an indication that the mDNS repeater is working? I will investigate with Wireshark if I have time tonight.

 

But if the mDNS repeater is ok, the question remains as of why I am not able to cast to the TV when I am on different vlans? Again, note that I have implemented and enabled the _googlecast._tcp.local service, as well as tried disabled any ACL rules.

 

When I have this working, the plan is to give the tv a fixed IP and setup specific rules allowing vlan30->vlan10 communication for the required chromecast ports.

Disable the ACL and Wireshark. Will you even receive the mDNS coming from another VLAN?

Or you receive it but do not reply on the TV?

 

Ping does not matter.

mDNS is a separate protocol. ACL can stop it. Misconfigure can make it not show up in the list. And like I wrote, mDNS service might not be the one you configured. You need to Wireshark and find out what is wrong.

Too many variables in this. I cannot decide with the information provided so far. I would say it is the ACL or misconfig.

 

Sure, but it the pinging of a hostname in another vlan is at least an indication that the mDNS is working or not. The Chromecast service is another thing indeed.

 

I investigated the problem further:
With the phone connected to vlan10 I ran the mDNS Discovery app searching for googlecast services over TCP. The app discovered the LG TV google cast from the other vlan. However, when checking the Youtube app, I couldnt find the LG TV as an option.

 

Thereafter I connected an external Chromecast to a TV and placed the Chromecast in the same vlan as the LG TV (vlan30). Again, with the phone connected to vlan10, the mDNS Discovery app discovered two google cast services: the LG TV and the external Chromecast. When checking the Youtube app though, I could only find the external Chromecast availabe. 

 

What does this mean? Is LG having a firewall configured to actively block incoming casts from other vlans than the one it is on itself? Any ideas if this could be solved without placing the TV in the trusted network?

 

Then something surprising occurred: When being connected to vlan10 with the phone, I opened up the Google Home app -> Devices. Therein the LG G4 was found and when clicking on it I got the option to "Cast Screen". That worked directly. I then checked the Google Photos app, and could also cast to the LG G4 from there. But from Youtube I still do not get any option.

Small further development: Tonight I tested the Netflix app on the phone from vlan10. No option to cast. Then I opened the Prime Video app on the phone from vlan10, from that one I can cast! What could be the cause for this?