Interfaces Tab only shows eth0 and lo Interfaces

darkexplosiveqwx · January 24, 2025, 8:45pm

The Interfaces Tab (Tools/Interfaces) in the Web Interface only shows eth0 and lo, although
wlan0, wlan1 and wg0 are also available. wlan1 and wg0 are connected and devices from wg0 are sending queries to Pi-hole. The setting dns.interface is set to wg0.
DHCP is disabled.
I am wondering if this is intentional before submitting a bug report.

I am on a Raspberry Pi 5 and my versions are Core 0f318027, FTL ead34f5e, Web 9913f888on v6.

rdwebdesign · January 24, 2025, 8:50pm

Please include a debug log:

Run the following command from the Pi-hole host terminal:

pihole -d

Answer YES when asked to upload the log and post here just the token URL that is generated after the upload process.

darkexplosiveqwx · January 24, 2025, 8:55pm

My debug log is https://tricorder.pi-hole.net/lWvN2ePx/

rdwebdesign · January 24, 2025, 8:55pm

Note:

The page should show all interfaces. Look at the screenshots here:

We will take a look in your debug log to try to understand what is happening in your case.

darkexplosiveqwx · January 24, 2025, 9:03pm

running nmcli dev gives the output of:


DEVICE         TYPE       STATE                   CONNECTION         
eth0           ethernet   connected               Wired connection 1 
wlan1          wifi       connected               MinasMorgul        
lo             loopback   connected (externally)  lo                 
wg0            wireguard  connected (externally)  wg0                
wlan0          wifi       disconnected            --                 
p2p-dev-wlan0  wifi-p2p   disconnected            --

DL6ER · January 25, 2025, 10:30am

Please check if /var/log/pihole/FTL.log contains any errors when you open the interfaces page.

darkexplosiveqwx · January 25, 2025, 11:02am

Opening up the Interfaces tab will not result in entries(neither errors not normal entries) in both FTL.log and webserver.log.

DL6ER · January 25, 2025, 11:24am

Please run

sudo pihole checkout ftl tweak/nlinks

and then try to open the page again.

There should now be plenty of logging in FTL.log

darkexplosiveqwx · January 25, 2025, 11:36am

Trying to switch the branch outputs:

 Please note that changing branches severely alters your Pi-hole subsystems
  Features that work on the master branch, may not on a development branch
  This feature is NOT supported unless a Pi-hole developer explicitly asks!
  Have you read and understood this? [y/N] y

  [i] Checking for availability of branch tweak/nlinks on GitHub
  [✓] Branch tweak/nlinks exists on GitHub
  [i] Checking for pihole-FTL-arm64 binary on https://ftl.pi-hole.net
  [✗] Binary for requested branch is not available, please try again later.
      If the issue persists, please contact Pi-hole Support and ask them to re-generate the binary.

DL6ER · January 25, 2025, 11:38am

I just checked and see that the arm64 binary build failed. We are seeing intermittent issues with Github Actions since at least yesterday. I can restart the build only in a few minutes and will come back to you. Sorry for the trouble.

DL6ER · January 25, 2025, 11:57am

@darkexplosiveqwx please try again, it worked on a retry.

darkexplosiveqwx · January 25, 2025, 12:28pm

Now when selecting the Interfaces tab I get the output of:

