Discussing Linux Bridge topics Question about network bridging in Linux environments
Discussing Linux Bridge topics Question about network bridging in Linux environments
But why? Why do you think you need to create a connection? I’m not sure you fully grasp the situation I’m trying to clarify. I’d revisit my original idea. It’s completely unrelated to being compromised from outside. This is entirely internal—there should be no external access to your NAS, and converting it into a switch won’t alter that. You should invest more time in networking basics before proceeding, since discussing external hacking here implies uncertainty about what you’re dealing with. That’s why I emphasize not turning TrueNAS into a switch. TrueNAS is 100% a NAS device, not just a Debian-based system. It expects stability and consistency; updates can cause issues if it doesn’t match its expectations exactly. You shouldn’t attempt to install anything under the hood of TrueNAS. There’s a high chance you’ll disrupt functionality, and your NAS likely isn’t the ideal setup for that. But you definitely don’t need a bridge or a dedicated NIC in your NAS for this purpose. Just establish a direct connection for quick communication between your desktop and TrueNAS, and also place both on the same slower LAN network. No bridging required. No turning TrueNAS into a switch. It will work perfectly without breaking anything.
It’s clear you’re aiming for a Windows setup with 10Gb bandwidth for game updates. I’m focused on establishing a bridge for ISCSI access across devices. The goal is direct links from Truenas and PC to backup machines, Proxmox, and an OPNsense router. A cache instance will handle most downloads—often exceeding 10GB. Internet traffic flows through a 2.5Gb connection to the Proxmox router. Currently, updates land in memory, but I plan to use bonding with proper VLAN configurations for faster syncs between machines and backups. A dedicated switch would support this setup, though it’s costly—likely exceeding ten connections. Bridging is essential here. I’m committed and hope others will benefit from this approach. YAY BRIDGING!
Switches rely on ASICs to manage traffic at line speed, while NICs depend on the CPU and fall far short compared to dedicated switches. It's important to note that even simple home routers with multiple LAN ports utilize ASIC technology since those ports function as switch ports.
Avoid making TrueNAS act like a switch—it’ll cause problems. The idea is straightforward: use iSCSI over the faster LAN while keeping regular traffic on the standard LAN. No need for bridging; Windows and TrueNAS should reside on separate subnets so they can communicate freely. They can also exchange data at higher speeds. It’s simple once you get the hang of it. Just don’t complicate things further.
Also worth mentioning... Based on what you’re saying, I believe you’re familiar with the setup I described. I’ve been working with it for roughly a year before upgrading to better networking equipment. My setup included a 1 GB LAN where all my devices were connected. There were several VLANs, but everything was managed through a single 1 gig LAN. I also had a direct 10 gig fiber connection between Windows and TrueNAS, with SMB shares available over that link.
For example, my fast fiber network was 10.10.10.x and the local LAN was 192.168.1.x. Both Windows and TrueNAS were on the same local network (though using separate VLANs for simplicity). I could create an SMB share in Windows by pointing to 192.168.1.3/myshare, but that would only work within the 1 gig LAN—clearly not ideal.
Instead, on TrueNAS, I’d set up an SMB share on the 10.10.10.3 interface. Then in Windows, I’d mount it as 10.10.10.3/myshare, giving access over the full 10 gig network. TrueNAS and Windows retained their 192.168.1.x subnet, allowing normal communication with other devices and the wider network.
TrueNAS also had a direct 10 gig fiber link to Windows, which was perfect for iSCSI transfers. There were no switches or routers in between—just a straight 10 gig SFP NIC on each machine, connected directly via fiber.
If this isn’t exactly what you needed… I’m not sure what your goal is.