Thanks Peci1. The vpn package was listed in the conf file, I deleted the entry, and now the router upgraded to 7.0.
to my surprise all went smooth - just a manual update needed - maybe turris team should force an automatic reboot on major versions upgrade
Hi,
unfortunately I made a clean USB recovery - but having issues to access the package installation.
Blockquote
Downloading https://repo.turris.cz/hbl/omnia/packages/core/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_core
Downloading https://repo.turris.cz/hbl/omnia/packages/core/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading https://repo.turris.cz/hbl/omnia/packages/base/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_base
Downloading https://repo.turris.cz/hbl/omnia/packages/base/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading https://repo.turris.cz/hbl/omnia/packages/cesnet/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_cesnet
Downloading https://repo.turris.cz/hbl/omnia/packages/cesnet/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading https://repo.turris.cz/hbl/omnia/packages/luci/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_luci
Downloading https://repo.turris.cz/hbl/omnia/packages/luci/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading https://repo.turris.cz/hbl/omnia/packages/node/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_node
Downloading https://repo.turris.cz/hbl/omnia/packages/node/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading https://repo.turris.cz/hbl/omnia/packages/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_packages
Downloading https://repo.turris.cz/hbl/omnia/packages/packages/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading https://repo.turris.cz/hbl/omnia/packages/routing/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_routing
Downloading https://repo.turris.cz/hbl/omnia/packages/routing/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading https://repo.turris.cz/hbl/omnia/packages/telephony/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_telephony
Downloading https://repo.turris.cz/hbl/omnia/packages/telephony/Packages.sig
Signature check failed.
Remove wrong Signature file.
Downloading https://repo.turris.cz/hbl/omnia/packages/turrispackages/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_turrispackages
Downloading https://repo.turris.cz/hbl/omnia/packages/turrispackages/Packages.sig
Signature check failed.
Remove wrong Signature file.
Blockquote
So where can I get the package for my AsiaRF AW7916-NPD?
Modellļ¼Turris Omnia
Architekturļ¼ARMv7 Processor rev 1 (v7l)
Firmware-Versionļ¼TurrisOS 7.0.0
Thanks
my omnia updated last night to 7.0. at first everything seemed to work fine but the i noticed some urls no longer resolving and that the foris/luci web-ui are unreachable. luckily ssh still worked so i rolled back to 6.5.2 for now.
this is the first botched upgrade path sice the tos 3.x desasterā¦ is this a known problem?
Itās software. Vulnerabilities can be found any time you do a thorough review of the code. In your original post you stated that the version of xz that Turris ships was unsafe. Without citing any sources this is just scaremongering.
Could you give an example, please? And do you have adblock installed?
I finally got an email about update. It was at 13:21. Interesting is last line in email:
Aktualizace bude automaticky nainstalovĆ”na nÄkdy po 2024-04-21T13:22:06.104076, pakliže se neobjevĆ novÄjÅ”Ć.
So update will be applied immediatelly, three days delay is ignored.
EDIT: in updater tab it is correct. So maybe only wrong date in email.
These updates are not going to be automatically installed before 23. dubna 2024 13:21.
Dunno if itās the good way to resolve it but
by vi /etc/opkg.conf
##option check_signature
Seems updating
THX for the advice - but there can be no real solution to comment out signature checking. The interesting thing is, that I have this issue with a clean installation and this normally is a good way of avoiding exactly those issues. What I am reading so far, are issues regarding update failures and package renaming. It might be not the best idea to initiate this changes without proper announcement, or did I miss documentation?
Unfortunately my AsiaRF AW7916-NPD is not recognised in Slot 1 or 2ā¦
Seems the upgrade happened and broke vpn-policy-routing
root@turris:~# opkg install pbr
Installing pbr (1.1.1-7) to root...
Collected errors:
* check_conflicts_for: The following packages conflict with pbr:
* check_conflicts_for: vpn-policy-routing *
* opkg_install_cmd: Cannot install package pbr.
root@turris:~# opkg --force-remove remove vpn-policy-routing
No packages removed.
Also when i try to install luci-app-pbr it refuses to install firewall4 since it overwrites some files belonging to firewall. Maybe itās safe to ignore but iām hesitant forcing stuff with such a crucial packageā¦
āThe interesting thing is, that I have this issue with a clean installation and this normally is a good way of avoiding exactly those issuesā
Same boat. And when installing vpn all connexions falling
Regarding MT7916 - Did revert to 6.5.2 and found a solution - dependencies does not seem to be correct. Installing kmod-mt76-sdio apart from kmod-mt7916-firmware did the trick for me.
MediaTek MT7615/MT79xx SDIO driver common code
My Omnia is still crashing/rebooting multiple times per day, and a rollback to 6.x fixes the issueā¦
so there is some weirdness going on here stillā¦
I updated today my infrastructure.
- My dump AP have firewall/dnsmasq/odhcp disabled. Error/warning messages in log for all installations:
2024-04-21 19:40:19: (../src/mod_openssl.c.3137) SSL:openssl library version is outdated and has reached end-of-life. As of 11 Sep 2023, only openssl 3.0.0 and later continue to receive security patches from openssl.org <several times>
ERROR:Failed operations:
resolver-debug/postinst: Remove buttons in LuCI's Custom Commands
Add debug buttons in LuCI's Custom Commands
Error connecting control socket, socket='/var/syslog-ng.ctl', error='Connection refused'
-
main router [Omnia 1GB/WIFI6-card AW7915-NP1] with normal functionality (TOR client, ddns client, dnssec via 1.1.1.1): update worked without problems. Had to remove
kmod-jool
andjool-tools
. -
dump AP [MOX AB(AW7915-NP1)D(2,5GBE))]:
- update via
pkgupdate
failed. AP was not reachable any more. Had those issues again and again in the past which means this might not at all has something to do with this update. - Fresh installation via preparing the SD-card with latest medkit (MOX MicroSD - Turris Documentation): Fails - reforis setup does not start, instead it prompts me for the reforis password (which I do not have as I havenāt set up the MOX yet). I had that in the past and what helped was to retry the procedure. But this time it didnāt help.
- ā had to rollback to my 6.5.2 exported snapshot.
- update via
-
dump AP [Omnia 1GB/WIFI6-cards 1xAW7915-NP1 + 2xAW7916-NPD]: update worked without problems
Does someone use DynDNS? I installed isc-dhcp-dyndns-ipv4 but it does not show in LUCI > System > Systemstart or in the menu - what am I missing?
@miska There is something wrong with the MOX medkit (https://repo.turris.cz/hbs/medkit/mox-medkit-202404020445.tar.gz or https://repo.turris.cz/hbs/medkit/mox-medkit-latest.tar.gz), the initial setup process is not launched when primarily accessing 192.168.1.1, thus a MOX cannot be setup from scratch with 7.0 medkit - could you please have a look into that?
The question is a bit off-topic for this thread, but:
Are you looking for ārealā Dynamic DNS as described in RFC2136, or DDNS as offered by some DNS providers (e.g. like those mentioned on the OpenWrt DDNS client page).
The isc-dhcp-dyndns-ipv4
package youāre referring to just installs other packages required for RFC2136 style dynamic DNS. And there is no LuCI component.
In case youāre looking for DDNS, luci-app-ddns
is probably what you want.
The forum search finds lots of other DDNS related topics.
THX!!!
Somehow I did not see the other packages yesterday - searched for DDNS apart from DynDNS and it didnĀ“t pop upā¦
but need to sort out some errors
Configuring luci-i18n-ddns-cs.
092248 WARN : Service section disabled! - TERMINATE
092248 WARN : Service section disabled! - TERMINATE
Interesting, over here there is ( after 7.0) something not running on the BCP38 side, both on Omnia and MOX.
It is activated, but canāt see it in the processes. did a off >on, still a no go.
yes the luci adblock plugin is installed. however since luci was inaccessible after the upgrade to 7.0 i couldnāt check itā¦ the only url i wrote down was go.redirectingat.com which is (i suspect) a tracking proxy. what i noticed is that many links while browsing/googling stopped resolvingā¦