We just released bugfix release 3.10.1. Nothing big, mostly just few fixes. We are still aware of some issues with odhcp6c an ucollect that we are trying to address but we decided not to delay the fixes we ready have.
Side-note regarding IPv6 workaround, we know those are not the best way how to get IPv6 - the best option would be for all ISP to stop beating a dead horse and embrace the future, but unfortunately, plenty of our users still have to deal with ISPs stuck in the past and thus depend on those.
Full release notes are as follows:
foris: support 6in4 and 6to4
foris: ability to set protocol in VPN
kernel: update and UAS driver
foris-pakon: bug and compatibility fixes
odhcp6c: fix after update
netmetr: fix synchronization code
As always, if you encounter any new issue, let us know.
Something hangs in postinstall. Last line displayed:
/usr/lib/opkg/info//luci-i18n-samba-de.postinst: .: line 4: canāt open ā/etc/uci-defaults/luci-i18n-samba-deā
After a reboot, additional problems:
Detected existing journal. Trying to recover it.
line not found
line not found
line not found
line not found
DIE:
[string ābackendā]:1172: [string ābackendā]:1163: Failed to lock the lock file //var/lock/opkg.lock: Resource temporarily unavailable
You have running updater in the background and when you run it manually you end up with running another instance of the updater, which failed. I suggest you wait.
IĀ“ve just sent the diagnostics to tech.support. Nothing changes if I connect/disconnect from ssh. I didnāt run updater from command line. It is an automatic installation
Should I do something special for the UAS driver to be used? I have a USB 3.0 NAS box connected, by specification it should support UASP, but in lsusb -t I still see Driver=usb-storage.
Iām on 3.10.1, tried rebooting the router several times.
If it helps, the NAS box is set up to be used as /srv through the Storage Foris plugin.
However, probably because I also use the NAS for storing logs, /var/log/messages does not contain information about the USB drive connection, since it happens before syslog-ng can be fully started.