TOR does not work on AR750S

Hello colleagues, in the latest version of this router (3.216-stable), I find that I cannot use Tor.

The steps I have done have been:
1.- Connect through the web browser.
2.- Update the packages.
3.- Go to the VPN menu (where TOR is located).
4.- I activate the mode and set it to Random and on the top right Apply.
5.- I see how a message appears in orange showing the Bootstrap progress percentage.

In this last step is where I always get stuck, because either it remains stagnant in 85% or 65% depending…

I tried to do it by SSH configuring some documents that I have seen in a previous publication, but the session gets stuck at the moment when I go for the 85% and does not respond and does not give internet connection (logical the router does not respond) and I can not connect through the web browser.

The router gets the internet through the WAN interface over the wired network.

Can you give me a hand? Thanks in advance!

PD: The last time I tried (a few minutes ago) it stayed at 70% and then appeared on the screen: Error! Time Out.

Best regards.

Can you ssh into the background and enter the following command and output the log?
cat /var/lib/tor/control.log
Then enter free and take a screenshot. Thank you.

root@GL-AR750S:~# cat /var/lib/tor/control.log
-ash: can’t fork: Out of memory
root@GL-AR750S:~# cat /var/lib/tor/control.log
Sep 05 13:16:23.000 [notice] Tor 0.4.6.8 opening new log file.
Sep 07 18:34:14.000 [notice] {CONTROL} Bootstrapped 0% (starting): Starting
Sep 07 18:34:15.000 [notice] {CONTROL} Bootstrapped 5% (conn): Connecting to a relay
Sep 07 18:36:32.000 [notice] {CONTROL} Bootstrapped 10% (conn_done): Connected to a relay
Sep 07 18:36:32.000 [notice] {CONTROL} Bootstrapped 14% (handshake): Handshaking with a relay
Sep 07 18:36:32.000 [notice] {CONTROL} Bootstrapped 15% (handshake_done): Handshake with a relay done
Sep 07 18:36:32.000 [notice] {CONTROL} Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Sep 07 18:36:32.000 [notice] {CONTROL} Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Sep 07 18:36:32.000 [notice] {CONTROL} Bootstrapped 30% (loading_status): Loading networkstatus consensus
Sep 07 18:36:38.000 [notice] {CONTROL} Bootstrapped 40% (loading_keys): Loading authority key certs
Sep 07 18:36:42.000 [notice] {CONTROL} Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Sep 07 18:36:44.000 [notice] {CONTROL} Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Sep 07 18:37:08.000 [notice] {CONTROL} Bootstrapped 56% (loading_descriptors): Loading relay descriptors
Sep 07 18:37:12.000 [notice] {CONTROL} Bootstrapped 63% (loading_descriptors): Loading relay descriptors
Sep 07 18:37:17.000 [notice] {CONTROL} Bootstrapped 71% (loading_descriptors): Loading relay descriptors
Sep 07 18:37:23.000 [notice] {CONTROL} Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Sep 07 18:40:47.000 [notice] {CONTROL} Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
Sep 07 18:42:41.000 [notice] {CONTROL} Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
Sep 07 18:42:41.000 [notice] {CONTROL} Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Sep 07 18:42:41.000 [notice] {CONTROL} Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Sep 07 18:42:41.000 [notice] {CONTROL} Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Sep 07 18:42:42.000 [notice] {CONTROL} Bootstrapped 100% (done): Done

Good afternoon,

this is the result of this command you told me about.
Greetings.

Update:

What has just happened is exceptional, as I have been able to connect. It must be electro-goblins xD. Anyway, I think the time it took to “set up” is quite long.

Yes, it takes a long time to connect.

Hi,

I don’t know what happened again, I’m back to the starting point, I can’t connect and the log doesn’t give any more details. Only for the percentage that remains.

Greetings

Which exit nodes did you choose? Try closing the exit node