It is freeNAS issue. Found info here
http://prntscr.com/oe75zv
It should have 192.168.10.32/16 instead 192.168.10.32/24 (current, default setup).
I am not very comfortable whit ssh. and I am unable to find how to change this in GUI.
Maybe I am missing something?
A /16 netmask that covers multiple subnets suggests that you have a network design error.
You can change the netmask on your FreeNAS system by going to Network, Interfaces, picking the interface in question, which will list the current IPv4 and netmask in one of the fields, and then selecting "Edit" from the three-dot menu dropdown in the last column. It will present a screen that includes "IPv4 Netmask" as probably the fourth stanza. But you probably shouldn't do this, and should fix your network instead.
A properly designed network would create a subnet for each location. A "subnet" is not just a range of IP's, but also an appropriate netmask. It limits the broadcast domain as well.
For example, let me build a prototype.
192.168.0.0/24 - New York
192.168.10.0/24 - Chicago
192.168.20.0/24 - Los Angeles
At each site, you would have a router at the ".1" address on the network.
All hosts in New York would be numbered as "192.168.0.xxx" where xxx is in the range 2...254, with a default route pointing at 192.168.0.1.
All hosts in Chicago would be numbered as "192.168.10.xxx" where xxx is in the range 2...254, with a default route pointing at 192.168.10.1.
All hosts in Los Angeles would be numbered as "192.168.20.xxx" where xxx is in the range 2...254, with a default route pointing at 192.168.20.1.
Each router would have a link to the other routers, and an appropriate route for each other router. So
The New York router would have a route pointing 192.168.10.0/24 to the Chicago router, and 192.168.20.0/24 to the Los Angeles router.
The Chicago router would have a route pointing 192.168.0.0/24 to the New York router, and 192.168.20.0/24 to the Los Angeles router.
The Los Angeles router would have a route pointing 192.168.0.0/24 to the New York router, and 192.168.10.0/24 to the Chicago router.
This creates appropriately scoped networks and also places a constraint on the size of the broadcast domain. With a /16, your entire network is a single broadcast domain (and is also a single network, and it is inappropriate to refer to 192.168.0.0/16 and 192.168.10.0/16 and 192.168.20.0/16 as different subnets).