Moto
July 15, 2024, 2:52pm
1
I have pihole running on 2 Pis here
On both I have run pihole -up
One pihole shows available updates, one does not
On the one showing available updates I have deleted /etc/pihole/versions and run pihole updatchecker
CORE_VERSION=v5.18.2-391-gb22731c6
CORE_BRANCH=development-v6
CORE_HASH=b22731c6
GITHUB_CORE_VERSION=null
GITHUB_CORE_HASH=b22731c6
WEB_VERSION=v5.19-822-g9d8a3dfc
WEB_BRANCH=development-v6
WEB_HASH=9d8a3dfc
GITHUB_WEB_VERSION=null
GITHUB_WEB_HASH=9d8a3dfc
FTL_VERSION=vDev-c9cfd38
FTL_BRANCH=development-v6
FTL_HASH=c9cfd382
GITHUB_FTL_VERSION=null
GITHUB_FTL_HASH=f12d14f3
Debug token: https://tricorder.pi-hole.net/yCuerghH/
I don't know if related but WebGUI says FTL update available but 'pihole -up' doesn't find any updates:
Core vDev (development-v6, b22731c6)FTL vDev (development-v6, c9cfd382) · Update available! Web interface vDev (development-v6, 9d8a3dfc)
Still:
HoleMan@Pi-Monitor:~ $ pihole -up
[✓] Update local cache of available packages
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for dialog
[✓] Checking for ca-certificates
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL binary already installed, verifying integrity...
[i] Local binary up-to-date. No need to download!
[i] FTL: up to date
[i] Warning: You are using FTL from a custom branch (development-v6) and might be missing future releases.
[✓] Everything is up to date!
DL6ER
July 16, 2024, 9:00am
3
Yes, this currently affects all ARM builds as the configuration of fail01.dnssec.works changed causing some of our CI containers to fail to build the most recent binaries. So yes, the display is right: There is an update available but you cannot download it as the ARM binaries are not ready.
This will be fixed within
pi-hole:development-v6 ← pi-hole:tweak/api_network_info
opened 02:43PM - 14 Jul 24 UTC
# What does this implement/fix?
The existing implementation for `/api/network… /{gateway,interface}` relied on manually parsing various files in `/proc/` and `/sys/class/net`. This had several drawbacks, e.g., was it not possible to get IPv6 routes (and, hence, gateways) or lifetimes and priority of IPv6 addresses.
This PR instead implements [Netlink](https://en.wikipedia.org/wiki/Netlink) which is the proper way of querying the kernel in a standardized way about routes and interface details. It is also the same method used by the popular `ip` command (e.g. `ip a` and `ip r`):
> Netlink is designed and used for transferring miscellaneous networking information between the [kernel space](https://en.wikipedia.org/wiki/Kernel_space) and userspace processes. Networking utilities, such as the [iproute2](https://en.wikipedia.org/wiki/Iproute2) family and the utilities used for configuring [mac80211](https://en.wikipedia.org/wiki/Mac80211)-based wireless drivers, use Netlink to communicate with the [Linux kernel](https://en.wikipedia.org/wiki/Linux_kernel) from userspace. Netlink provides a standard [socket](https://en.wikipedia.org/wiki/Internet_socket)-based interface for userspace processes, and a kernel-side [API](https://en.wikipedia.org/wiki/Application_programming_interface) for internal use by [kernel modules](https://en.wikipedia.org/wiki/Kernel_module). Originally, Netlink used the `AF_NETLINK` socket family.
>
> Netlink is designed to be a more flexible successor to [ioctl](https://en.wikipedia.org/wiki/Ioctl); [RFC 3549](https://tools.ietf.org/html/rfc3549) describes the protocol in detail.
This change allows us to provide much better/more complete interface information through the API offering the base for implementing [this Discourse feature request](https://discourse.pi-hole.net/t/list-ip-v4-and-v6-address-in-web-interface/70981/).
Note: The `prefered` (one `r`) typo is a standard typo in Linux and expected.
---
**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.
2 Likes
DL6ER
July 16, 2024, 10:17am
4
Should be fixed now. I singled out the corresponding change into a dedicated PR to make ease reviewing for the team. It has already been merged!
pi-hole:development-v6 ← pi-hole:fix/ci_dnssec
opened 09:27AM - 16 Jul 24 UTC
# What does this implement/fix?
`fail*.dnssec.works` changed its configuratio… n from being `BOGUS` to `ABANDONNED` and cannot be used any longer for `BOGUS` testing
---
**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.
2 Likes
system
August 6, 2024, 10:17am
5
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.