2025-01-25 13:26:16.914 INFO called nlroutes
2025-01-25 13:26:16.914 INFO nlrequest
2025-01-25 13:26:16.914 INFO nlgetmsg
2025-01-25 13:26:16.914 INFO parse_nl_msg(856)
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO nlgetmsg
2025-01-25 13:26:16.914 INFO parse_nl_msg(2592)
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO parse route
2025-01-25 13:26:16.914 INFO nlgetmsg
2025-01-25 13:26:16.914 INFO parse_nl_msg(20)
2025-01-25 13:26:16.914 INFO called nllinks
2025-01-25 13:26:16.914 INFO nlrequest
2025-01-25 13:26:16.914 INFO nlgetmsg
2025-01-25 13:26:16.914 INFO parse_nl_msg(4096)
2025-01-25 13:26:16.914 INFO parse link
2025-01-25 13:26:16.914 INFO Parsing link 1 -> lo
2025-01-25 13:26:16.915 INFO parse link
2025-01-25 13:26:16.915 INFO Parsing link 2 -> eth0
2025-01-25 13:26:16.915 INFO nlgetmsg
2025-01-25 13:26:16.915 INFO parse_nl_msg(20)
2025-01-25 13:26:16.915 INFO called nladdrs
2025-01-25 13:26:16.915 INFO nlrequest
2025-01-25 13:26:16.915 INFO nlgetmsg
2025-01-25 13:26:16.915 INFO parse_nl_msg(328)
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 1 of lo
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 2 of eth0
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 4 of wlan1
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 5 of wg0
2025-01-25 13:26:16.915 INFO nlgetmsg
2025-01-25 13:26:16.915 INFO parse_nl_msg(576)
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 1 of lo
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 2 of eth0
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 2 of eth0
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 2 of eth0
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 4 of wlan1
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 4 of wlan1
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 4 of wlan1
2025-01-25 13:26:16.915 INFO parse addr
2025-01-25 13:26:16.915 INFO Parsing address 5 of wg0
2025-01-25 13:26:16.915 INFO nlgetmsg
2025-01-25 13:26:16.915 INFO parse_nl_msg(20)

DL6ER · January 25, 2025, 6:07pm

This is interesting to see. Se we indeed get only the interfaces lo and eth0 when requesting links from the kernel but we do get addresses for the other interfaces and I did just verify that I do get the expected output locally for a Wireguard interface.

Please update the branch using the checkout command again (I checked that the binaries have succeeded building this time) and, thereafter, enable the new netlink debug mode like

sudo pihole-FTL --config debug.netlink true

Then load the interfaces page again and please post the log content again as you already did above. I added some more debug output, hopefully it leads somewhere.

The command pihole-FTL --hash returns 9c69a0be if you have the right binary.

darkexplosiveqwx · January 25, 2025, 6:13pm

I think i was a bit too fast here just now, i installed a ftl update while it was still building, commit was 1 minute ago then, but now i updated again and the new output is:

