[Solved] Sonos on VLANS

[skywalker007]

The archive contains all you need and a docx file ( sorry using windoze ).

No worries, even my mac can display that docx format :-)

[marjohn56]

Nivek1612 just tested and apart from the fact he cannot spell there appears to be file permission errors.

I have re-zipped it on from the host router so it should all be correct now.
I've also replaced the original attachment in the earlier message.


Attachment removed as a plugin is available for testing. PM me if you want to try it.

[nivek1612]

@marjohn I'm waiting for you to read my last email re /etc/rc.conf.d/  :) :) :)

[marjohn56]

done..  :D

[skywalker007]

Ok, I can confirm this works.
I have not tried replacing  my IGMPproxy for IPTV. I am just running a single instance of the relayproxy for port 1900 for Sonos and that works.
Many thanks for all who contributed to the solution, especially @marjohn56.

[marjohn56]

Good stuff.

I now have a modified version that will write the pid value etc to /var/run and allows you to specify the name of the pid file if you want. It will auto create a pid file called udpbcastrelay_[ID] using the ID value if you don't set your own pid filename.

It will be useful if you want to run multiple instances without having to rename the exe itself. For example, in Monit you would monitor the process by its ID, obtained from its PID file rather than just the process name itself, it would not work if you tried to monitor two instances with the same process name : :)

[scream]

I just found that thread today because im looking for a similar multi VLAN solution for:

- IPTV (Multicast)
- Sonos
- Shelly (CoAP / CoIoT Procotol)
- AirPlay

Is there any package for that already? Can't find it.
Is there any doc's how to configure it? What I have to know/configure to get it working.


TIA. Regards
scream

[marjohn56]

We're working on a package. In the meantime if you go back a couple of messages in this thread you'll see I posted an archive with all the details on how to install and configure it.


In its present form you'll need to manually configure as Monit is using the process itself to monitor. I have an updated version of the exe that will allow multiple instances from monit but I'm not quite ready to let that out into the world yet. Do do it without monit just use the rc.d stuff but create multiple copies, the instructions are in the docs.


Hopefully, and this is only hopefully if time allows, we'll have a full package available somewhere around 20.1.2

[marjohn56]

I have a plugin ready for testing, single instance only, but if you only need to relay one port then it's good. It will install properly and it installs the daemon as well so there's no hard work involved at all.


Let me know if anyone wants to try it.

[skywalker007]

Happy to volunteer for testing.
just let me know what to do with the manually installed pieces (rename/leave there but stop/whatever).
cheers!

[skywalker007]

Also - keep in mind, I am on the release, not dev. So I am running 19.7.9.

[marjohn56]

PM me, I'll send you the file and instructions, as for the way you've done it, you can remove it all.

[nivek1612]

tested the plugin in test and now production and works perfect nice smooth install process

[marjohn56]

Just a note, the plugin handles multiple instances, so you can relay/broadcast more than one port or multicast range, also now handles source address for use with the likes of chromecast.

[szty0pa]

Cheers for the great work @marjohn56! I would be very much interested trying it out.
What is the difference between pimd and udp-broadcast-relay? I was thinking pimd forwards the whole 224.0.0.0/4 subnet, but that could have been false.