Been using easytether-usb on GL-AR300M without issues for a couple of years. After updating to 3.105 FW, easytether-usb installs fine, but errors when running it: Error loading shared library libcrypto.so.1.0.0: No such file or directory (needed by /usr/bin/easytether-usb)
root@GL-AR300M:/temp# opkg install ./easytether-usb-openssl_0.8.9-4_mips_24kc.ip
Was able to get easytether-usb working on 3.105 FW by downgrading to libopenssl_1.0.2u-1_mips_24kc.ipk with this command:opkg install /tmp/libopenssl_1.0.2u-1_mips_24kc.ipk --force-downgrade
Not sure what dependencies will break by downgrading from libssl.so.1.1 to libssl.so.1.0.0
2 Likes
Another try is using the tiny version of easytether. But someone said it does not work stable and I do not have more details.
I just encountered the same error on my AR750s with firmware 3.105. Thanks for posting this solution! I was concerned about downgrading too, but good to know this works.
I instead reverted back to 3.104 and EasyTether is installed and working ok again, but will probably try again with the next firmware release.
I also encountered same problem on my GL-MT300N-V2 (V3.105). Without this library SSMTP package dont work.
But method by downgrading to libopenssl_1.0.2u-1_mipsel_24kc.ipk dont work correct. This causes Web UI to break.
Is it possible to solve in future firmware compatibility problem of some network packages with the library libcrypto.so.1.0.0 only?
On the other hand, if I manually install the latest version ssmtp package from locale:
opkg install /tmp/ssmtp_2.64-7_mipsel_24kc.ipk
Installing ssmtp (2.64-7) to root…
Collected errors:
- satisfy_dependencies_for: Cannot satisfy the following dependencies for ssmtp:
- libopenssl1.1
Just hold and we are pushing 3.201 firmware.
Hi, I had the same issue with the Creta, and now just received my Beryl, (fw v 3.200). Will there be an update for the MT1300 as well? I’d like to use easytether on the new router too.
Thanks!
Yes, all models will upgrade to 3.201.
Still too early to upgrade because the repo is not ready.
1 Like
Current Workaround for 3.105:
Install the TINY client from OpenWRT v19.0.3+ -tiny
SSH to device and issue commands:
openssl genpkey -algorithm rsa -pkeyopt rsa_keygen_bits:2048 -out /etc/easytether/adbkey
chown root:root /etc/easytether/adbkey
chmod 0600 /etc/easytether/adbkey
Also, documentation issue
cat << EOF >> /etc/config/easytether while true do if (ip a s tap-easytether up); then else easytether-usb fi sleep 1 done EOF
Should be:
cat << EOF >> /etc/config/easytether
while true
do
if (ip a s tap-easytether up);
then
echo > null
else
easytether-usb
fi
sleep 1
done
EOF
1 Like
The old version of libopenssl required by stunnel is here:
https://fw.gl-inet.com/releases/packages-3.x/ar71xx/base/libopenssl_1.0.2o-1_mips_24kc.ipk
These old libraries may be installed in /usr/lib alongside the new one.
(do not remove or overwrite the new ones!)
In an empty directory:
$ wget https://fw.gl-inet.com/releases/packages-3.x/ar71xx/base/libopenssl_1.0.2o-1_mips_24kc.ipk
$ tar xzf libopenssl_1.0.2o-1_mips_24kc.ipk
$ tar xzf data.tar.gz
$ cd usr/lib
$ cp libcrypto.so.1.0.0 libssl.so.1.0.0 /usr/lib
stunnel should now find its required libraries
Time to upgrade to 3.201 which solves this issue.
When will 3.201 be released! I do not have time to deal with weekly updates of the beta versions, as I use my devices in production. I am running 3.104 as I have the same issue with 3.105 breaking the shared libcryptio library, and have been living for months with the well known dnsmasq security bugs (7 CVEs). Many of us need a secure, fully functional, released version of your router firmware.
1 Like
so what is the best current solution to this issue?
3.201 has been released and you can install easytether without probelm.
I’m still getting the same errors as the original post. I can’t get the drivers to install for the life of me. I’m on 3.201.
Yes, it was upgraded properly. I checked to make sure. I had to downgrade two versions to get it to work, which it did flawlessly once downgraded. 3.201 just won’t install the drivers properly, same as 3.105.
As I posted the screenshot, you can post the same o verify.
As I said you may clear your settings. It may be due to reserved settings.
I did that - full factory reset. Still no go.
I mean can you post screenshot as I do?
Need to see firmware version and opkg output.