I'm having a strange problem with my GL.iNet Mudi E750. Tor has worked perfectly for a long time, had this problem once before, and a factory reset fixed it. Unfortunately, this time even resetting the router doesn't help. but today I woke up and it suddenly stopped working. Tor always gets stuck at 30% bootstraping.
What I've already tried:
Changed the SIM card.
Downgraded from firmware 4.3.26 to 4.3.19.
Installed the latest beta firmware just to test, then went back to 4.3.26 stable.
Connected via SSH and changed /etc/sysctl.conf from 6 MB to 8 MB (this helped on older firmware), but it made no difference.
Checked the Tor logs. They simply stop at 30% bootstrap with no further updates, even if I leave the router running for over an hour.
Has anyone experienced this before or knows how to fix it? Is there another firmware version or another solution I should try?
We checked the issue and found that the Tor service may fail to start as the system runs out of memory. When Tor is loading relay information, it can consume additional memory, and the system may terminate the Tor process due to insufficient RAM.
If you need to use the Tor feature, you can try using an SD card as swap memory to provide additional memory space. Please refer to the following discussion for the detailed setup steps.
Please note that swap requires frequent read/write operations, it may increase the wear of the SD card and potentially shorten its lifespan.
I don't think this is actually a memory issue, because on my Mudi E750 V2, Tor connects and works normally when I install the Beta 4.8.5 firmware. If the router really didn't have enough memory, I would expect the same problem to occur on the beta version as well.
I would really like to use the stable firmware because it has many more plugins available, and that's the version I want to stay on.
Could you please help me find a solution that allows Tor to work on the current stable firmware? If you need any logs or if there's anything you'd like me to test, I'd be happy to help.