Messages

Is it still happening? Or was it only once after you made some changes?
I noticed some times ago, that livelog confused some label tags after changing config...

Still happening, even after a reboot.

...and here are the firewall rules.

So - I have a strange one here I can't quite understand.

I noticed my firewall was passing UDP IPv4 traffic via an automatically generated rule designed to pass IPv6 traffic.  See attached screenshot for info.

I am very confused here...any insight?

Issue is that I'm unable to access a Jellyfin server I have installed on my LAN from some, but not all of my VLANs.

I have the latest version of OPNsense installed (OPNsense 23.1.5_4-amd64 specifically).  My configuration has several VLAN subnets - LAN (192.168.1.0/24), IoT (192.168.30.0/24), Kids (192.168.20.0/24), and a few others which aren't relevant to this discussion.  The way I have it setup, my Jellyfin server is installed on a NAS on my LAN subnet (192.168.1.30), and I'm trying to access it from Jellyfin clients sitting on the IoT and Kids subnets.

When accessing via Kids subnet, everythiing works fine.  Accessing via the IoT subnet does not work - the client on IoT is unable to connect to the server on LAN.  Firewall rules are identical on bith Kids and IoT as it pertains to this setup - I have a rule to allow traffic to flow from IoT/Kids to LAN when the destination is aligned with the Jellyfin server address (192.168.1.30:8096).

I've tried to ping the Jellyfin server (192.168.1.30) via the OPNsense diagnostics utility.  When I have the source address set to "Kids", the ping works successfully.  If I set the source address to IoT, the ping times out and does not get a response.

Between my router and my Jellyfin server I have two managed switches (TP link Omada switches), and I can't think of any settings which would be different between Kids and IoT VLANs. 

I've been scratching my head here for the better part of a week here, and haven't figured anything out yet.  Strange thing is, the client-server connection used to work from the IoT network - it's only recently that it stopped working and I'm not aware of having made any changes to the network. 

At wits end here - any ideas/thoughts?