Show Posts
1
General Discussion / Re: UDP Broadcast Relay
« on: September 08, 2022, 04:52:31 am »
Sorry to bring up an older thread. I have some questions about this udpbroadcastrelay. I understand how it cand replace avahi as a mdns repeater. I'm not convinced on the use of it to replace pimd or any form of pim sparse mode. The reason I say this is because udpbroadcastrelay can send out multicast traffic without regard to whether a device is part of the group or not increasing its packet overhead. Pim-sm on the other hand has been designed to allow clients to join or leave multicast groups.
I am currently running avahi and pimd on pfsense. I may take up opense in the near future. My system is running without any issues with Sonos, HEOS, Airplay , Apple screen sharing, and Miracast across multiple vlans. Currently only firewall rules are to allow all. Trying to get connectivity working first then lock it dowm
Marjohn56 maybe you could help.
The issue I'm trying to resolve is with the DIAL multiscreen protocol my packet captures look like the post from thexy post 88
To answer thexy the problem at hand is the server needs to send it's reply to client doing the search via tcp at the client ip address and application port. From your capture listed the server is seeing the request from the relay, but the source ip address and port were changed during the relay, so the client never establishes the connection.
I am unclear on the command string to have the relay maintain the source ip and port that is critical.
MKnusperer is also describing the same issue in post 122. Others that are having issues with TVs Roku's chromecasts.... are probably having problems with this DIAL multiscreen protocol.
If the code could parse the ssdp packet for the. ST DIAL Multiscreen line maybe it could be handled differently
As a side note if you start DIAL multiscreen server client connection while in the same vlan and then move the client to a different vlan it's possible to maintain the connection,
I am currently running avahi and pimd on pfsense. I may take up opense in the near future. My system is running without any issues with Sonos, HEOS, Airplay , Apple screen sharing, and Miracast across multiple vlans. Currently only firewall rules are to allow all. Trying to get connectivity working first then lock it dowm
Marjohn56 maybe you could help.
The issue I'm trying to resolve is with the DIAL multiscreen protocol my packet captures look like the post from thexy post 88
To answer thexy the problem at hand is the server needs to send it's reply to client doing the search via tcp at the client ip address and application port. From your capture listed the server is seeing the request from the relay, but the source ip address and port were changed during the relay, so the client never establishes the connection.
I am unclear on the command string to have the relay maintain the source ip and port that is critical.
MKnusperer is also describing the same issue in post 122. Others that are having issues with TVs Roku's chromecasts.... are probably having problems with this DIAL multiscreen protocol.
If the code could parse the ssdp packet for the. ST DIAL Multiscreen line maybe it could be handled differently
As a side note if you start DIAL multiscreen server client connection while in the same vlan and then move the client to a different vlan it's possible to maintain the connection,