search

jorisjean / cc-mdns-reflector

Reflect MDNS packets for Chromecast device in a VLAN to the configured Client in another VLAN
MIT License
2 stars 2 forks source link

Reflecting but Not Connecting #1

Open bikramjs7 opened 4 months ago

bikramjs7 commented 4 months ago

I have successfully run the reflector, and it is working as expected. My Chromecast and client devices are in different VLANs. However, after the discovery phase, I am unable to connect to the Chromecast. I have configured my Linux machine, where the reflector is running, to forward traffic on TCP ports 8008,8009 and UDP ports 32768-61000. Are there any additional steps required before the client device can connect to Chromecast?

jorisjean commented 4 months ago

Past the discovery the communications between the Client and the Chromecast are in uncast. So the issue should only be routing/firewalling between your client and your chromecast.

bikramjs7 commented 3 months ago

@jorisjean Thanks for response

In tcpdump i could see mdns queries initiated by client but no packets related to unicast connection error: unable to get cast application: unable to connect to chromecast at '192.168.40.192:8009': read tcp 192.168.95.177:54776->192.168.40.192:8009: read: connection reset by peer This is the exact error i am getting 192.168.95.177 is my client's IP I will get back to you if I have any more information.

jorisjean commented 3 months ago

You could try telnet 192.168.40.192 8009 and run a packet capture on the linux server interface facing the Chromecast. This way you'll be able to tell if the chromecast replies to the client.

Le ven. 19 juil. 2024 à 10:54, heuristic11 @.***> a écrit :

@jorisjean https://github.com/jorisjean Thanks for response

-

Ip4 forwarding is already enabled

Yes i am able to ping chromecast from other Vlan

The Ip advertized by chromecast is valid

In tcpdump i could see mdns queries initiated by client but no packets related to unicast connection error: unable to get cast application: unable to connect to chromecast at ' 192.168.40.192:8009': read tcp 192.168.95.177:54776->192.168.40.192:8009: read: connection reset by peer This is the exact error i am getting 192.168.95.177 is my client's IP I will get back to you if I have any more information.

— Reply to this email directly, view it on GitHub https://github.com/jorisjean/cc-mdns-reflector/issues/1#issuecomment-2238693736, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4SVQJFWAVXMPAAN4XYVR3ZNDH3HAVCNFSM6AAAAABLDAZA6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZYGY4TGNZTGY . You are receiving this because you were mentioned.Message ID: @.***>