Truenas IP routing

Hi All,

In Truenas CE 25.10.1 I recently configured an app from the catalogue with an alias IP. I didn’t create a bridge or vlan, just an additional alias to the interface. The app works as advertised. Using one of Tom’s video as reference, I also have a pfsense firewall that I’ve configured with a VPN gateway with kill switch. This also works as expected as when I add a client’s IP address to an Alias defined on the firewall, all traffic for that client is routed to the VPN gateway.

My problem is that this does not seem to work for Truenas Apps. When I add the app’s IP to the pfSense Alias list and I curl (ip.wtf) from the app’s shell, I still get my isp ip. Can anyone please tell me what bonehead misconception I have about how Truenas networking works?

Because of the way TrueNAS is designed it will only send the data out the primary IP even though you have that alias IP. The app will respond to requests that come in on that alias IP assigned to it, but will not initiate outbound connections from it.

Thanks Tom,

Does anyone know if this will also be the case for LXCs? Or, is there a way to target a specific network interface using a custom docker app . My goal is to use the interface defined in pfSense.

If you are using containers with a bridge then it will route out that IP

Thanks again Tom. I’ll likely wait until Truenas Half Moon is fully backed before I try again.

Cheers!