Network tab empty

Help
1

Dear community!

I have changed my router few days ago and I have just realized that the Network tab became empty.
Basically the network only changed that I now use VLANs to seperate a few things in the network, however the Pi-hole is on a VLAN where it can access any device on the network.
I could not guess what is missing here. I just updated to 5.0 and the issue remains.
Running ip neigh works as it should, so I can see entries there about devices all across the network.

What is also needed for this to work properly?

Thanks!

2

Tried everything, still empty...
What does Pi-hole use to discover neighbor clients?

3

Pi-hole pulls the data from the neigh table. To see the contents of the table on your host device, run

ip neigh

The output will look something like this:

192.168.0.100 dev enxb827eb0c8c4f lladdr b8:27:eb:f0:4a:90 STALE
192.168.0.154 dev enxb827ebf04a90 lladdr b8:27:eb:a2:7e:fc STALE
192.168.0.155 dev enxb827ebf04a90 lladdr b8:27:eb:0c:8c:4f STALE
192.168.0.160 dev enxb827ebf04a90 lladdr 02:81:5e:87:94:1c STALE
...
4

Yes, I can see every device there:

10.0.0.2 dev eth0 lladdr c4:ad:34:e9:0f:af STALE
10.0.0.59 dev eth0 lladdr ec:fa:bc:86:cd:dd STALE
10.0.0.63 dev eth0 lladdr 68:a8:6d:50:ca:56 STALE
10.0.0.122 dev eth0 lladdr 34:15:13:fa:a1:1d REACHABLE
10.0.0.51 dev eth0 lladdr 44:f0:34:88:88:7c REACHABLE
10.0.0.55 dev eth0 lladdr d4:ca:6d:68:7f:ab DELAY
10.0.0.106 dev eth0 lladdr 14:49:e0:b2:71:b2 REACHABLE
10.0.0.110 dev eth0 lladdr 98:f4:ab:b8:6d:01 STALE
10.0.3.253 dev eth0.20 lladdr 40:9c:28:6c:0b:f4 STALE
10.0.0.192 dev eth0 lladdr 00:05:cd:9d:14:ac STALE
10.0.0.56 dev eth0 lladdr a8:9c:ed:ce:ea:56 REACHABLE
10.0.3.2 dev eth0.20 lladdr c4:ad:34:e9:0f:af STALE
10.0.0.60 dev eth0 lladdr 2a:f9:2e:c0:0f:45 STALE
10.0.0.115 dev eth0 lladdr 00:d9:d1:ba:9f:1e STALE
10.0.0.52 dev eth0  FAILED
10.0.0.107 dev eth0 lladdr 90:0e:b3:06:6e:a7 STALE
10.0.0.111 dev eth0 lladdr c8:2b:96:10:af:4f STALE
10.0.0.174 dev eth0 lladdr 00:05:cd:fa:59:be STALE
10.0.0.99 dev eth0 lladdr 78:11:dc:55:9e:00 STALE
10.0.0.103 dev eth0 lladdr 04:cf:8c:25:61:92 STALE
10.0.0.91 dev eth0 lladdr c8:f6:50:ac:26:38 STALE
10.0.0.95 dev eth0 lladdr c4:61:8b:33:d9:75 REACHABLE
10.0.0.87 dev eth0 lladdr e4:f0:42:20:42:53 STALE
10.0.0.150 dev eth0 lladdr 36:eb:7b:82:42:42 REACHABLE
10.0.0.138 dev eth0 lladdr 98:f4:ab:f3:43:e2 STALE
10.0.0.120 dev eth0 lladdr c8:2b:96:11:4f:b4 STALE
10.0.0.61 dev eth0 lladdr 98:fe:94:5b:28:0c REACHABLE
10.0.0.112 dev eth0 lladdr c8:2b:96:10:ab:53 STALE
10.0.0.183 dev eth0 lladdr d4:ca:6d:68:7f:ab STALE
10.0.0.104 dev eth0 lladdr b4:e6:2d:4a:5a:a4 STALE
10.0.0.96 dev eth0 lladdr 40:9c:28:6c:0b:f4 REACHABLE
10.0.0.163 dev eth0 lladdr 12:42:e7:8f:9d:54 STALE
10.0.0.100 dev eth0 lladdr 00:04:20:f0:af:64 STALE
10.0.0.80 dev eth0 lladdr 70:88:6b:10:1e:8c STALE
10.0.0.76 dev eth0 lladdr f4:8c:50:75:c1:87 REACHABLE
10.0.0.131 dev eth0 lladdr 08:62:66:bc:8c:bf REACHABLE
10.0.0.68 dev eth0 lladdr 98:f4:ab:b9:24:21 STALE
10.0.0.135 dev eth0 lladdr dc:a6:32:0d:4b:73 STALE
10.0.0.62 dev eth0 lladdr 6c:96:cf:07:8b:4d STALE
10.0.0.50 dev eth0 lladdr cc:50:e3:f3:aa:23 STALE
10.0.0.105 dev eth0 lladdr 98:f4:ab:b8:64:0f STALE
10.0.0.109 dev eth0 lladdr 04:cf:8c:15:bd:5e STALE
10.0.0.101 dev eth0 lladdr 40:31:3c:d0:d9:30 STALE
10.0.0.89 dev eth0 lladdr 08:9e:08:c0:ba:67 STALE
10.0.0.93 dev eth0 lladdr 78:11:dc:eb:54:08 STALE
10.0.0.73 dev eth0 lladdr f0:79:60:a5:0c:4a REACHABLE
10.0.0.77 dev eth0 lladdr f4:5c:89:5d:9c:1c REACHABLE
10.0.0.195 dev eth0 lladdr ec:fa:bc:12:83:9f STALE

However in Pi-hole, nothing shows up.

5

From the admin GUI > Settings > System > Danger Zone, flush the network table and give it some time to repopulate.

6

Ok, the error might be here:

e[K [✗] Failed to truncate network_addresses table
Database location: /etc/pihole/pihole-FTL.db
Output: Error: database disk image is malformed

However this existed before 5.0 as well.
What could I do?
pihole -r ?

7

You can move the existing long term database to a new file and start with a new database using the following commands.

sudo service pihole-FTL stop

sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL-old.db

sudo service pihole-FTL start

If this clears up the problem and you don't need anything from the old database, then remove it

sudo rm /etc/pihole/pihole-FTL-old.db

8

Thanks I will try!

Just for curiosity what is included in this database? This contains the blocked domains or what?

9

The long term database is the query database. This is what populates the query log on the dashboard and the long term database tab. Essentially the history of requests, and the network information is stored there as well.

The gravity database is where the blocklists and groups are kept.

A good description of the databases is here in the documentation (menu on left leads to details of each).

10

Thanks for the clarification!
I will post the results here.

11

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.