Yes. That’s why you should configure servers like a NAS with static IP addresses and not rely on DHCP.
2 Likes
Yes.
What typically causes this IP change? I’ll research setting up static ips. Assuming there are pro’s and cons to both? The guide I followed after building this NAS system mentioned using DHCP.
Your router simply decided to give the NAS a new IP due to ‘reasons’ (router reboot, another device randomly wanted that IP while NAS was offline, DHCP lease expired, etc. etc., take your pick).
DHCP
pros: it is easy to initially setup.
cons: what you just experienced.
Static IP
pros: it avoids the nonsense you just experienced by assigning an IP that doesn’t change (static)
cons: takes maybe an additional 2 minutes to setup initially the very first time you do it if you’re new. If you goof & try giving two devices the same IP you’ll have a headache until you correct the IP for one of the said devices.
You can also initially use DHCP to just get connectivity & then change that IP to be statically assigned to the NAS on your router & on the NAS’ networking tab afterwards. This is the easiest of both worlds.
//edit: since you mentioned you’re new & that you’ll have to research static IP - be advised that you don’t manually have to set a static IP for each & every device you own, you can just setting a static IP for your NAS (99% chance of no further issues or config changes depending on your network setup).
2 Likes
I can’t tell if you are being for real or joking. I did say I am new to all this, this is also my first time in the TrueNas community. When I had the ip redacted folks told me that was critical information and I needed to include it. Now you’re saying I missed up badly.
Mr. @winnielinnie is the resident court jester. You need to read everything with a grain of salt.
He’s implying you yourself posted the new IP address three times so it should have dawned at you that your NAS simply got a new IP address from DHCP.
Then again at least I am aware there might be users who might not even have a firm understanding of what an IP address does exactly.
So no problem, I suggest you check the documentation and/or get someone local to help and set a static IP address for your NAS so it never changes again.
3 Likes
Which makes jesting a bad idea…
To keep it short:
Ranges for private networks are local. Everyone (and his dog, since “on the Internet nobody knows you’re a dog”) uses the same ranges, and an address in these reserved ranges can only be accessed from inside the local private network. This is NOT sensitive information. (No hacker is going to type 10.0.0.128 and get to your NAS… unless he has already broken inside your network.)
You have a DHCP server, likely the box provided by your ISP. Look into its documentation, and access its management interface to see which range it allocates.
Then pick an address that is inside your network but outside of the range used for DHCP; manually set the NAS to this address. (Say, the DHCP allocates 10.0.0.100 to 10.0.0.250, you could pick 10.0.0.99.)
Alternatively, you could make a DHCP reservation, that is: Instruct the DHCP server to always allocate a defined IP address to the MAC address of your NAS.
1 Like