Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Want to share your OpenWrt / Gargoyle knowledge? Implemented a new feature? Let us know here.

Moderator: Moderators

Post Reply
fiye68
Posts: 7
Joined: Wed Feb 02, 2022 12:13 pm

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-04-08

Post by fiye68 »

Many thanks for the effort to compile this image!

I have just tried it but there is the following error

Code: Select all

Preparing to install package gargoyle-tor...
sh: can't open '/etc/uci-defaults/tor.ucidefaults': No such file or directory
Warning: postinstall script failed for package gargoyle-tor.
        Successfully installed gargoyle-tor.
After that, I enabled Tor via the web interface, initially as toggled for each host and it throws errors, bootstraps to 50% and then kernel panic

Code: Select all

Fri May 22 10:59:44 2026 daemon.err uhttpd[2408]: /etc/tor.firewall: line 164: can't create : nonexistent directory
Fri May 22 10:59:44 2026 daemon.err uhttpd[2408]: md5sum: can't open '': No such file or directory
Fri May 22 10:59:44 2026 daemon.err uhttpd[2408]: mv: can't rename '': No such file or directory
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: We compiled with OpenSSL 30000130: OpenSSL 3.0.19 27 Jan 2026 and we are running with OpenSSL 30000130: 3.0.19. These two versions should be binary compatible.
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: Tor 0.4.8.12 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.19, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: Read configuration file "/etc/tor/torrc".
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: You configured a non-loopback address '192.168.1.1:9053' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: You configured a non-loopback address '192.168.1.1:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri May 22 10:59:50 2026 daemon.warn Tor[6631]: ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: You configured a non-loopback address '192.168.1.1:9053' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: You configured a non-loopback address '192.168.1.1:9040' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: Opening DNS listener on 192.168.1.1:9053
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: Opened DNS listener connection (ready) on 192.168.1.1:9053
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: Opening Transparent pf/netfilter listener on 192.168.1.1:9040
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: Opened Transparent pf/netfilter listener connection (ready) on 192.168.1.1:9040
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: Opening Control listener on 127.0.0.1:9051
Fri May 22 10:59:50 2026 daemon.notice Tor[6631]: Opened Control listener connection (ready) on 127.0.0.1:9051
Fri May 22 10:59:50 2026 daemon.warn Tor[6631]: Fixing permissions on directory /var/tor/keys
Fri May 22 10:59:50 2026 daemon.err uhttpd[2408]: /etc/tor.firewall: line 164: can't create : nonexistent directory
Fri May 22 10:59:51 2026 daemon.err uhttpd[2408]: md5sum: can't open '': No such file or directory
Fri May 22 10:59:51 2026 daemon.err uhttpd[2408]: mv: can't rename '': No such file or directory
Fri May 22 10:59:53 2026 daemon.err uhttpd[2408]: uci: Entry not found
Fri May 22 10:59:54 2026 daemon.info dnsmasq[3177]: exiting on receipt of SIGTERM
Fri May 22 10:59:56 2026 daemon.err uhttpd[2408]: udhcpc: started, v1.36.1
Fri May 22 10:59:56 2026 daemon.err uhttpd[2408]: udhcpc: broadcasting discover
Fri May 22 10:59:56 2026 daemon.notice Tor[6631]: Bootstrapped 0% (starting): Starting
Fri May 22 10:59:56 2026 daemon.notice Tor[6631]: Starting with guard context "default"
Fri May 22 10:59:58 2026 daemon.notice Tor[6631]: Bootstrapped 5% (conn): Connecting to a relay
Fri May 22 10:59:58 2026 daemon.notice Tor[6631]: Bootstrapped 10% (conn_done): Connected to a relay
Fri May 22 10:59:58 2026 daemon.notice Tor[6631]: Bootstrapped 14% (handshake): Handshaking with a relay
Fri May 22 10:59:59 2026 daemon.err uhttpd[2408]: udhcpc: no lease, failing
Fri May 22 10:59:59 2026 daemon.notice Tor[6631]: Bootstrapped 15% (handshake_done): Handshake with a relay done
Fri May 22 10:59:59 2026 daemon.notice Tor[6631]: Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Fri May 22 10:59:59 2026 daemon.notice Tor[6631]: Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Fri May 22 10:59:59 2026 daemon.notice Tor[6631]: Bootstrapped 30% (loading_status): Loading networkstatus consensus
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: started, version 2.90 cachesize 1000
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: DNS service limited to local subnets
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: UBus support enabled: connected to system bus
Fri May 22 10:59:59 2026 daemon.info dnsmasq-dhcp[6916]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using nameserver 192.168.1.1#9053 for domain onion
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for test
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for onion
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for localhost
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for local
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for invalid
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for bind
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for lan
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: reading /tmp/resolv.conf.d/resolv.conf.auto
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using nameserver 192.168.1.1#9053 for domain onion
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using nameserver 8.8.8.8#53
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using nameserver 8.8.8.8#53
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for test
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for onion
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for localhost
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for local
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for invalid
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for bind
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: using only locally-known addresses for lan
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: read /etc/hosts - 14 names
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Fri May 22 10:59:59 2026 daemon.info dnsmasq[6916]: read /tmp/hosts/odhcpd - 2 names
Fri May 22 10:59:59 2026 daemon.info dnsmasq-dhcp[6916]: read /etc/ethers - 0 addresses
Fri May 22 11:00:00 2026 daemon.err uhttpd[2408]: Error: Could not process rule: No such file or directory
Fri May 22 11:00:00 2026 daemon.err uhttpd[2408]: delete set inet fw4 tor_active_ips4
Fri May 22 11:00:00 2026 daemon.err uhttpd[2408]:                     ^^^^^^^^^^^^^^^
Fri May 22 11:00:01 2026 daemon.err uhttpd[2408]: /etc/tor.firewall: line 151: can't create : nonexistent directory
Fri May 22 11:00:01 2026 daemon.err uhttpd[2408]: /etc/tor.firewall: line 152: can't create : nonexistent directory
Fri May 22 11:00:01 2026 daemon.err uhttpd[2408]: md5sum: can't open '': No such file or directory
Fri May 22 11:00:01 2026 daemon.err uhttpd[2408]: mv: can't rename '': No such file or directory
Fri May 22 11:00:03 2026 daemon.err uhttpd[2408]: Error: syntax error, unexpected '}'
Fri May 22 11:00:03 2026 daemon.err uhttpd[2408]: add rule inet bwmon mangle_tor_down_bw tcp dport { } ct mark set ct mark & 0x0FFFFFFF | 0xF0000000
Fri May 22 11:00:03 2026 daemon.err uhttpd[2408]:                                                    ^
Fri May 22 11:00:03 2026 daemon.err uhttpd[2408]: Error: No such file or directory; did you mean set 'tor_relays4' in table inet 'fw4'?
Fri May 22 11:00:03 2026 daemon.err uhttpd[2408]: add rule inet bwmon mangle_tor_down_bw ip saddr @tor_relays ct mark set ct mark & 0x0FFFFFFF | 0xF0000000
Fri May 22 11:00:03 2026 daemon.err uhttpd[2408]:                                                 ^^^^^^^^^^^
Fri May 22 11:00:03 2026 daemon.err uhttpd[2408]: Error: No such file or directory; did you mean set 'tor_relays4' in table inet 'fw4'?
Fri May 22 11:00:03 2026 daemon.err uhttpd[2408]: add rule inet bwmon mangle_tor_up_bw ip daddr @tor_relays ct mark set ct mark & 0x0FFFFFFF | 0xF0000000
Fri May 22 11:00:03 2026 daemon.err uhttpd[2408]:                                               ^^^^^^^^^^^
Fri May 22 11:00:10 2026 daemon.notice Tor[6631]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Fri May 22 11:00:10 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:10 2026 daemon.notice Tor[6631]: Bootstrapped 40% (loading_keys): Loading authority key certs
Fri May 22 11:00:18 2026 daemon.notice Tor[6631]: The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Fri May 22 11:00:18 2026 daemon.notice Tor[6631]: Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Fri May 22 11:00:18 2026 daemon.notice Tor[6631]: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/9773, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Fri May 22 11:00:19 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:20 2026 daemon.notice Tor[6631]: Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Fri May 22 11:00:20 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:22 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:24 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:27 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:28 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:30 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:31 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:32 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:34 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:35 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:36 2026 daemon.notice Tor[6631]: The current consensus contains exit nodes. Tor can build exit and internal paths.
Fri May 22 11:00:38 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:40 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:41 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:46 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:00:50 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:01:03 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:01:10 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:01:12 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:01:13 2026 daemon.notice Tor[6631]: New control connection opened from 127.0.0.1.
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.207031] netifd invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.217712] CPU: 0 PID: 1785 Comm: netifd Tainted: G           O       6.6.127 #0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.225210] Stack : 80583288 00000000 ffffffff 800af47c 00000000 00000000 00000000 00000000
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.233597]         00000000 00000000 00000000 00000000 00000000 00000001 82d11b90 c5a5478e
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.241980]         82d11c28 00000000 00000000 82d11ad0 00000038 80534b84 00000000 00000003
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.250360]         2020204f 00000042 000016dc 20202020 8054bf84 8054bf84 81b5f700 8060bd1c
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.258751]         7fffffff 8060bb60 ffffffff 80000000 00000000 802e7df0 00000000 807c0000
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.267133]         ...
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.269584] Call Trace:
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.269593] [<800af47c>] 0x800af47c
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.275780] [<80534b84>] 0x80534b84
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.279353] [<802e7df0>] 0x802e7df0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.283009] [<80066144>] 0x80066144
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.286496] [<8006614c>] 0x8006614c
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.289984] [<80515e24>] 0x80515e24
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.293641] [<801360e8>] 0x801360e8
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.297464] [<80136510>] 0x80136510
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.300956] [<80171624>] 0x80171624
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.304446] [<80171624>] 0x80171624
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.308021] [<80136a7c>] 0x80136a7c
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.311515] [<801726a4>] 0x801726a4
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.315343] [<80133988>] 0x80133988
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.319410] [<80133c94>] 0x80133c94
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.323566] [<8015ab64>] 0x8015ab64
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.327139] [<8015e898>] 0x8015e898
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.331218] [<8006df8c>] 0x8006df8c
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.334707] [<801cd080>] 0x801cd080
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.338284] [<800719bc>] 0x800719bc
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.341958]
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.344024] Mem-Info:
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.346394] active_anon:14138 inactive_anon:4211 isolated_anon:0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.346394]  active_file:0 inactive_file:769 isolated_file:0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.346394]  unevictable:0 dirty:0 writeback:0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.346394]  slab_reclaimable:364 slab_unreclaimable:2702
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.346394]  mapped:42 shmem:4825 pagetables:116
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.346394]  sec_pagetables:0 bounce:0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.346394]  kernel_misc_reclaimable:0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.346394]  free:5844 free_pcp:24 free_cma:0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.384429] Node 0 active_anon:56552kB inactive_anon:16844kB active_file:0kB inactive_file:3076kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:168kB dirty:0kB writeback:0kB shmem:19300kB writeback_tmp:0kB kernel_stack:424kB pagetables:464kB sec_pagetables:0kB all_unreclaimable? no
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.410854] Normal free:23376kB boost:0kB min:16384kB low:20480kB high:24576kB reserved_highatomic:0KB active_anon:56552kB inactive_anon:16844kB active_file:0kB inactive_file:3076kB unevictable:0kB writepending:0kB present:131072kB managed:123304kB mlocked:0kB bounce:0kB free_pcp:88kB local_pcp:88kB free_cma:0kB
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.438767] lowmem_reserve[]: 0 0
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.442113] Normal: 494*4kB (UME) 163*8kB (UME) 46*16kB (UME) 47*32kB (UME) 23*64kB (UME) 12*128kB (UM) 4*256kB (UE) 3*512kB (UME) 2*1024kB (UE) 1*2048kB (M) 2*4096kB (UE) 0*8192kB = 23376kB
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.459254] 5594 total pagecache pages
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.463020] 0 pages in swap cache
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.466483] Free swap  = 0kB
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.469370] Total swap = 0kB
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.472243] 32768 pages RAM
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.475056] 0 pages HighMem/MovableOnly
Fri May 22 11:01:30 2026 kern.warn kernel: [  630.478920] 1942 pages reserved
Fri May 22 11:01:30 2026 kern.info kernel: [  630.482054] Tasks state (memory values in pages):
Fri May 22 11:01:30 2026 kern.info kernel: [  630.486811] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
Fri May 22 11:01:30 2026 kern.info kernel: [  630.495427] [    575]    81   575      382       25    20480        0             0 ubusd
Fri May 22 11:01:30 2026 kern.info kernel: [  630.503642] [    587]     0   587      271       12    20480        0             0 askfirst
Fri May 22 11:01:30 2026 kern.info kernel: [  630.512100] [    670]     0   670      309       14    20480        0             0 urngd
Fri May 22 11:01:30 2026 kern.info kernel: [  630.520441] [   1151]   514  1151      587       51    16384        0             0 logd
Fri May 22 11:01:30 2026 kern.info kernel: [  630.528737] [   1422]     0  1422      325       13    16384        0             0 dropbear
Fri May 22 11:01:30 2026 kern.info kernel: [  630.537226] [   1720]     0  1720     1334      126    20480        0             0 hostapd
Fri May 22 11:01:30 2026 kern.info kernel: [  630.545739] [   1721]     0  1721     1295      101    20480        0             0 wpa_supplicant
Fri May 22 11:01:30 2026 kern.info kernel: [  630.554739] [   1785]     0  1785      684       66    20480        0             0 netifd
Fri May 22 11:01:30 2026 kern.info kernel: [  630.563031] [   1966]     0  1966      479       30    16384        0             0 odhcpd
Fri May 22 11:01:30 2026 kern.info kernel: [  630.571448] [   2071]     0  2071      348       16    16384        0             0 ntpd
Fri May 22 11:01:30 2026 kern.info kernel: [  630.579616] [   2209]     0  2209      347       11    16384        0             0 udhcpc
Fri May 22 11:01:30 2026 kern.info kernel: [  630.587899] [   2408]     0  2408      698       52    16384        0             0 uhttpd
Fri May 22 11:01:30 2026 kern.info kernel: [  630.596224] [   2516]     0  2516      506       33    20480        0             0 usteerd
Fri May 22 11:01:30 2026 kern.info kernel: [  630.604965] [   6231]     0  6231      330       15    20480        0             0 dropbear
Fri May 22 11:01:30 2026 kern.info kernel: [  630.613607] [   6240]     0  6240      347       13    20480        0             0 ash
Fri May 22 11:01:30 2026 kern.info kernel: [  630.621826] [   6407]     0  6407      330       15    20480        0             0 dropbear
Fri May 22 11:01:30 2026 kern.info kernel: [  630.630332] [   6408]     0  6408      348       14    16384        0             0 ash
Fri May 22 11:01:30 2026 kern.info kernel: [  630.638361] [   6631]    52  6631    15121    12847    77824        0             0 tor
Fri May 22 11:01:30 2026 kern.info kernel: [  630.646557] [   6916]   453  6916      439       53    16384        0             0 dnsmasq
Fri May 22 11:01:30 2026 kern.info kernel: [  630.654946] [   7324]     0  7324      348       13    20480        0             0 crond
Fri May 22 11:01:30 2026 kern.info kernel: [  630.663156] [   7584]     0  7584      347       13    16384        0             0 run_haserl
Fri May 22 11:01:30 2026 kern.info kernel: [  630.671905] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),task=tor,pid=6631,uid=52
Fri May 22 11:01:30 2026 kern.err kernel: [  630.680102] Out of memory: Killed process 6631 (tor) total-vm:60484kB, anon-rss:51380kB, file-rss:4kB, shmem-rss:4kB, UID:52 pgtables:76kB oom_score_adj:0
The router reboot on its own and then I tried enabled for all hosts and the same behavior as above.

