FreeNAS cannot connect to internet.

[Required]

Hi, I just powered on my box, which was sitting for a while and seems like that internet connection is not working. Switching from DHCP to Static config and vice-versa does not make any difference. I cannot ping any external IP, but I can ping internal ones. Date & Time is correct. Both box and router were rebooted already.

Running out of ideas and search results...

Version:
FreeNAS-11.3-U2.1
Physical Memory:
8020 MiB
Model:
Intel(R) Celeron(R) CPU G1840 @ 2.80GHz

 

[HoneyBadger]

Your gateway is set at 10.11.0.0 - this isn't a valid gateway in a /24 network. It is likely the .1 IP, but you will have to confirm your local configuration.

 

[Required]

10.11.0.0 is IP of the router. Screenshot of OpenWRT config.

 

[jgreco]

@HoneyBadger is making the point that 10.11.0.0/24 is the network address of 10.11.0.0/24 and is not a valid host address on that network. In an IPv4 ethernet network, the first address is the network address and the last address is the broadcast address. For a /24 sized network, this works out to the last octets of .0 and .255.

It's not impossible for 10.11.0.0 to be a valid IP address; it would be valid on the 10.10.0.0/23 network, for example, where the first address is 10.10.0.0 and the last is 10.11.0.255.

However, your given configuration is broken. Please change that to 10.11.0.1/24 and use 10.11.0.1 as your gateway for hosts on that network.

 

[Required]

Thanks for explanation. Issue resolved!

 

[no_connection]

Remember that .0 and .255 can be hardcoded to not be regular IP. Even it it's technically valid for /23 and larger subnets. Windows update for one have not worked in the past with such an address.

It is strange that OpenWRT would allow you to save such a config.

 

[jgreco]

Remember that .0 and .255 can be hardcoded to not be regular IP. Even it it's technically valid for /23 and larger subnets. Windows update for one have not worked in the past with such an address.

Those of us in the netops community have been beating the crap out of every idiot netadmin and company that has done B/S like this for a good number of years now. No one has any business trying to determine this for a network that they do not themselves configure and administer.

It is strange that OpenWRT would allow you to save such a config.

That is definitely true.

 

[no_connection]

Yea but it's easy to set up a /22 or even /16 with DHCP and not make reservations for every .0 and .255 and run into strange problems like Windows Update strangely not working on one or two machines. I would imagine many IoT devices having broadcast and network addresses hard coded thus behave strange when it gets an address that ends with .0 or .255. Same for many applications with dubious network handling.
Point is keep those addresses away from clients even if it's a valid address.