Interface connection weirdness

[Tomjvk]

After a lot of hours I found out I have the same issue as described here: https://www.truenas.com/community/t...responding-after-reboot-network-config.34848/.
The issue is that after every reboot the box is not recognized on the network: I can see it's ip on the router page, but pinging both from and to the box is not working. (It seems like somewhere something is not allowing connections?)
And only when I perform the following steps in sequence it works again (basically resetting the interface):

1. Unplug ethernet cable from box
2. Go to Shell
3. ifconfig {interfacename} down
4. ifconfig {interfacename} up
5. exit shell
6. Reconnect ethernet cable to box
7. Press enter in TrueNas menu

When I try to reset via 1) Configure Network Interfaces, and select the interface and say remove current settings it does NOT work.
And if I try to reset via shell ifconfig (steps above), but while letting the ethernet cable in I get the error: {interfacename}: APE event 0x...... send timed out.

Anyone any idea how to fix this?

Maybe something with dhclient (https://www.cyberciti.biz/faq/freebsd-unix-force-dhcp-client-to-get-a-new-lease/)?


System specs:
Acer Veriton L4620G
Intel Pentium CPU G645 2.90GHz
4GB of RAM (Yep know it's not recommended, but do not have a second RAM stick sadly)

Running TrueNAS 12.0 from 32GB usb 3.0 usb stick

 

[chrishawver]

I am having the exact same issue. Only thing is that I have pfSense set to assign a static IP to Truenas. Do you have a reservation setup for your Truenas?

 

[Mrfix71]

I am experiencing almost the same thing. Has there been a solution?

 

[pschatz100]

There are two things that I can think of that might cause such a problem: 1) Power saving options that put the system into deep sleep, and 2) incompatibility between FreeBSD (the OS that TrueNAS is based on) and your network hardware.

1) It is possible that the system goes into a deep sleep from which TrueNAS is unable to awaken. Go into the bios and disable ALL power saving settings. While you're there, you should also disable all the other features TrueNAS won't be using such as sound, wifi, advanced USB features, etc.

2) TrueNAS may not be compatible with the network interfaces on that motherboard. If that is the case, then there is nothing you can do but try another NAS system that is based on Linux or Windows.

This Acer box is a really terrible choice for TrueNAS. It is designed for a completely different purpose. If you get it running for a while, but then lose your data - you have been warned.