Before rebooting cpu was used up

Code: Select all

root@Gargoyle:~# top
Mem: 70632K used, 52672K free, 15656K shrd, 0K buff, 37580K cached
CPU:  75% usr  25% sys   0% nic   0% idle   0% io   0% irq   0% sirq
Load average: 3.54 2.57 1.21 4/55 8172
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 8095  8059 root     R     3336   3%  58% nft -a list table inet fw4
 4826  4774 root     S     1704   1%   8% {update_tor_nfts} /bin/sh /usr/sbin/up
 1780     1 root     S     5352   4%   0% /usr/sbin/hostapd -s -g /var/run/hosta
 1781     1 root     S     5180   4%   0% /usr/sbin/wpa_supplicant -n -s -g /var
 2486     1 root     S     2792   2%   0% /usr/sbin/uhttpd -f -h /www -r Gargoyl
 1845     1 root     S     2736   2%   0% /sbin/netifd
 8172  4826 root     R     2672   2%   0% nft add element inet fw4 tor_relays6 {
    1     0 root     S     2376   2%   0% /sbin/procd
 1155     1 logd     S     2348   2%   0% /sbin/logd -S 128
 2569     1 root     S     2020   2%   0% /sbin/usteerd
 2026     1 root     S     1916   2%   0% /usr/sbin/odhcpd
 2678     1 dnsmasq  S     1756   1%   0% /usr/sbin/dnsmasq -C /var/etc/dnsmasq.
 4774     1 root     S     1692   1%   0% {050-tor.bwmon} /bin/sh /usr/lib/bwmon
 7788  6633 root     S     1684   1%   0% {hotplug-call} /bin/sh /sbin/hotplug-c
 8059  7788 root     S     1656   1%   0% restore_quotas -w eth1 -d 0x8000 -m 0x
  579     1 ubus     S     1528   1%   0% /sbin/ubusd
 6633  1845 root     S     1476   1%   0% {hotplug-call} /bin/sh /sbin/hotplug-c
 8169  8141 root     R     1400   1%   0% top
 8141  8062 root     S     1392   1%   0% -ash
 2148     1 root     S<    1392   1%   0% /usr/sbin/ntpd -n -N -l -S /usr/sbin/n
I then tried the gargoyle-large image with usb stick as Tor Data Drive to free up ram but still it only bootstraps to 50% and cpu usage 100%.

To see if it is even possible any more to run tor on this router, I finally tried openwrt 24 with https://openwrt.org/docs/guide-user/services/tor/client and while tor works, there is constant cpu usage and little memory left so the router is unstable. It seems that tor or openssl3 have increased system requirements, maybe they need cpu hardware cryptograpic functions enabled so a newer router with a faster cpu and more than 128MB ram is needed.

If you have tested gargoyle tor on specific router models, please mention so that I can look into them.

Thanks again for all your continuous support.
Top
Lantis
Moderator
Posts: 7323
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia
Contact:
Contact Lantis

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-04-08

Post by Lantis »

I’ll need some time to look into this.
There’s a number of errors in your log which don’t look great (firewall rules failing), and then there’s the OOM issue which has always been a problem for Tor but maybe it is worse now.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
https://lantisproject.com/blog
Top
pythonic
Posts: 283
Joined: Mon Mar 11, 2019 5:47 am
Location: Australia

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by pythonic »

In case anyone missed the thread title change, Lantis now has a 2026-06-13 build up.
Top
fifonik
Posts: 180
Joined: Fri Dec 02, 2016 3:52 am
Location: Brisbane, AU

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by fifonik »

Changelog not available?
Top
pythonic
Posts: 283
Joined: Mon Mar 11, 2019 5:47 am
Location: Australia

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by pythonic »

fifonik wrote: ↑
Mon Jun 22, 2026 5:06 am
 Changelog not available?
The changelog in the first post was updated?
Top
fifonik
Posts: 180
Joined: Fri Dec 02, 2016 3:52 am
Location: Brisbane, AU

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by fifonik »

Ah, my bad.
I've red 'Changes since "BETA - 2026-04-08"' as 'Changes for "BETA - 2026-04-08"' so could not find the mentioned '2026-06-03'
%-)
So the main thing for me is OpenWrt 24.10.6 => OpenWrt 24.10.7. Will check the OpenWRT's changelog.
Top
ispyisail
Moderator
Posts: 5232
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by ispyisail »

