TrueNAS Core to Mac Studio direct connection

[kochumvk]

Hello TrueNAS Community,

My objective:

Establish a 10Gbe direct link between TrueNAS Core and a Mac Studio.
I dont know how to configure the network/IP on the second network adapter or on the Mac. Looking for help on this.

My current setup:

TrueNAS Core host have two network adapters:

1. 1G intel -> connected to the router -> web interface available at 192.168.1.112 (Works fine, slow)
2. 10G TP Link TX 401 -> connected to Mac Stusio's 10G RJ45 port (Cant't connect from the Mac)

Can you tell me how I can establish 10G transfer between the Mac and the NAS via TX401?

Notes:
I do not care for fast connection with other devices at this point.
Mac and the TrueNAS host are sitting next to each other.
Router is in another room. I May remove the 1G ethernet cable to router after the 10G connection starts working.

 

[danb35]

I dont know how to configure the network/IP on the second network adapter

You'd set it up in the say way you (should have) set up the first one. It will need to have an IP address in a different subnet from the first. There's no reason to set a gateway for this interface.

or on the Mac

Use a different IP address on the same subnet as on the 10G NIC on your NAS. Again, no gateway is needed.

 

[kochumvk]

You'd set it up in the say way you (should have) set up the first one. It will need to have an IP address in a different subnet from the first. There's no reason to set a gateway for this interface.

Use a different IP address on the same subnet as on the 10G NIC on your NAS. Again, no gateway is needed.

Thank you. I tried based on your suggestion:

On the TrueNAS: Set the IP to 150.100.1.1

On the Mac: Ethernet IP set manually to 150.100.1.2

However, when I try to connect from Mac, no luck!

Am I doing something wrong ?

 

[winnielinnie]

What if you append the share name at the end?

Like this:
smb://150.100.1.1/media

 

[danb35]

Those are real, routable, Internet IP addresses, so you shouldn't be using them; you should instead use something in the private IP space (10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16). Not sure that's your problem, but it's definitely a problem.

What happens if you try to ping the NAS from the Mac? Open a Terminal window, and ping 150.100.1.1

 

[kochumvk]

What if you append the share name at the end?

Like this:
smb://150.100.1.1/media

This did not work either!

 

[kochumvk]

What happens if you try to ping the NAS from the Mac? Open a Terminal window, and ping 150.100.1.1

-- 150.100.1.1 ping statistics --- 639 packets transmitted, 639 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 240.572/295.738/458.610/40.654 ms

My understanding is that the ping worked.

 

[winnielinnie]

I don't know how to understand this. But I will try changing the IP as you suggested.

That's definitely not a direct local connection, with latency like that.

 

[kochumvk]

Changed the IP on NAS to 172.16.0.0/12 and on the Mac to 172.16.0.1

Now the ping is just timing out!

 

[winnielinnie]

Changed the IP on NAS to 172.16.0.0/12

Can't end with a 0.

 

[danb35]

My understanding is that the ping worked.

It "worked", in that it got a response, but it definitely wasn't hitting your NAS. A round-trip time of 250 ms shows it was something quite distant, and since that IP is owned by someone in Japan, that's to be expected.

Changed the IP on NAS to 172.16.0.0/12

You really need to learn a bit about IP network addressing, and I don't think this forum is going to be the place. In short, 172.16.0.0/12 is a range of 16 Class B networks whose addresses are reserved for private networks--172.16.x to 172.31.x. You'd choose one of these--let's say it's 172.20.0.0--as your network. You'd use a 16-bit netmask, as it's a class B network. So, the address for your network would be 172.20.0.0/16, and the available address range would be from 172.20.0.1 to 172.20.255.254 (the lowest and highest addresses--.0.0 and .255.255 in this case--are reserved). You'd then assign individual addresses within that--172.20.0.1, 172.20.0.2, etc.--to devices on your network. If you're asked for the address in CIDR format, it'd be 172.20.0.1/16; if you're asked for a separate netmask, it would be 255.255.0.0.

Now, it's pretty unusual that a Class B network would be needed at home--it allows for up to 65,534 addresses, which is far more than most home users need. A Class C network is much more common, and adequate for all but the largest home networks, allowing as it does for up to 254 addresses on the same network. So, you could use just a portion of that network--instead of 172.20.0.0/16, you could use 172.20.0.0/24, which would make the available address space 172.20.0.1 to 172.20.0.254 (again, high and low addresses are reserved). Or you could use an address space that's designated for Class C subnets--192.168.x.0/24, where x is between 0 and 255, inclusive.

 

[winnielinnie]

Or you could use an address space that's designated for Class C subnets--192.168.x.0/24, where x is between 0 and 255, inclusive.

This is what I do.

My personal mnemonic is:

• 192.168.1.0/24 for "1-GbE network"
• 192.168.10.0/24 for "10-GbE network"
• 192.168.25.0/24 for "2.5-GbE network"
• 192.168.5.0/24 for "5-GbE network"
• 1-9 (except for 5) for 1-GbE as well.

 

[danb35]

Of course, the simplest answer is "buy a switch." This one looks like it would do the job:

Amazon.com

And then plug the 10G port on the NAS into one of the 10G ports on the switch, the 10G port on the Mac into the other, and run a cable from one of the 2.5G ports to the router. Keep everything on the same network. Much simpler.

Otherwise, it's likely possible to set up a bridge interface on the NAS with both the 1G and 10G ports as members and effectively use the NAS as a switch--can't really speak more to that possibility, though, as I haven't messed with it.

 

[kochumvk]

It worked! I used 192.168.x.0/24

Thank you very much for teaching me the IP basics and helping me fix this.
Your patience is very appreciated. @danb35 and @winnielinnie