Truenas VLAN jellyfin return route wrong

[4o4rh]

I have a truenas scale server with a bridged lacp connection
the main vlan is on the 20.x
a media vlan is on the 30.x

when i install jellyfin, clients on the media vlan can connect to the server on 30.x but on other subnets, curl just times out

In the pfsense logs i see

192.168.30.10:9096 192.168.40.xx:39992 pc.net.lan TCP:SA

notably the interface shows as being on the 20.x

i guess this has something to do with the default route on the truenas being the 20.x vlan address.

any help appreciated

[4o4rh]

@4o4rh i am struggling to get policy based routing working on truenas scale.
either i get the situation where non-media vlans can access the jellyfin server on the media vlan (but then the truenas/smb vlan is not accessible, or the truenas/smb vlan is accessible by not the jellyfin vlan (other than from a device on the vlan).

It both cases the non-accessible vlan is appearing on the wrong pfsense interface.

so, it seems truenas is returning via the default route rather than the desired return route