@fiye68

Thanks for the detailed log — it made the bugs straightforward to track down.

There are two separate problems here:

1. nftables script bugs (now fixed)

Found five issues across three files in the gargoyle-tor package, all nftables migration problems:
  • tor.firewall — tmp_cron variable used but never defined in this script, causing the can't create, md5sum '' and mv: can't rename '' errors on every start/stop
  • tor.firewall — grep missing its input file, silently discarding crontab contents into nowhere
  • tor.firewall — nft delete set tor_active_ips4 fails on first run before the set exists
  • 050-tor.bwmon — bandwidth rules reference @tor_relays but the sets are named tor_relays4/tor_relays6 — wrong name, hence No such file or directory
  • 050-tor.bwmon — tcp dport { } with an empty set when relay mode is off — nftables rejects this unlike iptables
Also fixed the CPU spike: update_tor_nftset was calling nft add element once per relay IP (~10,000 times per minute). Replaced with a single batched nft -f - call.

PR submitted: https://github.com/lantis1008/gargoyle/pull/59

2. RAM (hardware limit — not fixable)

The OOM kill at 50% bootstrap is a separate problem:

Code: Select all

tor pid 6631 — 60484kB virtual, 51380kB RSS → killed by OOM
Tor needs ~50 MB just to load relay descriptors. With Gargoyle's full stack running on 128 MB that leaves no headroom. OpenSSL 3 has increased Tor's memory footprint and this appears to be the new floor. The WRT3200ACM won't be able to
run Tor reliably regardless of the script fixes — 256 MB is the practical minimum now.

