Jump to content

Pi-Hole Update to v4.2(.1)


guidol

Recommended Posts

https://pi-hole.net/2019/02/03/pi-hole-v4-2-available-with-shared-memory-new-blocking-modes-and-more/

 

v4.2.1 Hotfix
We have released a small hotfix which addresses possible crashes experienced for users without libcap capabilities

(running FTLDNS under root). For most users, this update will not change anything.

 

HIGHLIGHTS

 

New Blocking Mode
We’ve added a new blocking mode (NODATA), where blocked requested are replied with a status code of NOERROR

and A / AAAA records are empty.  

It’s unclear if there are advantages to this mode over others, but you’re welcome to experiment with it.

 

Shared Memory
In preparation of the new API we are working on, FTLDNS will now store its data in a shared-memory space,

so that the API can come in and read from that memory to fulfill requests.  

In short, this means FTLDNS will be even lighter as it doesn’t have to care about sending the statistics to some requester.  

Instead, it will concentrate on generating the statistics and the API can read FTL’s data directly,

resulting in reduced delays in the API.

 

wpad Vulnerability Fix
We previously mentioned how you could work around a vulnerability regarding wpad entries.  

This fix is now in place as suggested by dnsmaq.conf.example.

 

Fixes And Tweaks
We updated SQLite to 3.26.0
We fixed the query status if a forwarded query was partially replied to from the cache
We now prevent multiple static DHCP entries with same IP
And more…

 

Docker Version Also Updated
We heard your feedback and we made sure to coordinate better to release our traditional install and our Docker install together.

The docker image will be released when testing is complete.

Link to comment
Share on other sites

https://pi-hole.net/2019/02/18/hotfix-release-of-pi-hole-v4-2-2/

 

Hotfix Release Of Pi-hole v4.2.2
telekrmor  2019-02-18  Updates  1

We released two small updates to Core and FTL, which will bump both to version 4.2.2.

In the Core codebase, some users experienced crashes if their systems were without 
libcap support which caused FTLDNS to run as root, later dropping to the unprivileged 
user pihole. 
As the shared memory objects used for FTLDNS are created before this switch, 
issues such as failing to access, reallocate, or delete the shared memory were seen. 

For most of you, this update will be transparent.

Meanwhile, the release of FTLDNS will let FTLDNS continue running as root if necessary 
on the given system. 

This will let FTLDNS retain access to its shared memory.  

We’ve added one related feature that reports both the user pihole-FTL started as and 
the user pihole-FTL crashed as in case it crashes and generated a crash ticket in pihole-FTL.log.

Also included, is a fix for the blocking status display for NODATA and NXDOMAIN blocking modes, 
which were incorrectly reported as OK (cached) although they were blocking just fine by FTL v4.2.

Finally, there is a fix that also fixes FTL crashing by adjusting the overTime data structure.

Thanks for reporting these issues and help us making Pi-hole a better software!

 

Link to comment
Share on other sites

https://github.com/pi-hole/FTL/releases/tag/v4.2.3
Pi-hole FTL v4.2.3

Quote

@DL6ER DL6ER released this 15 hours ago

This is a patch release following on Pi-hole FTL v4.2.2.

We apologize for the large number of updates in a short time but a fundamental change

in our memory handling was causing unforeseeable issues which this patch release fixes

now once and for all.

 

This PR consist of only one pull request #519.

https://github.com/pi-hole/FTL/pull/519

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines