Lost Network Connectivity (IPv4)

TrueNAS General
1

Scale (version 24.04.2)) has been running for quite some time without issue. When I attempted to connect to the web portal this weekend I get a connection time out. Attempts to SSH similarly fail.

From local connection to server it appears I no longer have IPv4 connectivity. My network is configured with a PFSense router configured to serve DHCP.

From PfSense | Status | DHCP Leases I can see the address has been assigned and shows active/online

192.168.6.250 04:7c:00:00:00:b2 truenas TrueNAS Scale Server in Lab

From option 7 Open Linux Shell.
I don’t see a binding when running an ‘ip addr’

1: lo <LOOPBACK, UP, LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/LOOPBACK 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_code1 state UP group default qlen 1000
link/ether 04:7c:00:00:00:b2 brd ff:ff:ff:ff:ff:ff
----> Missing ipv4 inet info
inet6 fe80:67c:0000:0000:0000/64 scope link
valid_lft forever preferred_lft forever

Much of the troubleshooting info I find online suggests running dhcpd checks on the server but I don’t see that service or cli installed on my TrueNAS instance.

From Option 6 Truenas CLI:
Running a network summary I see:
ips: < dict >
default_routes: < empty list >
nameservers: 192.168.6.1

Running a network configuration config I see:
id: 1
hostname: truenas
domain: local
ipv4gateway: ← blank
ipv6gateway: ← blank
nameserver1-3: ← all blank
httpproxy: ← blank
hosts: < empty list >
domains: < empty list >
service_announcement: < dict >
activity: < dict >
hostname_local: truenas
state: < dict >

Appreciate any help or pointers to help! :slight_smile:

2

Hi - I think I have the problem resolved. This was a physical layer problem.

I have an un-managed switch between the NAS and the pfSense router and the Ethernet cable between those two was not seated properly. Still unclear as to why pfSense was reporting the connection as Active/Online.

In the process of troubleshooting this problem I chose Option 5 of the TrueNAS CLI “Reset All Configuration Data” which (at the time) seemed like a reasonable thing to do since all I had on my mind was network configuration. Now that it is back up I have an empty NAS.

I did an upgrade a couple months back and still have the TAR config backed up locally . I worked through the process here to upload that TAR and now I am back to full functionality:
General Settings Screen | TrueNAS Documentation Hub.

1 Like