Networking Question

[McNinjaTNT]

This is probably a dumb question, but basically I've tried setting a static IPv4 on igb0, tried many IPs, like 168.192.15.18, however 192.168.1.XX works,

• 10.0.0.0/8 IP addresses: 10.0.0.0 – 10.255.255.255
• 172.16.0.0/12 IP addresses: 172.16.0.0 – 172.31.255.255
• 192.168.0.0/16 IP addresses: 192.168.0.0 – 192.168.255.255
  
  According to this ^ any 192.168.xxx.xxx IP that's not in use should work right? I've also tried 10.10.1.25 with no luck, all of these with the subnet 24.
  Please help me understand why this is.

 

[danb35]

What problem are you having with, e.g., 10.10.1.25? I assume that instead of 168.192.15.18 (not a valid private IP) you meant 192.168.15.18 (which is), but what's the problem you're having, and how is the rest of your network configured?

 

[Spearfoot]

This is probably a dumb question, but basically I've tried setting a static IPv4 on igb0, tried many IPs, like 168.192.15.18, however 192.168.1.XX works,

• 10.0.0.0/8 IP addresses: 10.0.0.0 – 10.255.255.255
• 172.16.0.0/12 IP addresses: 172.16.0.0 – 172.31.255.255
• 192.168.0.0/16 IP addresses: 192.168.0.0 – 192.168.255.255
  
  According to this ^ any 192.168.xxx.xxx IP that's not in use should work right? I've also tried 10.10.1.25 with no luck, all of these with the subnet 24.
  Please help me understand why this is.

No such thing as a 'dumb question'!

Those are the private subnets designated for use on local area networks; they are not for use on the internet.

So, yes, any IP address in those subnets should work for you, but here's the caveat -- all of your systems need to be on the same subnet, or they can't 'see' each other. This isn't strictly true, if you've configured a router to route traffic between different subnets, but most home users put all their systems on a single subnet, something like 192.168.1.0/24 for example.

In fact, the system you're using to access the TrueNAS server must be on the 192.168.1.0/24 subnet -- that would explain why it works for you, while the other IP addresses do not.

Hard to say for certain, until we know more about your system configuration (as @danb35 pointed out above).

 

[McNinjaTNT]

What problem are you having with, e.g., 10.10.1.25? I assume that instead of 168.192.15.18 (not a valid private IP) you meant 192.168.15.18 (which is), but what's the problem you're having, and how is the rest of your network configured?

Yes, I meant 192.168.15.18, and no I just tested 10.10.1.25, didn't work. All the other devices connected are between 192.168.1.2 - 192.168.1.21.

No such thing as a 'dumb question'!

Those are the private subnets designated for use on local area networks; they are not for use on the internet.

So, yes, any IP address in those subnets should work for you, but here's the caveat -- all of your systems need to be on the same subnet, or they can't 'see' each other. This isn't strictly true, if you've configured a router to route traffic between different subnets, but most home users put all their systems on a single subnet, something like 192.168.1.0/24 for example.

In fact, the system you're using to access the TrueNAS server must be on the 192.168.1.0/24 subnet -- that would explain why it works for you, while the other IP addresses do not.

Hard to say for certain, until we know more about your system configuration (as @danb35 pointed out above).

The setup is as follows: Netgear R7800 for the whole family with 11 devices connected including the TrueNAS, within the IP range listed above, the TrueNAS is setup with IPv4 only with a static connection. It lets me connect to it from both the custom set IP (192.168.1.21) as well as 192.168.1.13.

From what I'm getting, using a different IP (even with /24) changes the subnet? If so it'd make perfect sense, and if so I'm curios what defines inside and outside a subnet when it comes to the IPs.

 

[danb35]

All the other devices connected are between 192.168.1.2 - 192.168.1.21.

There is your problem. If everything else is in 192.168.1.0/24, and you put a device in 10.10.1.0/24, you need to have something to route between those two networks. You may be able to configure your router to do this. If not, and you have a reason to put your NAS on a different network, consider upgrading your router (e.g., to something like pfSense or OPNsense).

 

[McNinjaTNT]

There is your problem. If everything else is in 192.168.1.0/24, and you put a device in 10.10.1.0/24, you need to have something to route between those two networks. You may be able to configure your router to do this. If not, and you have a reason to put your NAS on a different network, consider upgrading your router (e.g., to something like pfSense or OPNsense).

Cool! I understand now, just wanted to know the why. I actually plan to get a OPNsense router for unrelated reasons haha (VLAN isolation, VPN, Firewall, IPS/IDS). Thanks both of you!!