I’m tired of dealing with the TN GUI and services taking over all network interfaces and common ports (like 80, 443). How can I have all app traffic use another NIC, and keep the web GUI and other core services on the 1st one?
I have my Truenas GUI management and storage services in 1 vlan, and I want my applications in a different VLAN with proper default gateway routing.
Possible since the latest updates to both the system and the app catalog. Just set the IP address of your app to the one in that other VLAN.
For ingress …
Not possible for egress right now. Yes, I am equally disappointed.
Since I use CE for apps only, I decided to throw everything into the “app” VLAN, including the UI.
File sharing and jails and VMs are on CORE where this type of separation just works. For jails and VMs - not for file sharing.
Kind regards,
Patrick
How?
GUI is set to use the 172 address in VLAN 1.
Dockge Truenas app is set to a 10 address VLAN 2:
Dockge works on the 10 address, but when trying to setup Traefik, I get an error as it tries to bind to 0.0.0.0:80:
I was referring to the iX standard catalog apps only. No idea or experience about Dockge or Portainer, sorry.
I use a jail (systemd) running portainer that has all its containers on the jail IP address. This is bound to a bridge port, a physical port on the NAS that is in whatever VLAN I want it to be with whatever addressing scheme I want it to be.
I am not using incus for this at the moment due to ther experimental nature. However incus does allow the use of either macvlan OR a bridge. I also have an Incus container setup with docker and portainer setup - I am not using it at the moment, but I am considering migration when the experimental goes away and a few new features appear
This does not help with the standard IX catalog but it would allow a custom setup with VLAN’s / bridges and its own gateway