2025-01-25 19:10:33.845 DEBUG_NETLINK Called nlroutes
2025-01-25 19:10:33.845 DEBUG_NETLINK nlrequest
2025-01-25 19:10:33.845 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:10:33.845 DEBUG_NETLINK Calling parse_nl_msg (856)
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 68/856, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 254 is default via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 68/788, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 254 is default via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 52/720, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 254 is 172.29.0.2 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 52/668, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 254 is 172.29.0.3 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 68/616, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 254 is 192.168.178.0 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 68/548, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 254 is 192.168.179.0 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/480, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 255 is 127.0.0.0 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/420, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 255 is 127.0.0.1 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/360, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 255 is 127.255.255.255 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/300, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 255 is 172.29.0.1 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/240, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 255 is 192.168.178.158 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/180, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 255 is 192.168.178.255 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/120, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 255 is 192.168.179.6 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/60, flags 0x2, sqe 0)
2025-01-25 19:10:33.845 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.845 DEBUG_NETLINK Parsing IPv4 route: table 255 is 192.168.179.255 via direct
2025-01-25 19:10:33.845 DEBUG_NETLINK Next nl_msg_type: 0
2025-01-25 19:10:33.845 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:10:33.846 DEBUG_NETLINK Calling parse_nl_msg (2980)
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2980, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is 2001:9e8:b3ef:2000:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2864, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is 2001:9e8:b3ef:2001:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 136/2748, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is 2001:9e8:b3ef:2000:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 136/2612, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is 2001:9e8:b3ef:2000:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2476, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is fd00:abcd:4567:1:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2360, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is fde6:4eec:57f7:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 136/2244, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is fde6:4eec:57f7:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2108, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is fde6:4eec:57f7:1:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 136/1992, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is fde6:4eec:57f7:1:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1856, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is fe80:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1740, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is fe80:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1624, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is default via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1508, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 254 is default via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1392, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is ::1 via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1276, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is 2001:9e8:b3ef:2000:c4:bb4e:cf36:dbeb via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1160, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is 2001:9e8:b3ef:2001:a918:a49e:3a79:ec7e via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1044, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is fd00:abcd:4567:1:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/928, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is fd00:abcd:4567:1::1 via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/812, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is fde6:4eec:57f7:0:51d7:eb29:e44:13d8 via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/696, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is fde6:4eec:57f7:1:d625:71c4:fe4b:3b3e via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/580, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is fe80::c414:a21d:477e:8fb6 via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/464, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is fe80::ecd0:451b:792b:f8eb via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/348, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing IPv6 route: table 255 is ff00:: via direct
2025-01-25 19:10:33.846 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/232, flags 0x2, sqe 0)
2025-01-25 19:10:33.846 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing IPv6 route: table 255 is ff00:: via direct
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/116, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing route
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing IPv6 route: table 255 is ff00:: via direct
2025-01-25 19:10:33.847 DEBUG_NETLINK Next nl_msg_type: 0
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling parse_nl_msg (20)
2025-01-25 19:10:33.847 DEBUG_NETLINK Next nl_msg_type: 3
2025-01-25 19:10:33.847 DEBUG_NETLINK Called nllinks
2025-01-25 19:10:33.847 DEBUG_NETLINK nlrequest
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling parse_nl_msg (4112)
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 16, len 1428/4112, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing link
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing unspec link 1 -> lo
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 16, len 1488/2684, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing link
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing unspec link 2 -> eth0
2025-01-25 19:10:33.847 DEBUG_NETLINK Next nl_msg_type: 16
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling parse_nl_msg (20)
2025-01-25 19:10:33.847 DEBUG_NETLINK Next nl_msg_type: 3
2025-01-25 19:10:33.847 DEBUG_NETLINK Called nladdrs
2025-01-25 19:10:33.847 DEBUG_NETLINK nlrequest
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling parse_nl_msg (328)
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 76/328, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet address of iface lo (1): 127.0.0.1/8
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 88/252, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet address of iface eth0 (2): 192.168.178.158/24
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 88/164, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet address of iface wlan1 (4): 192.168.179.6/24
2025-01-25 19:10:33.847 DEBUG_NETLINK Interface wlan1 undefined, skipping
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 76/76, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet address of iface wg0 (5): 172.29.0.1/32
2025-01-25 19:10:33.847 DEBUG_NETLINK Interface wg0 undefined, skipping
2025-01-25 19:10:33.847 DEBUG_NETLINK Next nl_msg_type: 0
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling parse_nl_msg (576)
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/576, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet6 address of iface lo (1): ::1/128
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/504, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet6 address of iface eth0 (2): 2001:9e8:b3ef:2000:c4:bb4e:cf36:dbeb/64
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/432, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet6 address of iface eth0 (2): fde6:4eec:57f7:0:51d7:eb29:e44:13d8/64
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/360, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet6 address of iface eth0 (2): fe80::ecd0:451b:792b:f8eb/64
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/288, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet6 address of iface wlan1 (4): 2001:9e8:b3ef:2001:a918:a49e:3a79:ec7e/64
2025-01-25 19:10:33.847 DEBUG_NETLINK Interface wlan1 undefined, skipping
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/216, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet6 address of iface wlan1 (4): fde6:4eec:57f7:1:d625:71c4:fe4b:3b3e/64
2025-01-25 19:10:33.847 DEBUG_NETLINK Interface wlan1 undefined, skipping
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/144, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet6 address of iface wlan1 (4): fe80::c414:a21d:477e:8fb6/64
2025-01-25 19:10:33.847 DEBUG_NETLINK Interface wlan1 undefined, skipping
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/72, flags 0x2, sqe 0)
2025-01-25 19:10:33.847 DEBUG_NETLINK parsing address
2025-01-25 19:10:33.847 DEBUG_NETLINK Parsing inet6 address of iface wg0 (5): fd00:abcd:4567:1::1/64
2025-01-25 19:10:33.847 DEBUG_NETLINK Interface wg0 undefined, skipping
2025-01-25 19:10:33.847 DEBUG_NETLINK Next nl_msg_type: 0
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:10:33.847 DEBUG_NETLINK Calling parse_nl_msg (20)
2025-01-25 19:10:33.847 DEBUG_NETLINK Next nl_msg_type: 3