If anyone has confirmed working hardware on current Gargoyle + Tor I'd be interested to know the model.
Top
ispyisail
Moderator
Posts: 5232
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by ispyisail »

Reply 1 — hotplug auto-share bug

Lantis,

I found another ksmbd issue while looking into the "Same folder on all disks" problem - USB drives that are hotplugged (inserted while the router is running) are never shared via ksmbd at all, even if ksmbd is already running.

The cause is in ksmbd.hotplug. When a drive is inserted, the hotplug script creates a UCI config section of type share:

Code: Select all

set ksmbd.$DEVICE="share"
But ksmbd.init only iterates sections of type sambashare:

Code: Select all

config_foreach smb_add_share sambashare
So the hotplug entry is silently ignored - it never gets written to ksmbd.conf and never appears in the UI. The equivalent script for the older samba36 package correctly uses sambashare.

The fix is a one-character change in ksmbd.hotplug:

Code: Select all

set ksmbd.$DEVICE="sambashare"
I have submitted a pull request with this fix: https://github.com/lantis1008/gargoyle/pull/60

---
Reply 2 — "Same folder on all disks" access denied bug

Lantis,

I tracked down the root cause of the known issue "Samba shares utilising ksmbd will not work if 'Same folder on all disks' option is selected".

Root cause

