Apple Devices Not in Network Overview

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

[All clients/devices, including those made by Apple, have their DNS queries logged in the Network Overview. All queries from all clients show up when using the pihole tail command. Ads are blocked for all clients.]

Actual Behaviour:

[All clients/devices, except for those made by Apple, have their DNS queries logged in the Network Overview. All queries from all clients show up when using the pihole tail command. Ads are blocked for all clients. Apple-made clients will show up in the Network Overview for the first couple queries after connecting to the network, but they will cease appearing after the few (no more than 10) that immediately ping Apple servers. Apple devices (and all devices on the network) only have the IPv4 and IPv6 DNS addresses for the Pi-hole listed in their network configurations, and they cease resolving addresses if the connection to the Pi-hole is lost.]

Debug Token:

[https://tricorder.pi-hole.net/w7rv8dmxr2]

2

I was focused really hard on the Network Overview and totally overlooked the Dashboard. To follow up, it looks like these are showing up as IPv6 clients, and Pi-hole is not associating them with their hostnames. Evidence of this is that the top client list is filled with IPv6 addresses. Any idea why this is happening for just Apple devices?

3

If you aren't using IPv6, then set IPv6 to Link-Local on your Apple devices.

image
image1296×1106 97.9 KB

4

I am using IPv6, though. All of my compatible devices are connected to the internet with IPv6 addresses and pass IPv6 tests. This minor inconvenience isn't enough for me to disable the protocol.

6

IPv6 support for the network table is not yet released. It will be released in the next major version:
https://github.com/pi-hole/FTL/pull/591

7

The missing hostnames for IPv6 clients is a separate issue, and is likely due to the clients not reporting a hostname to Pi-hole when registering with DHCP.

8

Gotcha. My knowledge of IPv6 is pretty small. I'm pretty sure my clients are getting their IPv6 addresses from the router (dd-wrt). I use dnsmasq to to assign the IPv6 DNS address as the pihole (which works). Maybe this will help:

Summary of my setup:
IPv4:
dd-wrt assigns pihole 192.168.1.2. dd-wrt DHCP forwards to 192.168.1.2. Pihole acts as DHCP server for 192.168.1.3-253. (Weird thing happened here. Windows machines couldn't ping pihole by its host name (raspberrypi.). However my Mac could. I created an additional host file on the pihole to define local addresses. This allows the Windows machine to see the ping the pihole and add an SMB share the pi also has.)

IPv6:
dd-wrt uses DHCPv6 to give addresses from Comcast. dnsmasq uses slaac and ra to assign addresses, and it specifies pihole's IPv6 address as the DNS. These are configured manually.* I have the IPv6 box checked on the pihole DHCP settings.

Here are the dnsmasq additional options:

interface=br0
dhcp range=::1000,::FFFF,constructor:br0,slaac,1800
ra-param=*,60,1800 
enable-ra
dhcp-option=option6:dns-server,[2601:285:8180:16d8:eaec:5e44:ae4d:35]

*I feel like here is where I need to do the same as IPv4 and assign a static IPv6 for the pihole using the router's dnsmasq. Then, I assume, the pihole would work properly as the SLAAC+RA, rather than the router. Then hostnames would resolve on the pihole? However, I cannot figure out how to do this. I've done a lot of Googling and I'm not sure if it's even possible. Anyone know? Am I even on the right track?

9

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