IPv6 address question

Hi,
I think I'm having this problem.


I don't understand how the raspberry shows up with the same IPV6 as the router (localhost).
I did a pihole -d and I get the alert of:

"IPv6 address(es) bound to the eth0 interface:
2001:8a0:574c:e301:4d99:d1e0:7c76:4db3 does not match the IP found in /etc/pihole/setupVars.conf
fe80::94e8:3f10:e797:c26c does not match the IP found in /etc/pihole/setupVars.conf "

but I set the IPV6 in the setupVars.conf and did pihole -g but it still shows this..
pihole_debug.txt (35.4 KB)

I've uploaded the debug log.
Can anyone help?

Those are reverse lookups (Type) for a single IPv6 address (Domain) as requested by raspberrypi and localhost (Client) where no hostname was ever returned as an answer (Reply) (terms in brackets refer to your screenshot's respective column).

From the screenshot itself, it is not deducible which device in your network would have that IPv6 address assigned.

Considering your debug log and assuming that your posted excerpt is complete, it can however be concluded that the requested IPv6 does not match your Pi-hole's public IPv6 address, as the latter ends in 4db3 and the former in 04ef.
At the same time, it can be concluded from the respective IPv6 prefixes that those public IPv6 addresses from both your screenshot as well as your debug log belong to your local network.

All in all, this wouldn't constitute an error at all, and it specfically doesn't show that your router and Pi-hole would share the same IP address.

If that doesn't help, please try to rephrase your question.

2 Likes

Hi and thank you for your reply.

I've been digging through this for a while now and I'm coming to some conclusions.
I'm noticing raspberrypi is sharing the same IPv6 address as my mobile phone. I don't know how is this happening.
We can see in the pihole_debug attached that the IPv6 is 2001:8a0:574c:e301:4d99:d1e0:7c76:4db3
But on the Clients (also see attached images) it associates another IPv6 to raspberrypi..

How can I fix this?

raspberry pihole_debug.txt (30.5 KB)

What's the output of the following commands when issued for each of your IPv6 addresses (ending in :4db3 and :c768)?

dig -x <your-ipv6-address-here>

(Replace <your-ipv6-address-here> with the respective full IPv6 address.)

1 Like

All IPs shown there are also IPs which made requests to your Pi-hole. This is guaranteed. So your IP address may have changed over time. Pi-hole still handles them as different devices as you may very well have two raspberrypi in the same network, right?

No, I have only one raspberrypi.
The IPv6 address 2001:8a0:574c:e301:30a0:4f96:b62b:c768 is from my mobile phone wifi 5GHz.
I don't understand why it is being associated with the raspberrypi..

Your output shows that dig was using your router as DNS server.

Please repeat the commands, forcing lookup through your Pi-hole's IP this time:

dig -x <your-ipv6-address-here> @192.168.1.88
PS: (click for more)

Please consider posting the textual output of commands.
It might be necessary to reenact or reuse some of it, and that is easier to do for both other potential readers and me with living text instead of a “ dead ” screenshot.

You can paste your output here and format it by selecting a text passage and applying the </> Preformatted text option from the menu. :wink:

PPS:
In some shells (e.g. puTTY) it is enough to highlight text to copy it into the clipboard, from where it can be pasted here.

1 Like

I thought about posting the text but it looks off/not formatted for easy reading..

pi@raspberrypi:~ $ dig -x 2001:8a0:574c:e301:30a0:4f96:b62b:c768@192.168.1.88                                                                                                                                                                                                                         ; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> -x 2001:8a0:574c:e301:30a0:4f96:b62b:c768@192.168.1.88                                              ;; global options: +cmd                                                                                                                            ;; Got answer:                                                                                                                                     ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46842                                                                                         ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1                                                                                                                                                                                                                               ;; OPT PSEUDOSECTION:                                                                                                                              ; EDNS: version: 0, flags:; udp: 4010                                                                                                              ;; QUESTION SECTION:                                                                                                                               ;88.1.168.2001:8a0:574c:e301:30a0:4f96:b62b:c768\@192.in-addr.arpa. IN PTR                                                                                                                                                                                                                            ;; AUTHORITY SECTION:                                                                                                                              in-addr.arpa.           2391    IN      SOA     b.in-addr-servers.arpa. nstld.iana.org. 2020061019 1800 900 604800 3600                                                                                                                                                                               ;; Query time: 156 msec                                                                                                                            ;; SERVER: 192.168.1.254#53(192.168.1.254)                                                                                                         ;; WHEN: ter jun 30 12:31:55 WEST 2020                                                                                                             ;; MSG SIZE  rcvd: 161  
                                                                                                                                                                                                                                                                              pi@raspberrypi:~ $ dig -x 2001:8a0:574c:e301:4d99:d1e0:7c76:4db3@192.168.1.88                                                                                                                                                                                                                         ; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> -x 2001:8a0:574c:e301:4d99:d1e0:7c76:4db3@192.168.1.88                                              ;; global options: +cmd                                                                                                                            ;; Got answer:                                                                                                                                     ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40517                                                                                         ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1                                                                                                                                                                                                                               ;; OPT PSEUDOSECTION:                                                                                                                              ; EDNS: version: 0, flags:; udp: 4010                                                                                                              ;; QUESTION SECTION:                                                                                                                               ;88.1.168.2001:8a0:574c:e301:4d99:d1e0:7c76:4db3\@192.in-addr.arpa. IN PTR                                                                                                                                                                                                                            ;; AUTHORITY SECTION:                                                                                                                              in-addr.arpa.           1717    IN      SOA     b.in-addr-servers.arpa. nstld.iana.org. 2020061019 1800 900 604800 3600                                                                                                                                                                               ;; Query time: 212 msec                                                                                                                            ;; SERVER: 192.168.1.254#53(192.168.1.254)                                                                                                         ;; WHEN: ter jun 30 12:35:51 WEST 2020                                                                                                             ;; MSG SIZE  rcvd: 161

Also I checked on the router again and DHCP is off.Screenshot_1

You missed a (significant) space between address and the server.
(:c768@192. vs. correct :c768 @192.)

1 Like
pi@raspberrypi:~ $ dig -x 2001:8a0:574c:e301:30a0:4f96:b62b:c768 @192.168.1.88

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> -x 2001:8a0:574c:e301:30a0:4f96:b62b:c768 @192.168.1.88
;; global options: +cmd
;; Got answer:         
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 57727 
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1     

;; OPT PSEUDOSECTION:  
; EDNS: version: 0, flags:; udp: 1452      

;; QUESTION SECTION:   
;8.6.7.c.b.2.6.b.6.9.f.4.0.a.0.3.1.0.3.e.c.4.7.5.0.a.8.0.1.0.0.2.ip6.arpa. IN PTR

;; Query time: 4623 msec   
;; SERVER: 192.168.1.88#53(192.168.1.88)   
;; WHEN: ter jun 30 13:06:25 WEST 2020     
;; MSG SIZE  rcvd: 101      
pi@raspberrypi:~ $ dig -x 2001:8a0:574c:e301:4d99:d1e0:7c76:4db3 @192.168.1.88   

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> -x 2001:8a0:574c:e301:4d99:d1e0:7c76:4db3 @192.168.1.88     
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44764  
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1  

;; OPT PSEUDOSECTION:  ; EDNS: version: 0, flags:; udp: 4096      

;; QUESTION SECTION:   ;3.b.d.4.6.7.c.7.0.e.1.d.9.9.d.4.1.0.3.e.c.4.7.5.0.a.8.0.1.0.0.2.ip6.arpa. IN PTR

;; ANSWER SECTION: 
3.b.d.4.6.7.c.7.0.e.1.d.9.9.d.4.1.0.3.e.c.4.7.5.0.a.8.0.1.0.0.2.ip6.arpa. 2 IN PTR raspberrypi.  

;; Query time: 1 msec  
;; SERVER: 192.168.1.88#53(192.168.1.88)   
;; WHEN: ter jun 30 13:06:38 WEST 2020     
;; MSG SIZE  rcvd: 126

From what I understood, c768 doesn't return the hostname while 4db3 returns the raspberrypi, as it should.

Yes. But you could have two. Pi-hole cannot know this. Someone told it that this IP has the host name raspberrypi

That's correct, and from that output, we can conclude that Pi-hole does not associate your mobile phone's :c768 address with a hostname of raspberrypi.

Rather, there seems to be no hostname at all associated with your mobile, which is unusual. Most mobile phones will also try to register a name when requesting an IPv4 address via DHCP. IPv6 addresses get associated with that hostname by virtue of using the same MAC on the link, at least when Pi-hole is acting as DHCP (which it is in your case, right?).

Does your mobile phone appear with a DHCP lease under Settings | DHCP ?

1 Like

Only the IPv4 of the phone shows up there. Strange.
Is there a way to flush all the leases or restart the DHCP to gather the devices again?
I'm considering turning off IPv6 on DHCP after all this...

PS.- Thank you so much for helping me Bucking_Horn

That's ok.
Devices are not at all obliged to request an IPv6 address via DHCPv6. In fact, most won't (Android doesn't even support DHCPv6). Commonly, they will calculate an IPv6 address for themselves, respecting only some information as advertised by the router via RAs (most importantly, the IPv6 prefix),

