Linux Bridge question

[ianm_ozzy]

7 hours ago, LIGISTX said:

Also, of note…. Assuming I am understanding you correctly, which I think I am, I do know what you want, and I did this myself for about a year until I bought nicer networking gear. 
 

I had a 1 GB LAN that all my devices were on. I had many vlans, but all of that ran over a 1 gig physical LAN. My desktop and TrueNAS box were both on that 1 gig lan (on separate vlans, but for simplicity let’s assume a flat network). I ALSO had a direct 10 gig fiber connection between windows and TrueNAS, and over that direct link I had SMB shares.

 

Let’s say my fast fiber network was 10.10.10.x and my 1 gig network was 192.168.1.x. Windows and TrueNAS were on both. Windows had a 10.10.10.2 IP and a 192.168.1.2 IP, and TrueNAS had 10.10.10.3 and 192.168.1.3. I could add an SMB share in windows via adding 192.168.1.3/myshare, but then the data would only go over the 1 gig network… obviously not what I want. So instead, on TrueNAS, you create an SMB share on the 10.10.10.3 interface. Then in windows, you mount your share as 10.10.10.3/myshare and boom, 10 gig connection. Easy. 
 

TrueNAS and Windows still have the 192.168.1.x subnet, so they can both still talk to the rest of the network, they can talk to WAN, they can do anything like normal. But they also have the 10.10.10.x 10 gig direct link which is what in your case, you would use for iSCSI. No extra switches, no bonding, just a direct link between the two machines for the 10.10.10.x subnet. No switch in the middle. No router in the middle. Literally just a 10 gig SFP NIC in both machines, and fiber running directly from one NIC to the other.

 

If this is not exactly what you want….. I have no idea what you want. 

A setup  you described is fine for just accessing standard resources on truenas - nfs, smb, ISCSI - at faster speeds.

 

So  my  truennas - quad port 10 gigbit

PC - 2 port 10 gigabit.

One direct link between them  on its own network using one.

 

On truenas  bridge the other 3 connections.

A direct connection  to/from PC to  one of the bridges ones.

Another of the bridges connections to the proxmox machine - with windows VM (for slow game updates) & opnsense router.

There are  exactly 2 ISCSI shares on truenas for games, using deduplication - and working  very well.

One for the windows VM &  one for the gaming PC.

 

 

The problem is  this:   https://lancache.net/

 

I could not get it to work on multiple networks.

So wither use a 10Gb switch, or  the much much cheap option of a bridge.

 

If for example I installed   ubuntu server as a VM on truenas, it can work.

If the VM is connected to both networks, it  apparently  can only be configured to respond to one.

I am unsure why, as I  did not create it.

 

So bridging is the way to go for me.

 

The upside is an exclusive 10Gb link for ISCSI and also up to 10Gb for game updates/downloads.

 

If anyone cannot cannot see why this is needed, then it is your problem.  i am over it.

 

The  query has been answered!

 

 

 

 

[LIGISTX]

4 hours ago, ianm_ozzy said:

If anyone cannot cannot see why this is needed, then it is your problem.  i am over it.

Then put another direct connection between TrueNAS and Proxmox..? Or run lancache and the windows update VM virtualized under TrueNAS, so it can handle all of the networking of lancache and the updater VM internally? 
 

¯\_(ツ)_/¯ 

 

Good luck, just whatever you do, don’t turn TrueNAS into a switch. And if you do anyways, make sure to save your TrueNAS config often so when the OS poops the bed, you can easily and quickly get your core TrueNAS features restored. 

[LIGISTX]

Actually, maybe a way better idea… just stop using TrueNAS. Start with arch, Ubuntu, Debian, whatever you want, import your ZFS arrays, and then you can turn that OS into a switch and still have all of the functionality you want without the issue of TrueNAS being an appliance… with your own clean slate of a more standard Linux distro, you’d have much better luck doing non standard things since you can control how things get updated and not beholden to iXsystems.