In the intermediary patch or what i installed the output was:

2025-01-25 19:06:28.981 WARNING Netlink: Interface wlan1 undefined
2025-01-25 19:06:28.981 WARNING Netlink: Interface wg0 undefined
2025-01-25 19:06:28.981 WARNING Netlink: Interface wlan1 undefined
2025-01-25 19:06:28.981 WARNING Netlink: Interface wlan1 undefined
2025-01-25 19:06:28.981 WARNING Netlink: Interface wlan1 undefined
2025-01-25 19:06:28.981 WARNING Netlink: Interface wg0 undefined

DL6ER · January 25, 2025, 6:25pm

It seems like your kernel is maxing out the buffer in the first round, causing some interface information to be cropped. When we go and try to get the rest of it, we only get some debris which cannot be parsed. This is very different that what my kernel replies with, which kernel do you run? For me, it is

$ uname -a
Linux ryzen 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec  5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Please try again with the most recent commit 1b3c3da9 which tries to maybe remedy/circumvent this by doubling the allowed buffer size from 4kB to 8kB.

darkexplosiveqwx · January 25, 2025, 6:27pm

uname -a outputs

Linux blueberrypi 6.6.74-v8-16k+ #1842 SMP PREEMPT Fri Jan 24 16:20:20 GMT 2025 aarch64 GNU/Linux

I am running the normal Raspbian which uses 6.6.z LTS kernel.
I regularly run sudo rpi-update so i am using the latest dev 6.6.z kernel.

darkexplosiveqwx · January 25, 2025, 6:33pm

Updating take some minutes due to it refreshing my 100 gravity lists.
This update fixed the issue and all interfaces now show up.

But still, here is the current output:

2025-01-25 19:30:00.096 DEBUG_ANY dnsmasq received signal 17
2025-01-25 19:30:00.100 DEBUG_ANY dnsmasq received signal 17
2025-01-25 19:30:51.419 DEBUG_NETLINK Called nlroutes
2025-01-25 19:30:51.419 DEBUG_NETLINK nlrequest
2025-01-25 19:30:51.419 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:30:51.419 DEBUG_NETLINK Calling parse_nl_msg (856)
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing Netlink message (type 24, len 68/856, flags 0x2, sqe 0)
2025-01-25 19:30:51.419 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing IPv4 route: table 254 is default via direct
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing Netlink message (type 24, len 68/788, flags 0x2, sqe 0)
2025-01-25 19:30:51.419 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing IPv4 route: table 254 is default via direct
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing Netlink message (type 24, len 52/720, flags 0x2, sqe 0)
2025-01-25 19:30:51.419 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing IPv4 route: table 254 is 172.29.0.2 via direct
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing Netlink message (type 24, len 52/668, flags 0x2, sqe 0)
2025-01-25 19:30:51.419 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing IPv4 route: table 254 is 172.29.0.3 via direct
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing Netlink message (type 24, len 68/616, flags 0x2, sqe 0)
2025-01-25 19:30:51.419 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing IPv4 route: table 254 is 192.168.178.0 via direct
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing Netlink message (type 24, len 68/548, flags 0x2, sqe 0)
2025-01-25 19:30:51.419 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing IPv4 route: table 254 is 192.168.179.0 via direct
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/480, flags 0x2, sqe 0)
2025-01-25 19:30:51.419 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing IPv4 route: table 255 is 127.0.0.0 via direct
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/420, flags 0x2, sqe 0)
2025-01-25 19:30:51.419 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing IPv4 route: table 255 is 127.0.0.1 via direct
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/360, flags 0x2, sqe 0)
2025-01-25 19:30:51.419 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.419 DEBUG_NETLINK Parsing IPv4 route: table 255 is 127.255.255.255 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/300, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv4 route: table 255 is 172.29.0.1 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/240, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv4 route: table 255 is 192.168.178.158 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/180, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv4 route: table 255 is 192.168.178.255 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/120, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv4 route: table 255 is 192.168.179.6 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 60/60, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv4 route: table 255 is 192.168.179.255 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Next nl_msg_type: 0
2025-01-25 19:30:51.420 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:30:51.420 DEBUG_NETLINK Calling parse_nl_msg (2980)
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2980, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is 2001:9e8:b3ef:2000:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2864, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is 2001:9e8:b3ef:2001:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 136/2748, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is 2001:9e8:b3ef:2000:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 136/2612, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is 2001:9e8:b3ef:2000:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2476, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is fd00:abcd:4567:1:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2360, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is fde6:4eec:57f7:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 136/2244, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is fde6:4eec:57f7:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/2108, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is fde6:4eec:57f7:1:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 136/1992, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is fde6:4eec:57f7:1:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1856, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is fe80:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1740, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is fe80:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1624, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is default via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1508, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 254 is default via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1392, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is ::1 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1276, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is 2001:9e8:b3ef:2000:c4:bb4e:cf36:dbeb via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1160, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is 2001:9e8:b3ef:2001:a918:a49e:3a79:ec7e via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/1044, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is fd00:abcd:4567:1:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/928, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is fd00:abcd:4567:1::1 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/812, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is fde6:4eec:57f7:0:51d7:eb29:e44:13d8 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/696, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is fde6:4eec:57f7:1:d625:71c4:fe4b:3b3e via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/580, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is fe80::c414:a21d:477e:8fb6 via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/464, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is fe80::ecd0:451b:792b:f8eb via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/348, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is ff00:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/232, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is ff00:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing Netlink message (type 24, len 116/116, flags 0x2, sqe 0)
2025-01-25 19:30:51.420 DEBUG_NETLINK parsing route
2025-01-25 19:30:51.420 DEBUG_NETLINK Parsing IPv6 route: table 255 is ff00:: via direct
2025-01-25 19:30:51.420 DEBUG_NETLINK Next nl_msg_type: 0
2025-01-25 19:30:51.420 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:30:51.420 DEBUG_NETLINK Calling parse_nl_msg (20)
2025-01-25 19:30:51.420 DEBUG_NETLINK Next nl_msg_type: 3
2025-01-25 19:30:51.420 DEBUG_NETLINK Called nllinks
2025-01-25 19:30:51.420 DEBUG_NETLINK nlrequest
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling parse_nl_msg (7280)
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 16, len 1428/7280, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing link
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing unspec link 1 -> lo
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 16, len 1488/5852, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing link
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing unspec link 2 -> eth0
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 16, len 1476/4364, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing link
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing unspec link 3 -> wlan0
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 16, len 1464/2888, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing link
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing unspec link 4 -> wlan1
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 16, len 1424/1424, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing link
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing unspec link 5 -> wg0
2025-01-25 19:30:51.421 DEBUG_NETLINK Next nl_msg_type: 0
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling parse_nl_msg (20)
2025-01-25 19:30:51.421 DEBUG_NETLINK Next nl_msg_type: 3
2025-01-25 19:30:51.421 DEBUG_NETLINK Called nladdrs
2025-01-25 19:30:51.421 DEBUG_NETLINK nlrequest
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling parse_nl_msg (328)
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 76/328, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet address of iface lo (1): 127.0.0.1/8
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 88/252, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet address of iface eth0 (2): 192.168.178.158/24
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 88/164, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet address of iface wlan1 (4): 192.168.179.6/24
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 76/76, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet address of iface wg0 (5): 172.29.0.1/32
2025-01-25 19:30:51.421 DEBUG_NETLINK Next nl_msg_type: 0
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling parse_nl_msg (576)
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/576, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet6 address of iface lo (1): ::1/128
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/504, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet6 address of iface eth0 (2): 2001:9e8:b3ef:2000:c4:bb4e:cf36:dbeb/64
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/432, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet6 address of iface eth0 (2): fde6:4eec:57f7:0:51d7:eb29:e44:13d8/64
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/360, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet6 address of iface eth0 (2): fe80::ecd0:451b:792b:f8eb/64
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/288, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet6 address of iface wlan1 (4): 2001:9e8:b3ef:2001:a918:a49e:3a79:ec7e/64
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/216, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet6 address of iface wlan1 (4): fde6:4eec:57f7:1:d625:71c4:fe4b:3b3e/64
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/144, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet6 address of iface wlan1 (4): fe80::c414:a21d:477e:8fb6/64
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing Netlink message (type 20, len 72/72, flags 0x2, sqe 0)
2025-01-25 19:30:51.421 DEBUG_NETLINK parsing address
2025-01-25 19:30:51.421 DEBUG_NETLINK Parsing inet6 address of iface wg0 (5): fd00:abcd:4567:1::1/64
2025-01-25 19:30:51.421 DEBUG_NETLINK Next nl_msg_type: 0
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling nlgetmsg
2025-01-25 19:30:51.421 DEBUG_NETLINK Calling parse_nl_msg (20)
2025-01-25 19:30:51.421 DEBUG_NETLINK Next nl_msg_type: 3