But if an IPv4 DHCP lease would have been absent for your Smartphone, it could have explained why there is no hostname for your corresponding public IPv6 address.

From your screenshot, I'd expect a reverse lookup to return gonsaplus as hostname.

Does that IPv4 indeed match the IP on your mobile?
Your earlier mobile screen only shows DNS and IPv6 info, not IPv4.

1 Like
pi@raspberrypi:~ $ host gonsaplus                                                                                                               Host gonsaplus not found: 3(NXDOMAIN)                                                                                                           pi@raspberrypi:~ $ host 192.168.1.80                                                                                                            Host 80.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)

And in a screenshot a few posts above you can see the IPv6 address of the phone.

@ Bucking_Horn I found this:

This is where it is associating the IP 192.168.1.80 to raspberrypi, although as we know the real one is 192.168.1.88.
How can I fix this? Can I flush these entries?

So I pressed the Flush Network Table in the settings, it wiped all these entries but put back the IP ending in 80 as raspberrypi...

This confirms that :c767 and .80 are related to the same device.
It shows the same unwanted and yet unexplainable association of raspberrypi with those addresses.

Now that we've verified that .80 is your smartphone's IPv4, what does a dig return for that IPv4 address?

1 Like
pi@raspberrypi:~ $ dig -x 192.168.1.80 @192.168.1.88

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> -x 192.168.1.80 @192.168.1.88
;; global options: +cmd
;; Got answer:  
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56562   
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1     

;; OPT PSEUDOSECTION:      
; EDNS: version: 0, flags:; udp: 4096 

;; QUESTION SECTION:       
;80.1.168.192.in-addr.arpa.     IN      PTR

;; ANSWER SECTION:         
80.1.168.192.in-addr.arpa. 2    IN      PTR     gonsaplus.amor.  

;; Query time: 1 msec      
;; SERVER: 192.168.1.88#53(192.168.1.88)         
;; WHEN: qua jul 01 11:06:38 WEST 2020
;; MSG SIZE  rcvd: 82

Yes now the return of dig is right, it associates with the right hostname gonsaplus.
How and why is it showing up in the network table and clients as raspberrypi???