Jibun no Kage
Dabbler
- Joined
- May 18, 2023
- Messages
- 15
Good point. I realistically I am an edge case. I evaluate and stress test solutions I plan to use for my own use, but once I did the same as part of the my job/career, as an IT enterprise engineer, and as emerging IT technology evaluator for a Fortune 10, yes 10 firm. You learn what a solution can do... when your goal is to break it various ways on purpose. This type of analysis, often exposes where a solution is flexible in one aspect but limited in others, if by design, that is one thing. If by default, well, that is of course another. If I think I can qualify an applicable use case, I will consider a feature request.
The question I can't quite scratch, is how TrueNAS is structured logically to not allow NIC flexibility in some ways, but then allows explicitly assignment of interface binding, but address binding. If you stack multiple IP addresses on a NIC, then assign IPs to various traffic types, i.e. services, fine. But interface binding, implies routing, implies isolation, suggests traffic control. Again, same segment/domain issues, withstanding. Hence all my questions and chiming in on the limits imposed. But again, I wanted to go off the reservation... which is not typical except, say in the context of what I am doing.
The question I can't quite scratch, is how TrueNAS is structured logically to not allow NIC flexibility in some ways, but then allows explicitly assignment of interface binding, but address binding. If you stack multiple IP addresses on a NIC, then assign IPs to various traffic types, i.e. services, fine. But interface binding, implies routing, implies isolation, suggests traffic control. Again, same segment/domain issues, withstanding. Hence all my questions and chiming in on the limits imposed. But again, I wanted to go off the reservation... which is not typical except, say in the context of what I am doing.
Last edited:
