# Please explain: Difference in blocking IPv4 and IPv6?

**URL:** <https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475>\
**Category:** Beta 5.0\
**Created:** [January 26, 2020, 4:46pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475 "2020-01-26T16:46:08Z")\
**Posts on this page:** 12\
**Page:** 5

<div class="post-metadata">

**Author:** ![Arno](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/a/a5b964/32.png) [@Arno](https://discourse.pi-hole.net/u/Arno)\
**Post date:** [January 31, 2020, 6:38pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/88 "2020-01-31T18:38:33Z")

</div>

Can't use LTD (lighttpd issue). Can use Query Log - Show all

`apt-get update` on the client gives expected results.

msn.com in browser gives one query (A) OK. I whitelisted msn.com. Next domain in chain is blocked.  
When I remove msn.com from the whitelist it is Blocked (gravity, CNAME)

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [February 3, 2020, 8:27pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/89 "2020-02-03T20:27:36Z")

</div>

15 posts were split to a new topic: [Inconsistend CNAME blocking?](https://discourse.pi-hole.net/t/inconsistend-cname-blocking/27861)

---

<div class="post-metadata">

**Author:** ![Arno](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/a/a5b964/32.png) [@Arno](https://discourse.pi-hole.net/u/Arno)\
**Post date:** [January 31, 2020, 6:57pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/90 "2020-01-31T18:57:26Z")

</div>

> [@DanSchaper](#):
>
> Thanks, so your questions have been answered?

Mine are. Don't know about @jpgpi250.  
Can I go back to `release/v5.0`?  
Will the patch be merged before release? I know I will loose the patch in the meantime.

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [January 31, 2020, 7:04pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/91 "2020-01-31T19:04:39Z")

</div>

> [@Arno](#):
>
> Will the patch be merged before release? I know I will loose the patch in the meantime.

Yes, this will all go in to the release. I don't know if the branches are compatible yet for going back to beta5.0 branch but if you give us a few hours to review and merge that branch in then you should be able to return to beta5.0 branch. Once [Improvements to deep CNAME inspection data processing by DL6ER · Pull Request #685 · pi-hole/FTL · GitHub](https://github.com/pi-hole/FTL/pull/685) shows a purple Merged flair then you should be good to go.

---

<div class="post-metadata">

**Author:** ![Arno](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/a/a5b964/32.png) [@Arno](https://discourse.pi-hole.net/u/Arno)\
**Post date:** [January 31, 2020, 7:09pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/92 "2020-01-31T19:09:15Z")

</div>

Thanks, I will see when it's merged.  
Now going back to `release/v5.0` to rule out if this patch is the cause of a Fatal PHP error in Long term data.

---

<div class="post-metadata">

**Author:** ![Arno](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/a/a5b964/32.png) [@Arno](https://discourse.pi-hole.net/u/Arno)\
**Post date:** [January 31, 2020, 7:23pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/93 "2020-01-31T19:23:55Z")

</div>

There is no PHP error `release/v5.0`.  
Is it correct to apply your patch by checking out core/web/ftl of your patch?

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [January 31, 2020, 7:29pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/94 "2020-01-31T19:29:23Z")

</div>

Please open a new topic for any PHP errors. This topic/thread is resolved.

List any steps you have taken and what errors you are seeing.

---

<div class="post-metadata">

**Author:** ![Arno](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/a/a5b964/32.png) [@Arno](https://discourse.pi-hole.net/u/Arno)\
**Post date:** [January 31, 2020, 7:32pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/95 "2020-01-31T19:32:17Z")

</div>

> [@DanSchaper](#):
>
> Please open a new topic

Sure but I think your patch for this topic is the cause of the PHP error.

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [January 31, 2020, 7:33pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/96 "2020-01-31T19:33:25Z")

</div>

Thanks, 94 posts in a topic is too many. We need to keep things on topic and short to review.

---

<div class="post-metadata">

**Author:** ![Arno](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/a/a5b964/32.png) [@Arno](https://discourse.pi-hole.net/u/Arno)\
**Post date:** [January 31, 2020, 7:41pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/97 "2020-01-31T19:41:44Z")

</div>

Can't reproduce PHP error. Forget about it. Thanks for your help in this topic.

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [February 12, 2020, 6:37pm UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/98 "2020-02-12T18:37:39Z")

</div>

> [@DanSchaper](#):
>
> Once [https://github.com/pi-hole/FTL/pull/685](https://github.com/pi-hole/FTL/pull/685) shows a purple Merged flair then you should be good to go.

Check.

---

<div class="post-metadata">

**Author:** ![pisome](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/f475e1/32.png) [@pisome](https://discourse.pi-hole.net/u/pisome)\
**Post date:** [February 13, 2020, 8:38am UTC](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475/99 "2020-02-13T08:38:23Z")

</div>

Just updated - looking and working fine so far. One small thing happened, don't know if it had something to do with ne new code:

The lighttpd error log was flooded extremely with

> unexpected "=" in pihole-FTL.conf line 4

and a relating PHP error. The reason for this was that the pihole-FTL.conf must be rewritten during the update process and looked like this:

> BLOCKINGMODE=NULL  
> MAXDBDAYS=30  
> RESOLVE\_IPV6=yes  
> RESOLVE\_IPV4=yesPRIVACYLEVEL=0

The web interface did its work anyway. I added the missing linefeed, stopped lighttpd, deleted its large error log, restartet it and no error occured so far.

[Previous page](https://discourse.pi-hole.net/t/please-explain-difference-in-blocking-ipv4-and-ipv6/27475.md?page=4)