IMHO it should be possible to assign an app to an IP-address related to a VLAN and related subnet.
Not so< in the actual implementation. It is possible to assign the gui to a certain IP … however all traffic is routed via the same gateway back.
So not bound to the VLAN and/or subnet and causing asymmetrical routing.
All things I regard NOT OK and even not secure!
I will never allow this on my network!
I honestly don’t think the TrueNAS Docker implementation is made for you, you’re better off with a base OS (Debian, etc) or something like Proxmox and to mess around there with your own firewall/routing rules. This is more of an appliance OS and there’s certain features that are possible but not setup/enabled/coded or etc. Basically good luck!
At this moment I am not using app’s at all. Surely practical, however they have to full fill requirements as described. I use VM’s which are more work and less practical, but IMHO significant more flexable and more secure.
Problem I privately, do not have and want to have a collection of servers. And TrueNas is an environment which allows me to combine the majority of things in one physical server.
However there are surely things I really really would like to see improved and this is high om my wish list.
Not only for VM’s but also for the basis NAS function where I would love to see the option for the use of different vlan’s for different goals. For example IMHO you need to separate truenas machine managment, from data storeage, which is not possible (using separate vlan’s).
3 words:
LEARN Docker networking!
Use Custom App, portainer, Docker, arcane.
(It is possible to use an interface in a vlan, but usually you want that interface without an IP and create a bridge to it where you do have an IP).
Since it seems to work better, my network situation is as follows:
