NB This is not a bug, I just need help fixing the issue.
What happened?
I am experiencing an issue with FCast receiver discovery across subnets, even after configuring Avahi as an mDNS reflector on my pfSense router. Here are the details of my setup and the steps I’ve taken so far:
Environment:
FCast Receiver: Running on 192.168.50.187 (subnet: 192.168.50.0/24)
FCast Sender: Grayjay on a device in subnet 192.168.40.0/24
Router/Firewall: pfSense 2.8.x (latest)
Avahi Daemon: Enabled on pfSense with reflector mode (enable-reflector=yes)
Reflection Filtering: Configured to allow _fcast._tcp (or all)
Firewall Rules:
UDP 5353 (mDNS) allowed between 192.168.40.0/24 and 192.168.50.0/24
TCP 46899 allowed from 192.168.40.0/24 to 192.168.50.187
Replication steps
Steps Taken:
Enabled Avahi daemon on pfSense with reflector mode.
Added _fcast._tcp to the Reflection Filtering list in Avahi.
Verified firewall rules allow mDNS (UDP 5353) and FCast (UDP 46899) traffic between subnets.
Restarted Avahi and the FCast receiver.
Tested discovery using avahi-browse -art _fcast._tcp from the sender’s subnet. The FCast receiver appear in the output.
root@pc:/home/user# avahi-browse -a | grep _fcast._tcp
- eth1 IPv4 FCast-XXXXXX Android TV _fcast._tcp local
- eth1 IPv4 FCast-XXXXX-19 _fcast._tcp local
Confirmed the FCast receiver is running and advertising its service on its local subnet and other subnet (192.168.50.0/24).
Tried manual connection to the receiver via IP (192.168.50.187), which works, but automatic discovery fails.
Which sender are you using?
Grayjay
FCast Receiver Version
41
Grayjay Version
No response
Which operating system are you using on your receiver?
Android
Which protocol did you use to cast?
FCast
What plugins are you seeing the problem on?
No response
Plugin Version
No response
When do you experience the issue?
Are you using a VPN?
No
Relevant log output
NB This is not a bug, I just need help fixing the issue.
What happened?
I am experiencing an issue with FCast receiver discovery across subnets, even after configuring Avahi as an mDNS reflector on my pfSense router. Here are the details of my setup and the steps I’ve taken so far:
Environment:
FCast Receiver: Running on 192.168.50.187 (subnet: 192.168.50.0/24)
FCast Sender: Grayjay on a device in subnet 192.168.40.0/24
Router/Firewall: pfSense 2.8.x (latest)
Avahi Daemon: Enabled on pfSense with reflector mode (enable-reflector=yes)
Reflection Filtering: Configured to allow _fcast._tcp (or all)
Firewall Rules:
UDP 5353 (mDNS) allowed between 192.168.40.0/24 and 192.168.50.0/24
TCP 46899 allowed from 192.168.40.0/24 to 192.168.50.187
Replication steps
Steps Taken:
Enabled Avahi daemon on pfSense with reflector mode.
Added _fcast._tcp to the Reflection Filtering list in Avahi.
Verified firewall rules allow mDNS (UDP 5353) and FCast (UDP 46899) traffic between subnets.
Restarted Avahi and the FCast receiver.
Tested discovery using avahi-browse -art _fcast._tcp from the sender’s subnet. The FCast receiver appear in the output.
root@pc:/home/user# avahi-browse -a | grep _fcast._tcp
Confirmed the FCast receiver is running and advertising its service on its local subnet and other subnet (192.168.50.0/24).
Tried manual connection to the receiver via IP (192.168.50.187), which works, but automatic discovery fails.
Which sender are you using?
Grayjay
FCast Receiver Version
41
Grayjay Version
No response
Which operating system are you using on your receiver?
Android
Which protocol did you use to cast?
FCast
What plugins are you seeing the problem on?
No response
Plugin Version
No response
When do you experience the issue?
Are you using a VPN?
No
Relevant log output