v7.14.3 [stable] is released!

It is really stunning how many lines say “introduced in v7.14”. This was already the case in 7.13. Please don’t push “major” releases too early. Give your developers time to fix crucial bugs. Improve your internal QA process. So for example now we all know that VRF broke in 7.14. Add this knowledge to your testing process/setup and we will never ever run again in these same issues. Of course this needs automation and not just some additional manpower and 2 more entries in a hand-written checklist.

Regarding the urge to release:

http://forum.mikrotik.com/t/v7-14rc-testing-is-released/173569/178

We have reproduced multiple issues regarding VLAN MTU not applying correctly or resetting to default after reboot. Unfortunately, it is too late to incorporate the fixes into 7.14, so those will be available in the upcoming 7.15beta

It is never too late to incorporate fixes. I don’t know who “pushed” or “urged” you to release 7.14. Wasn’t the best idea it seems to me.

Very strange, my pihole works on hap ac3 with 7.14.1. Can you show your config?

Needs more work. When a peer without endpoint-address connects and then disconnects - RouterOS still floods the log with useless messages (probably because now the peer does have remote address under the hood - the address of the last message from peer)

now 7.13.5 pihole work not problem ( instruction install https://blog.unixhost.pro/ru/2022/10/ustanovka-docker-v-mikrotik-routeros/)
Screenshot 2024-03-11 134706.png

@hova888,
In any case, we need to check the log.

How to do it?

You need to enable logging in the container settings and then check the log messages to understand what the error is.

this is log 7.13.5 not problems

  • Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service s6rc-oneshot-runner: starting
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service s6rc-oneshot-runner successfully started
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service fix-attrs: starting
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service fix-attrs successfully started
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service legacy-cont-init: starting
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service legacy-cont-init successfully started
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service cron: starting
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service cron successfully started
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service _uid-gid-changer: starting
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service _uid-gid-changer successfully started
    Mar/11/2024 14:20:21 container,info,debug s6-rc: info: service _startup: starting
    Mar/11/2024 14:20:21 container,info,debug _Starting docker specific checks & setup for docker pihole/pihole
    Mar/11/2024 14:20:21 container,info,debug Setting capabilities on pihole-FTL where possible
    Mar/11/2024 14:20:21 container,info,debug Applying the following caps to pihole-FTL:
    Mar/11/2024 14:20:21 container,info,debug * CAP_CHOWN
    Mar/11/2024 14:20:21 container,info,debug * CAP_NET_BIND_SERVICE
    Mar/11/2024 14:20:21 container,info,debug * CAP_NET_RAW
    Mar/11/2024 14:20:21 container,info,debug * CAP_NET_ADMIN
    Mar/11/2024 14:20:21 container,info,debug * CAP_SYS_NICE
    Mar/11/2024 14:20:21 container,info,debug Ensuring basic configuration by re-running select functions from basic-install.sh
    Mar/11/2024 14:20:21 container,info,debug
    Mar/11/2024 14:20:21 container,info,debug Installing configs from /etc/.pihole…
    Mar/11/2024 14:20:21 container,info,debug Existing dnsmasq.conf found… it is not a Pi-hole file, leaving alone!
    Mar/11/2024 14:20:21 container,info,debug Installing /etc/dnsmasq.d/01-pihole.conf…
    [K [✓] Installed /etc/dnsmasq.d/01-pihole.conf
    Mar/11/2024 14:20:25 container,info,debug Installing /etc/.pihole/advanced/06-rfc6761.conf…
    [K [✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
    Mar/11/2024 14:20:27 container,info,debug
    Mar/11/2024 14:20:27 container,info,debug Installing latest logrotate script…
    Mar/11/2024 14:20:27 container,info,debug Existing logrotate file found. No changes made.
    Mar/11/2024 14:20:28 container,info,debug [i] Assigning password defined by Environment Variable
    Mar/11/2024 14:20:28 container,info,debug [✓] New password set
    Mar/11/2024 14:20:29 container,info,debug [i] Added ENV to php:
    Mar/11/2024 14:20:29 container,info,debug “TZ” => “Europe/Kyiv”,
    Mar/11/2024 14:20:29 container,info,debug “PIHOLE_DOCKER_TAG” => “”,
    Mar/11/2024 14:20:29 container,info,debug “PHP_ERROR_LOG” => “/var/log/lighttpd/error-pihole.log”,
    Mar/11/2024 14:20:29 container,info,debug “CORS_HOSTS” => “”,
    Mar/11/2024 14:20:29 container,info,debug “VIRTUAL_HOST” => “MikroTik”,
    Mar/11/2024 14:20:29 container,info,debug [i] Using IPv4 and IPv6
    Mar/11/2024 14:20:29 container,info,debug
    Mar/11/2024 14:20:30 container,info,debug [i] Installing latest Cron script…
    [K [✓] Installing latest Cron script
    Mar/11/2024 14:20:30 container,info,debug [i] Preexisting ad list /etc/pihole/adlists.list detected (exiting setup_blocklists early)
    Mar/11/2024 14:20:30 container,info,debug [i] Existing DNS servers detected in setupVars.conf. Leaving them alone
    Mar/11/2024 14:20:30 container,info,debug [i] Applying pihole-FTL.conf setting LOCAL_IPV4=0.0.0.0
    Mar/11/2024 14:20:30 container,info,debug [i] FTL binding to default interface: eth0
    Mar/11/2024 14:20:33 container,info,debug [i] Enabling Query Logging
    Mar/11/2024 14:20:35 container,info,debug [i] Testing lighttpd config: Syntax OK
    Mar/11/2024 14:20:35 container,info,debug [i] All config checks passed, cleared for startup …
    Mar/11/2024 14:20:35 container,info,debug [i] Docker start setup complete
    Mar/11/2024 14:20:35 container,info,debug
    Mar/11/2024 14:20:35 container,info,debug [i] pihole-FTL (no-daemon) will be started as root
    Mar/11/2024 14:20:35 container,info,debug
    Mar/11/2024 14:20:35 container,info,debug s6-rc: info: service _startup successfully started
    Mar/11/2024 14:20:35 container,info,debug s6-rc: info: service pihole-FTL: starting
    Mar/11/2024 14:20:35 container,info,debug s6-rc: info: service pihole-FTL successfully started
    Mar/11/2024 14:20:35 container,info,debug s6-rc: info: service lighttpd: starting
    Mar/11/2024 14:20:35 container,info,debug s6-rc: info: service lighttpd successfully started
    Mar/11/2024 14:20:35 container,info,debug s6-rc: info: service _postFTL: starting
    Mar/11/2024 14:20:35 container,info,debug s6-rc: info: service postFTL successfully started
    Mar/11/2024 14:20:35 container,info,debug s6-rc: info: service legacy-services: starting
    Mar/11/2024 14:20:35 container,info,debug Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
    Mar/11/2024 14:20:35 container,info,debug s6-rc: info: service legacy-services successfully started
    Mar/11/2024 14:20:38 container,info,debug [i] Neutrino emissions detected…
    Mar/11/2024 14:20:39 container,info,debug
    [K [✓] Pulling blocklist source list into range
    Mar/11/2024 14:20:39 container,info,debug
    Mar/11/2024 14:20:45 container,info,debug [i] Preparing new gravity database…
    [K [✓] Preparing new gravity database
    Mar/11/2024 14:20:58 container,info,debug [i] Creating new gravity databases…
    [K [✓] Creating new gravity databases
    Mar/11/2024 14:20:59 container,info,debug [i] Using libz compression
    Mar/11/2024 14:20:59 container,info,debug
    Mar/11/2024 14:20:59 container,info,debug [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
    Mar/11/2024 14:21:03 container,info,debug [i] Status: Pending…
    [K [✓] Status: Retrieval successful
    Mar/11/2024 14:21:25 container,info,debug
    [✓] Parsed 173658 exact domains and 0 ABP-style domains (ignored 1 non-domain entries)
    Mar/11/2024 14:21:25 container,info,debug Sample of non-domain entries:
    Mar/11/2024 14:21:25 container,info,debug - “0.0.0.0”
    Mar/11/2024 14:21:25 container,info,debug
    Mar/11/2024 14:21:25 container,info,debug [i] List stayed unchanged
    Mar/11/2024 14:21:25 container,info,debug
    Mar/11/2024 14:21:25 container,info,debug [i] Target: https://adguardteam.github.io/AdGuardSDNSFilter/Filters/filter.txt
    Mar/11/2024 14:21:27 container,info,debug [i] Status: Pending…
    [K [✓] Status: Retrieval successful
    Mar/11/2024 14:21:36 container,info,debug
    [✓] Parsed 2 exact domains and 62518 ABP-style domains (ignored 589 non-domain entries)
    Mar/11/2024 14:21:36 container,info,debug Sample of non-domain entries:
    Mar/11/2024 14:21:36 container,info,debug - “||ads.livetv*.me^”
    Mar/11/2024 14:21:36 container,info,debug - “||counter*.stat.ovh^”
    Mar/11/2024 14:21:36 container,info,debug - “||fxhpaoxqyajvmdg”
    Mar/11/2024 14:21:36 container,info,debug - “||rgfftupf”
    Mar/11/2024 14:21:36 container,info,debug - “||clk.rtpdn*.com^”
    Mar/11/2024 14:21:36 container,info,debug
    Mar/11/2024 14:21:37 container,info,debug [i] List has been updated
    Mar/11/2024 14:21:37 container,info,debug
    Mar/11/2024 14:21:43 container,info,debug [i] Building tree…
    [K [✓] Building tree
    Mar/11/2024 14:21:43 container,info,debug [i] Swapping databases…
    [K [✓] Swapping databases
    Mar/11/2024 14:21:43 container,info,debug [✓] The old database remains available
    Mar/11/2024 14:21:46 container,info,debug [i] Number of gravity domains: 236178 (236178 unique domains)
    Mar/11/2024 14:21:47 container,info,debug [i] Number of exact blacklisted domains: 0
    Mar/11/2024 14:21:47 container,info,debug [i] Number of regex blacklist filters: 0
    Mar/11/2024 14:21:47 container,info,debug [i] Number of exact whitelisted domains: 4
    Mar/11/2024 14:21:47 container,info,debug [i] Number of regex whitelist filters: 0
    Mar/11/2024 14:21:47 container,info,debug [i] Cleaning up stray matter…
    [K [✓] Cleaning up stray matter
    Mar/11/2024 14:21:47 container,info,debug
    Mar/11/2024 14:21:47 container,info,debug [✓] FTL is listening on port 53
    Mar/11/2024 14:21:47 container,info,debug [✓] UDP (IPv4)
    Mar/11/2024 14:21:47 container,info,debug [✓] TCP (IPv4)
    Mar/11/2024 14:21:47 container,info,debug [✓] UDP (IPv6)
    Mar/11/2024 14:21:47 container,info,debug [✓] TCP (IPv6)
    Mar/11/2024 14:21:47 container,info,debug
    Mar/11/2024 14:21:47 container,info,debug [✓] Pi-hole blocking is enabled
    Mar/11/2024 14:21:47 container,info,debug
    Mar/11/2024 14:21:54 container,info,debug Pi-hole version is v5.17.3 (Latest: v5.17.3)
    Mar/11/2024 14:21:54 container,info,debug web version is v5.21 (Latest: v5.21)
    Mar/11/2024 14:21:54 container,info,debug FTL version is v5.25.1 (Latest: v5.25.1)
    Mar/11/2024 14:21:54 container,info,debug Container tag is: 2024.02.2
    Mar/11/2024 14:21:54 container,info,debug

The upgrade is done by the installed version, not the new on.

If you upgrade from (say) 7.13 to 7.14, then the upgrade package is downloaded by the running 7.13, tested, extracted and installed by the running 7.13
Only after the boot the new 7.14 will be running.

So, when they say “improved system stability” you will only see the benefits after the first boot, when the new version starts running. In some cases maybe not even then, since they would need for the firmware to be upgraded too.

log container 7.14.1
Screenshot 2024-03-11 144046.png
Screenshot 2024-03-11 144006.png
Screenshot 2024-03-11 143922.png

What versions of the solution will you have for my problem pihole 7.14.1 log above in the screenshot?

I soldered a push button switch to my lab card now so atleast I’m a bit more ready.

Tunnel interfaces are still going to the main VRF instead of the configured VRF in 7.14.1.

#notfixed - it’s getting ridiculous..

Mr. Support, with the latest update 7.14.1 the logging problems with the handshake have NOT been solved, both in the wireguard road-warrior links and with BTH.

  1. I have connected with the RW, I navigate a little bit and when I disconnect, the messages in the log appear again, it does not stop after 20 attempts.
  2. I have activated the BTH with the app and the same thing, the messages start coming out as if there was no tomorrow. The funny thing is that they come out whether you are connected or not.

Any idea?

Must be something config specific, I do use wireguard for road-warrior setup and I have 0 such logs.
I don’t use or have BTH though.

Yes, i have the same issue, that my Wireguard Interface for my Road Warrior Clients go to the main VRF, instead of the dedicated VRF.

Mr. Support, with the latest update 7.14.1 the logging problems with the handshake have NOT been solved, both in the wireguard road-warrior links and with BTH.

https://i.postimg.cc/kg0MwDQq/image.png
  1. I have connected with the RW, I navigate a little bit and when I disconnect, the messages in the log appear again, it does not stop after 20 attempts.
  2. I have activated the BTH with the app and the same thing, the messages start coming out as if there was no tomorrow. The funny thing is that they come out whether you are connected or not.

Try to connect with road-warrior and when you disconnect you will see that the handshak messages start coming out, this started since the first versions of 7.13.

Nope, I don’t…
Just tested, deliberately.
That is why I am actually wondering, maybe some specific config setting is involved.