"Quote from: EricPerl on March 27, 2025, 07:23:31 PMWhat's your OPN domain? System > Settings > General > Domain.
localdomain
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#1
25.1, 25.4 Production Series / Re: Google Home Remote Feature
March 27, 2025, 09:00:08 PMlocaldomain
#2
25.1, 25.4 Production Series / Google Home Remote Feature
March 27, 2025, 03:26:50 AM
Flat network, 10.0.0.0/24
Versions:
OPNsense 25.1.3-amd64
FreeBSD 14.2-RELEASE-p2
OpenSSL 3.0.16
The only way I've found to make the google home remote feature work for android devices is to toggle a udpbroadcastrelay mdns rule from on to off. Afterwards the google home remote feature immediately works as intended for a temporary period and eventually stops working at some point. To clarify, the remote feature does not work while the rule is enabled, only when toggled back to the off\disabled position does it allow the google home remote feature to immediately start working.
Can someone please assist with resolving this issue. Providing a way to automate the web ui rule toggle would suffice as well. I can create a cron job to schedule the toggle similar to my current workaround for sslh which periodically crashes and needs to be started via a script that checks if its down.
Note: my assumption is that udpbroadcastrelay should not be needed on a flat network but was the only way to get mdns to work and allow the google home feature to work, which is why it is being used in the first place, same experience using both udp relay and mdns repeater, have to toggle on and off in order to allow the google home remote feature to work, nothing is showing as being blocked in the firewall logs, does not appear to be firewall related, seems to be an mdns issue.
Update: found a way to automate the toggle, leave the rule enabled then disable the service, enable\disable the udpbroadcastrelay service periodically via cron job, this resolves the issue and allows the remote feature to work for now
configctl udpbroadcastrelay start
configctl udpbroadcastrelay stop
Versions:
OPNsense 25.1.3-amd64
FreeBSD 14.2-RELEASE-p2
OpenSSL 3.0.16
The only way I've found to make the google home remote feature work for android devices is to toggle a udpbroadcastrelay mdns rule from on to off. Afterwards the google home remote feature immediately works as intended for a temporary period and eventually stops working at some point. To clarify, the remote feature does not work while the rule is enabled, only when toggled back to the off\disabled position does it allow the google home remote feature to immediately start working.
Can someone please assist with resolving this issue. Providing a way to automate the web ui rule toggle would suffice as well. I can create a cron job to schedule the toggle similar to my current workaround for sslh which periodically crashes and needs to be started via a script that checks if its down.
Note: my assumption is that udpbroadcastrelay should not be needed on a flat network but was the only way to get mdns to work and allow the google home feature to work, which is why it is being used in the first place, same experience using both udp relay and mdns repeater, have to toggle on and off in order to allow the google home remote feature to work, nothing is showing as being blocked in the firewall logs, does not appear to be firewall related, seems to be an mdns issue.
Update: found a way to automate the toggle, leave the rule enabled then disable the service, enable\disable the udpbroadcastrelay service periodically via cron job, this resolves the issue and allows the remote feature to work for now
configctl udpbroadcastrelay start
configctl udpbroadcastrelay stop
Pages1