The "Same Partition On Any USB Drive" option saves the dev-based symlink path (e.g. /tmp/usb_mount/dev_sda1) to the ksmbd UCI config. When ksmbd.init writes this path into ksmbd.conf, the ksmbd kernel module returns
NT_STATUS_ACCESS_DENIED when any client tries to connect, because ksmbd does not follow symlinks for share root paths.

The "Only This Specific Drive" (UUID) option saves the real directory path (e.g. /tmp/usb_mount/UUID) and works correctly.

Confirmed on hardware

With symlink path in ksmbd.conf:

Code: Select all

$ smbclient //router/myshare -N -c 'ls'
  Anonymous login successful
  NT_STATUS_ACCESS_DENIED listing \*
With the symlink resolved to its real path:

Code: Select all

$ smbclient //router/myshare -N -c 'ls'
  Anonymous login successful
    .                                   D        0  ...
    testfile.txt                        A        6  ...
Fix

One line added to smb_add_share in ksmbd.init, immediately after the path is read from UCI:

Code: Select all

path="$(readlink -f "$path" 2>/dev/null || echo "$path")"
This resolves any symlink to its real path before writing ksmbd.conf. The fallback preserves the original path if the drive is not currently mounted, so saving a share config without a drive plugged in still works.

I have submitted a pull request with this fix: https://github.com/lantis1008/gargoyle/pull/61
Top
ispyisail
Moderator
Posts: 5232
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: Gargoyle 1.15.x OpenWrt 24.10 - 2026-06-13

Post by ispyisail »

● oliver44

Thanks for the suggestion — done.

In dual-band AP mode two new fields now appear below the existing encryption/password rows:
  • 5GHz Encryption — choose WPA3 SAE, WPA3/WPA2 mixed, WPA2 PSK, WPA PSK, OWE, or none independently of the 2.4 GHz band
  • 5GHz Password — separate passphrase for the 5 GHz AP
So you can run WPA2 PSK on 2.4 GHz for older devices while setting WPA3 SAE on 5 GHz. The fields only appear when both bands are active — single-band and WDS modes are unchanged. Existing configs load cleanly; on first open the 5 GHz
field shows whatever encryption was already set on that band.

PR submitted for review: https://github.com/lantis1008/gargoyle/pull/62
Top
Post Reply

Return to “Show / Tell / Contribute”