Pulling hairs...Just want to make static IP work and setup a direct connection for my laptop

TrueNAS General
1

Not having a great experience…

Heres what Im trying to do:
#1 I want to create a static IP with TrueNas so that I can have a solid system. My TrueNas has 2 ethernet ports that both work, however making static ips work is a pita. Following youtube tutorials, I go into interfaces and edit, then De-select DCHP, then click add. The Ip address i want to use is the same that was assigned from DCHP which is 10.77.134.28/20. I then hit skip for the gateway because it should be the same as when I was using DCHP. Finally, I go to test , but when I open another browser with those numbers, Im not able to get in with the static address. What could I be doing wrong?

#2 I want to connect my laptop to the 2nd ethernet port to move files quickly without going through the router (direct connection). Connecting with either dchp or attempting static I am not able to get in.

ps venting: I thought i was just clearing my configured settings to try to make things work, but it ended up deleting my pool and dataset. I didn’t get any warning that it would do that to my data which has me pissed at the moment…

2

Sorry that you’re not having a good experience.

I assume you’re on Scale - which version?

What is your network’s Gateway IP address - likely your router’s IP address?

What is your laptop’s IP address?

3

Thanks for your help…
I’m on ver: 25.04.1

I logged into my router and my router is showing the standard 192.162.0.1 and 255.255.255.0, however with DCHP enabled on Truenas I’m getting 10.77.128.1 for the default gateway and 10.77.134.28/20 for the IP address for me to login to truenas (which I’m now) and would like to switch over to static.
Wifi on laptop: 192.168.0.100 connects to truenas at the moment

Ethernet port on my laptop computer "(direct connected to truenas machine) 169.254.124.21 subnet 255.255.0.0 not working on truenas the ip is 10.77.137.0/20

4

edit: my writeup overlapped with your second post.
changed the IP’s and the Subnet to be fitting to your routers network

Hey there,
I go ahead and assume following(Check if true and change where needed!):
You run TrueNAS Scale 25.04.1
Your Router IP is 192.162.0.1
Your local Subnet is 192.162.0.1/24
Your Router also acts as DNS-Server
Your desired Server-IP is 192.162.0.28
You do not have any bridges configured in ‘Network → Interfaces’ (just your two NICs are visible)

The following will set the ServerIP to 192.162.0.28 and both physical Network ports will behave like any Network Switch.
Any Port can be used as Uplink to the Router or Downlink to your Laptop or other devices.

First go to ‘Network’ and click on ‘Global Configuration → Settings’
In section ‘DNS Servers’ set ‘Nameserver 1’ to your Router-IP (192.162.0.1)
Optional: Set Nameserver 2&3 to 1.1.1.1 and 8.8.8.8 as backup

In section ‘Default Gateway’ set ‘IPv4 Default Gateway’ to your Router-IP (192.162.0.1)

Save the configuration.

Second (Still in ‘Network’) click on ‘Interfaces → Add’
Set ‘Type’ → ‘Bridge’
Set ‘Name’ → ‘br0’
Set ‘Description’ → ‘vSwitch’
Set ‘Bridge Members’ → Select both your physical NIC’s
Click ‘Aliases → Add’
Set ‘IP Address’ → 192.162.0.28 / 24

Save the Configuration, apply and confirm it when asked.

Good luck and I hope it helps :o)

1 Like
5

Wouldn’t that require OP to also remove the IPs from the bridge interfaces beforehand?

I agree with everything you set above it though; that to me looks fine.

6

true :o)
But since there was no specific information given i wrote it up in the assumptions that there are just the Physical Nic’s visible in Network → Interfaces.
An existing bridge could/should be deleted or modified.

7

Did you mean 192.168.0.1 and not 192.162.0.1?
Either way, i tried changing the settings and can’t get back in.

in the section where ‘Default Gateway’ set ‘IPv4 Default Gateway’ to your Router-IP (192.162.0.1) or 192.168.0.1 (i tried both) there was a message that came up and said that is was umreachable and would not let me save…

thanks for the help

1 Like
8

I think the 192. ips given by @John-Noah were examples, since those are pretty much stock IPs.

Given that dhcp gave you a 10.77,etc/20, I’m going to assume that your gateway’s IP is 10.77.134.1/20

So first thing first - lets go to Network & check what we have for “Global Configuration”

Do you see 10.77.134.1? If not, let me know what you have there.

For now, we’re going to work on one interface at a time. I’m going to call the interface going to your router as ‘interface 1’ and the one to your laptop as ‘interface 2’ - go ahead & delete anything configured under interface 2 & confirm you’re still able to reach the UI of your NAS.

Next lets find the interface 1 we’re going to modify; it should look something like the following:

image
image424×141 2.04 KB

…Which sounds like 100% what you were trying to do in step#1 - if it isn’t, let me know. If you’re still having issues, we’re gonna need to know the LAN IP of your gateway & if you have anything else at all between your gateway & your NAS.

If it doesn’t work, make sure nothing else on your router is already using 10.77.134.28 - DHCP can sometimes goof… If something else is already using 10.77.134.28 either force it to something else, or just make the NAS 10.77.134.29 if it isn’t too much of a pain.

Next, assuming you’ve set a static IP & can still reach the NAS successfully on interface 1, we go some option. First question though is: why does it matter if the laptop connects directly to the NAS? If this is a LAN connection for a small business/home setup, I can guarantee you that the router would add like… 2ms of latency? If it is adding more than that, then you got another issue that needs investigating imo.

If you still really want to, instead of a bridge, I’d actually consider setting up interface 2 on a completely different subnet (something I did when my ingest station was directly connected to my NAS), something like: 192.168.0.2/24, then connect the ethernet to the Laptop, edit the laptop to have that connection be something like 192.168.0.3/24

You might wonder: “why have interface 2 on a different subnet?” TrueNAS demands it to be so is the shortest answer.

…This has turned out much longer than expected; if things still ain’t working, then just share us the LAN ip of your gateway, a screenshot of the networking TAB on truenas, and the LAN IP of the laptop & uhh, I guess we’ll do our best.

9

No, it didn’t. It removed the configuration for your pool, so TrueNAS doesn’t know about it, but all the data is still there–just import the pool again. Unless the pool was encrypted and you hadn’t saved the key.

Why do you think this would make things any quicker?

2 Likes
10

Having that network is unusual all on it’s own.
And to then be able to connect to the router on 192.162.0.1 is more usual still.

Can you doublecheck that your 192.162.0.1 router is indeed offering the 10.77.134.28/20 network to DHCP clients? Do this on the router, not on a client. It should be plainly visible on the applicable LAN/DHCP page if you’re the administrative user on the router.

I ask because I think you have two devices and the one you view as your router currently isn’t the one providing DHCP for your TrueNAS server.

My best guess is that you have your own router and then you have your ISP provided equipment, and and you have it connected & configured incorrectly. Leaving it like that is going to cause you an endless stream of quirky issues.

2 Likes
11

Starting over again.

3
31034×918 26.4 KB

2
21664×736 12 KB

1
11660×646 9.08 KB

These are my new settings, before I actually had the wrong network cable plugged in and now they are both correctly on the same wifi router.I was finally able to get a static connection using * 192.168.0.127/24 with the gateway being the 192.168.0.1.
This working good so far