On every Linux, Windows, Mac box I have ever worked on with multiable NICS. Each NIC can have its own IP and Gateway.
So what where saying is I cant have an IP address for management and an IP for the storage network. What am I missing?
Nobody’s saying that; of course you can (so long as they’re on different subnets). But you have one and only one default gateway.
TrueNAS does not have firewall rules manageable by the user.
TrueNAS does not implement policy routing.
These features simply do not exist. It’s fine to be asking for them but claiming it was a bug that a storage platform does not implement advanced networking features still does not track with me.
It’s a storage appliance supposed to be placed into an isolated storage network in an enterprise setting.
Open up a feature request thread and see how far that gets. Seriously, no sarcasm intended.
1 Like
I ran into the same situation on XigmaNAS (FreeBSD) which used to be FreeNAS which TrueNAS took…
Anyway… long story short… same issue. my current XigmaNAS box has 6x 10Gb NIC on it. trying to isolate traffic to each NIC was a nightmare. Because of the default gateway. even when you have one nic in a VLAN, VLAN80, and have smbd to listen on that VLAN’s IP it would ONLY accept traffic, but outbound traffic was send via the default gateway.
Even on the FreeBSD box, setting up a FIB with its own route table it will exhibit the same. Why? because smbd is launched in FIB 0. took me a LONG time to figure it out. You literally have to kill the smbd process and relauch it in the other FiB. At least in FreeBSD arena, it’s not just the network routing, but it’s also how the service “works”.
I just load up TrueNAS SCALE to test, and saw this post… and I have a feeling it is going to be the same…
Of course it is. Nobody ever implemented per service FIBs on this platform and I doubt it’s even on the roadmap.
If you truly need isolation, you must use a container technology that provides it. Like jails on FreeBSD and I assume LXC on Linux.