9.10 mdnsresponder error 51 (Network is unreachable)

[Dennis22]

Dear Community,
On my NAS is running Freenas 9.10. Yesterday my Router was broken, but now its fixed. Now the NAS says (look on Picture). I have tried to reset the whole configuration, but it doesnt work, because the NAS did nothing.

Regards
Dennis

 

[jgreco]

mod note: this is not appropriate to "9.10 FAQs" and has been moved to the New User section

 

[jgreco]

It looks like your FreeNAS hasn't received a DHCP assignment. Either fix whatever is assigning DHCP on your network, or assign an IP address manually. The latter is a much better choice for a fileserver.

 

[Mirfster]

Most of those messages can be ignored. The real issue I see is that your FreeNAS system has an IP Address of 0.0.0.0... May want to double check your router..

 

[Mirfster]

While I am not sure of what router you are using, the fact that FreeNAS is showing 0.0.0.0 leads me to believe that DHCP is NOT enabled currently on the router.

Check your router settings to ensure DHCP is enabled. If you want to post information about your router (make/model and if you are running something like DD-WRT on it) it will help us as well.

 

[melloa]

It looks like your FreeNAS hasn't received a DHCP assignment. Either fix whatever is assigning DHCP on your network, or assign an IP address manually. The latter is a much better choice for a fileserver.

I agree the way to go with a server is to assign a SIP. He can do that on FN itself, but I'm not sure how his interface is configured. For my own education, if the box is configured for DHCP, is that specified in /etc/rc.conf line synchronous_dhclient="YES" # Start dhclient directly on configured?

 

[Mirfster]

Agreed giving it a Static IP or even MAC Reservation with an IP outside of the normal DHCP Scope is preferred (heck even both). However, I am just trying to get the OP "up and running". ;)

 

[melloa]

Agreed giving it a Static IP or even MAC Reservation with an IP outside of the normal DHCP Scope is preferred (heck even both). However, I am just trying to get the OP "up and running". ;)

Ditto. But I'd need more information like:

- What router?
- Are other clients getting an IP from it?
- What's the FN Interface configuration?

Not getting here if it is out of scope, but without getting the whole picture will be hard to help. As I'm still learning FN/FreeBSD I'm probably missing something :)

 

[jgreco]

I agree the way to go with a server is to assign a SIP.

FreeNAS does not support SIP.

Obviously that's not what you *meant*, but the point remains: Please do not make up new abbreviations especially where they overlap with a significant protocol within the networking scope of discussion.

For my own education, if the box is configured for DHCP, is that specified in /etc/rc.conf line synchronous_dhclient="YES" # Start dhclient directly on configured?

No. It's specified in the GUI or in the console network configuration subsections. What happens under the sheets is "none of yer durn bizness" and is not meant for you to tinker with. FreeNAS is designed to be an appliance, managed through the middleware. This allows the developers to focus on providing functionality, and they can modify the base system, alter how it works, reimplement it entirely, etc., without it impacting the end user, who only knows that it is necessary to configure things via the GUI (which updates the database, which in turn drives the system configuration).

"synchronous_dhclient" is just a directive telling dhclient to operate synchronously... that is, to wait for a DHCP response before allowing the system to continue. Certain other things freak out if IP addresses aren't set (or sometimes if they change).

The actual network configuration is promulgated down into the host system through /etc/rc.conf.local, which provides some opportunity to see how values are retrieved from the configuration database.

 

[melloa]

FreeNAS does not support SIP.

Obviously that's not what you *meant*, but the point remains: Please do not make up new abbreviations especially where they overlap with a significant protocol within the networking scope of discussion.

Will not argue that the abbreviation as, although understood by some, might lead to misleading interpretation with the protocol.

Thanks for the information on FN, really appreciated.