darkexplosiveqwx · January 25, 2025, 6:39pm

Both my WLAN adapters show up as Type: ether
wlan0 is the built-in and wlan1 is a USB Adapter.

DL6ER · January 25, 2025, 6:57pm

Type: ether is correct even for WiFi interfaces as they are still Ethernet devices in the ARP sense. I will still look at reproducing this locally to analyze the issue (it seems to happen with arm64 sometimes) but I will first need to buy a Raspberry Pi 5 for this.

DL6ER · January 28, 2025, 7:12pm

Raspberry Pi 5 received yesterday and dove deeply into the kernel source code and documentation. The result is

github.com/pi-hole/FTL

Netlink tweaks

pi-hole:development ← pi-hole:tweak/nlinks

opened 07:10PM - 28 Jan 25 UTC

DL6ER

+205 -55

# What does this implement/fix? Following an issue report on Discourse, menti…oning that not all interfaces were shown, I dived deeply into both the Netlink documentation as well as the kernel source code realizing that they are not always congruent. I modified our Netlink code in a way that would be consistent with how the kernel does it but still work if the way the kernel does it would be modified to behave as documented (I know this sounds a bit weird). In addition, we now have a lot of additional code that handles warning the user in case anything unexpected (most worth noticing would be Netlink packet truncation). This PR adds the new config option `debug.netlink` obviously defaulting to `false`. Extensively tested on three x86_64, a Raspberry Pi 1 B+, 4 and a 5 running the `aarch64` kernel. On the latter, the problem was originally reported and I was able to reproduce it on this hardware. --- **Related issue or feature (if applicable):** N/A **Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A --- **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 2. I have commented my proposed changes within the code. 3. I am willing to help maintain this change if there are issues with it later. 4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) ## Checklist: - [x] The code change is tested and works locally. - [x] I based my code and PRs against the repositories `developmental` branch. - [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions - [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship - [x] I have read the above and my PR is ready for review.

which should work. Could you please check if the current state of this same branch is still

returning the interfaces are expected, and
NOT showing any Netlink-related warnings

for you?

It'd probably be the easiest if you first turn of debug.netlink to avoid cluttering the log with content.