What's new

DNScrypt dnscrypt installer for asuswrt

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

This can be exploited by a MITM, middle box blocking packets over 1500 bytes between the anonamous relay and DNS server as well. https://github.com/DNSCrypt/dnscrypt-proxy/issues/1255 and exploited to affect any DNS server over relay no matter what. And if he keeps this feature onboard after the fix is in for the servers, then I would consider it an inbuilt exploit.
A short recap of what happened during the past 3 versions
But now that the actual root cause has been found, and quickly fixed upstream, it is great to know that these workarounds will only be temporary and many servers will be faster and reliably anonymizable soon.
Version 2.0.42 is working well and is the version that should be used until the affected servers have been updated!
The workaround in this version will break anonymized DNS on these servers, But those servers will be used with regular DNSCrypt v2 (same security level as DoH) reliability for the user (It encrypts, authenticates and protects from MITM).

edit:
A new option in dnscrypt-proxy.toml was added in this version aswell.
If a user dont want to use a server that is not working with relays this can be changed to "true"
Code:
# skip resolvers incompatible with anonymization instead of using them directly

skip_incompatible = false
 
Last edited:
Hello all, wanted to provide an update and ask for input.

I've been using DoT for the past week and decided to jump back on the dnscrypt (DoH) wagon. After doing a clean install of version 2.0.42 using the installer, I get the following error at the very last step:
Code:
 Info:  Checking dnscrypt-proxy configuration...
[2020-03-30 21:08:59] [NOTICE] dnscrypt-proxy 2.0.42
[2020-03-30 21:08:59] [NOTICE] Network connectivity detected
[2020-03-30 21:08:59] [NOTICE] Source [public-resolvers] loaded
[2020-03-30 21:08:59] [NOTICE] Source [relays] loaded
[2020-03-30 21:08:59] [NOTICE] Configuration successfully checked
 Info:  Starting dnscrypt-proxy...
 *** Error:  Couldn't start dnscrypt-proxy
 *** Error:  Please send WebUI System Log to dev

After checking my syslog, it shows:
Code:
Mar 30 21:19:05 dnscrypt-proxy[11135]: dnscrypt-proxy 2.0.42
Mar 30 21:19:05 dnscrypt-proxy[11135]: Network connectivity detected
Mar 30 21:19:05 dnscrypt-proxy[11135]: Source [public-resolvers] loaded
Mar 30 21:19:05 dnscrypt-proxy[11135]: Source [relays] loaded
Mar 30 21:19:05 dnscrypt-proxy[11135]: Firefox workaround initialized
Mar 30 21:19:05 dnscrypt-proxy[11135]: listen udp 127.0.1.1:53: bind: address already in use

I use Diversion/pixelserv and Skynet, but I can't think of anything on my network that would be conflicting with that address (udp 127.0.1.1:53). Has anyone else experienced any type of similar issue in the past?
 
Hello all, wanted to provide and update and ask for input.

I've been using DoT for the past week and decided to jump back on the dnscrypt (DoH) wagon. After doing a clean install of version 2.0.42 using the installer, I get the following error at the very last step:
Code:
 Info:  Checking dnscrypt-proxy configuration...
[2020-03-30 21:08:59] [NOTICE] dnscrypt-proxy 2.0.42
[2020-03-30 21:08:59] [NOTICE] Network connectivity detected
[2020-03-30 21:08:59] [NOTICE] Source [public-resolvers] loaded
[2020-03-30 21:08:59] [NOTICE] Source [relays] loaded
[2020-03-30 21:08:59] [NOTICE] Configuration successfully checked
 Info:  Starting dnscrypt-proxy...
 *** Error:  Couldn't start dnscrypt-proxy
 *** Error:  Please send WebUI System Log to dev

After checking my syslog, it shows:
Code:
Mar 30 21:19:05 dnscrypt-proxy[11135]: dnscrypt-proxy 2.0.42
Mar 30 21:19:05 dnscrypt-proxy[11135]: Network connectivity detected
Mar 30 21:19:05 dnscrypt-proxy[11135]: Source [public-resolvers] loaded
Mar 30 21:19:05 dnscrypt-proxy[11135]: Source [relays] loaded
Mar 30 21:19:05 dnscrypt-proxy[11135]: Firefox workaround initialized
Mar 30 21:19:05 dnscrypt-proxy[11135]: listen udp 127.0.1.1:53: bind: address already in use

I use Diversion/pixelserv and Skynet, but I can't think of anything on my network that would be conflicting with that address (udp 127.0.1.1:53). Has anyone else experienced any type of similar issue in the past?
well first off you need to make sure you have dnsprivacy(dot) turned off (turn off stubby) reboot your router. then try running dnscrypt-proxy installer.
 
Last edited:
Quick comment / bug report (?)... I did a search and didn't see it previously noted.

In AMTM, using "U" to check for updates, it correctly identifies that there's an update available for DNSCrypt, but when I try to update DNSCrypt from 2.0.36 to 2.0.42, it just re-downloads 2.0.36. I had to run the install command at the prompt
Code:
curl -L -s -k -O https://raw.githubusercontent.com/thuantran/dnscrypt-asuswrt-installer/master/installer && sh installer ; rm installer
to download 2.0.42. Dunno.
 
Quick comment / bug report (?)... I did a search and didn't see it previously noted.

In AMTM, using "U" to check for updates, it correctly identifies that there's an update available for DNSCrypt, but when I try to update DNSCrypt from 2.0.36 to 2.0.42, it just re-downloads 2.0.36. I had to run the install command at the prompt
Code:
curl -L -s -k -O https://raw.githubusercontent.com/thuantran/dnscrypt-asuswrt-installer/master/installer && sh installer ; rm installer
to download 2.0.42. Dunno.
Think you updated from a old version of the installer.
https://www.snbforums.com/threads/release-dnscrypt-installer-for-asuswrt.36071/page-75#post-551251
But you solved it the correct way ;)
 
DI_VERSION="v2.1.4" is Now Available!
To help to try to uncomplicated some of the many changes DNScrypt-Proxy 2 has implemented with its previous releases.Dnscrypt installer for Asuswrt has been adapted to accommodate some of the new options provided inside the dnscrypt-proxy.toml, such as skip_incompatible. This allows users to now skip using dnscrypt-servers that are incompatible with anonymous relays, which would otherwise leak traffic if the user allowed the servers to be used with other servers that were bound for relay traffic.

What is New:
  • Enhanced use of security features for DoH and Dnscrypt-v2 protocol
  • Option to use Load Balance Estimator to reduce latency with servers
  • Option to skip_incompatible= Warning is provided in advanced so users can choose to skip potentially incompatible servers while using relays.


Many Thanks @Zastoff for providing several days of testing && collaboration.

Edit **Minor Updates**

  • Fixed Minor errors in the order of execution of the update function. Thanks @SMS786 for pointing out a bug/glitch.
***
Enhancements explained
  • DoH (tls_disable_session_tickets = true) A disadvantage of servers storing session tickets is that they eliminate the effects of forward secrecy when a server uses the same key for long time it is like keeping a finger print of you. With this option set to true dnscrypt-proxy2 request DoH server for a new session ticket each time a new connection is created. That is, the secrecy of all sessions on a server using tickets depends on the ticket key being kept secret.
  • DNSCrypt v2 (w/dnscrypt_ephemeral_keys = true) With this option, it is the same principle, but a key is used instead. It creates a new Key for every query. Without this, the server stores record of the key, and dnscrypt-proxy uses the same key to reduce the effort of starting a new one, the problem with this is that it is a bad security practice and makes the traffic to and from user/device identifiable.
  • Anonymized DNSCrypt(w/skip_incompatible=true) A glitch in some Dnscrypt-Servers has been found. Some of queries are fragmented bringing into question the reliability of the Dnscrypt-Server being used. For that, a workaround (fragments_blocked =) was created to make them behave as reliable Dnscrypt- Servers- At-least until they are fixed. Because of the issues present at this time, these servers are not compatible with relays though, but they are compatible to be ran as regular Dnscrypt-servers using the work around. The option (skip_incompatible) allows for dnscrypt-proxy 2 to detect servers with the same incompatibilities. Users that rely on relays anonymity can now skip using any incompatible resolver that will not work with relays thus preventing any external traffic leaks.
  • All options above prevent fingerprinting users & devices.
 
Last edited:
Thanks @SomeWhereOverTheRainBow for this new version of the installer!
It is now finely tuned and easier to configure with more secure options :)
Available in amtm (di)
I have come to love the:
Code:
Info:  Choose how your DNS servers are selected:
  1) Automatically
It is easy mode, fast, secure with options for even more privacy with anonymized DNS (using relays)
Info: Detected ARMv7 architecture.
Info: JFFS custom scripts and configs are already enabled
Info: DNS Environment is Ready.
Info: DI_VERSION=v2.1.4
Info: DNSCRYPT_VER=2.0.42
Info: Manager file is Up-To-Date!
Info: Choose what you want to do:
1) Install/Update dnscrypt-proxy
2) Uninstall dnscrypt-proxy
3) Configure dnscrypt-proxy
4) Set timezone
5) Unset timezone
6) Install (P)RNG
7) Uninstall (P)RNG
8) Install swap file
9) Uninstall ALL
q) Quit
=> Please enter the number that designates your selection:, [1-9/q]: 3
Info: This operation allows you to configure dnscrypt-proxy
=> Do you want to proceed? [y/n]: y
Info: Configuring dnscrypt-proxy...
Info: Checking dnscrypt-proxy configuration...
[2020-04-11 07:49:31] [NOTICE] dnscrypt-proxy 2.0.42
[2020-04-11 07:49:31] [NOTICE] Network connectivity detected
[2020-04-11 07:49:31] [NOTICE] Source [public-resolvers] loaded
[2020-04-11 07:49:31] [NOTICE] Source [relays] loaded
[2020-04-11 07:49:31] [NOTICE] Anonymized DNS: routing everything via [anon-xx-xx anon-xxx-xx]
[2020-04-11 07:49:31] [NOTICE] Configuration successfully checked
Info: Found previous dnscrypt-proxy config file
Info: How do you want to reconfigure:
Info: 1) Start from previous settings file
Info: 2) Start from default config
=> Your selection, [1-2]: 1
Info: Use previous settings file
=> Do you want to redirect all DNS resolutions on your network through this proxy? [y/n]: y
Info: DNSFilter is Already on.
Info: User can choose to keep any custom dnsfilter values and only redirect non-custom traffic.
=> Do you want to redirect only SOME DNS resolutions on your network through this proxy? [y/n]: y
Info: Set DNSFilter to Control DNS through this proxy, while leaving any Custom Rules and Values.
=> Do you want to use DNS server over IPv6 (yes only if your connection has IPv6)? [y/n]: n (I don`t have IPv6)
Info: Choose DNS resolving load balancing strategy:
1) p2 (default) (randomly choose between the top 2 fastest servers)
2) ph (randomly choose between the top fastest half of all servers)
3) first (always pick the fastest server in the list)
4) random (just pick any random server from the list)
=> Select your mode, [1-4]: 1
=> Do you want to use load balance estimator to adjust resolvers based on latency calculations? [y/n]: y
Info: Choose how your DNS servers are selected:
1) Automatically
2) Manually
3) Static
=> Select your mode, [1-3]: 1
(How servers are filtered from public-resolvers.md) (Link to servers)
=> Use only servers that support the DNSCrypt protocol [y/n]: y ( also enables dnscrypt_ephemeral_keys = true)
=> Use only servers that support the DNS-over-HTTPS protocol [y/n]: n (DoH is not compatible with anonymized DNS yet)
=> Use only servers that support DNSSEC [y/n]: y
=> Use only servers that do not log user's queries [y/n]: y
=> Use only servers that do not filter result [y/n]: y
Info: Set the DNS server(s) for initializing dnscrypt-proxy
Info: and router services (e.g. ntp) at boot
=> Default is 9.9.9.9: 1.1.1.1
=> 2nd Default is 8.8.8.8: 1.0.0.1
=> Set log level, default is 2, 0 is the most verbose, [0-6]: 2
Info: Writing dnscrypt-proxy configuration...
Info: Evaluating other possibilities for dnscrypt-proxy configuration...
Info: Checking for Anonymized Dnscrypt Support
Info: Users may specify Wild-card Relay Support (server_name *) with option 1 (this supports only DNSCrypt Servers).
* Warning: All DNSCRYPT Server traffic will be sent through same set of chosen Relays with Wild-Card Option.
Info: Option 2 gives users the choice to Setup Relays per Dnscrypt-Server.
Info: Option 3 allows the users to skip relay configuration or remove old relays configurations.
* Warning: Option 1 & 2 delete old relay configurations.
* Warning: Issues may occur if user is not using same servers as defined in relays.
Info: What do you want to do:
1) All Servers with Wild-Card Relay Support.
2) Pick Relays for DNSCRYPT servers (Per Server).
3) Skip Setting-up/Modifying Relay Support.
=> Your choice, [1-3]: 1
Info: This allows users to setup wildcard relay support for all compatible servers
=> Do you want to skip using incompatible resolvers instead of using them directly? [y/n]: y
Info: Available Relay servers:
1) anon-am-us: Anonymized DNS relay hosted in Seattle - US
.....
35) anon-v.dnscrypt.uk-ipv4: Anonymized DNS relay hosted in UK on Vultr
=> Please choose RELAY server, [1-35]: xx
=> Please choose next RELAY server or press n to stop, [1-35/n]: xx
=> Please choose next RELAY server or press n to stop, [1-35/n]: n
Info: Checking dnscrypt-proxy configuration...
[2020-04-11 07:51:02] [NOTICE] dnscrypt-proxy 2.0.42
[2020-04-11 07:51:02] [NOTICE] Network connectivity detected
[2020-04-11 07:51:02] [NOTICE] Source [public-resolvers] loaded
[2020-04-11 07:51:02] [NOTICE] Source [relays] loaded
[2020-04-11 07:51:02] [NOTICE] Anonymized DNS: routing everything via [anon-xx-xx anon-xxx-xx]
[2020-04-11 07:51:02] [NOTICE] Configuration successfully checked
Info: Restarting dnscrypt-proxy with new config...
With this setup: I have 27 encrypted DNS servers, but with "load balancing strategy" P2 it will use the top 2 DNS servers ;)
And these 27 DNS servers have been filtered/tested on startup and is compatible with anonymized DNSCrypt.
Code:
Apr 11 07:51:31 dnscrypt-proxy[15599]: Server with the lowest initial latency: xxx-dnscrypt-xx (rtt: 21ms)
Apr 11 07:51:31 dnscrypt-proxy[15599]: dnscrypt-proxy is ready - live servers: 27
DNSCrypt Installer also have built in "Health Check" to help out with Relay randomization :)
Any questions on this setup or want help with another setup just ask ;) (Tested most setups i can think of)

Updated the NextDNS how to: Now more secure with "tls_disable_session_tickets = true" (to better reflect the new version of the installer)
 
Last edited:
Hello, I have a problem. And that comes since the firmware update and new configuration of the dnscrypt installer:

**In the Asus Log:**

Apr 16 20:54:35 GLM2900: Warning: dnscrypt-proxy is dead
Apr 16 20:54:35 GLM2900: Start dnscrypt-proxy
Apr 16 20:54:45 GLM2900: Warning: dnscrypt-proxy is dead
Apr 16 20:54:45 GLM2900: Start dnscrypt-proxy
Apr 16 20:54:56 GLM2900: Warning: dnscrypt-proxy is dead
Apr 16 20:54:56 GLM2900: Start dnscrypt-proxy

**Putty:**

Enter option di
_____________________________________________

Info: Detected ARMv8 architecture.
Info: JFFS custom scripts and configs are already enabled
Info: DNS Environment is Ready.
Info: DI_VERSION=v2.1.4
fatal error: out of memory allocating heap arena map

runtime stack:
runtime.throw(0x518803, 0x27)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/panic.go:1114 +0x54 fp=0x 7fda5970f0 sp=0x7fda5970c0 pc=0x40a64
runtime.(*mheap).sysAlloc(0x94fc00, 0x400000, 0x7fda597208, 0x34528)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/malloc.go:725 +0x5f0 fp=0 x7fda5971a0 sp=0x7fda5970f0 pc=0x1aed0
runtime.(*mheap).grow(0x94fc00, 0x1, 0x0)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mheap.go:1286 +0x134 fp=0 x7fda597210 sp=0x7fda5971a0 pc=0x349a4
runtime.(*mheap).allocSpan(0x94fc00, 0x1, 0x2a00, 0x9641e8, 0x0)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mheap.go:1124 +0x610 fp=0 x7fda597290 sp=0x7fda597210 pc=0x34710
runtime.(*mheap).alloc.func1()
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mheap.go:871 +0x60 fp=0x7 fda5972f0 sp=0x7fda597290 pc=0x6ac60
runtime.(*mheap).alloc(0x94fc00, 0x1, 0x7fda59012a, 0x25b84)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mheap.go:865 +0x64 fp=0x7 fda597340 sp=0x7fda5972f0 pc=0x33d14
runtime.(*mcentral).grow(0x960ad8, 0x0)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mcentral.go:255 +0x74 fp= 0x7fda597390 sp=0x7fda597340 pc=0x26374
runtime.(*mcentral).cacheSpan(0x960ad8, 0x1c410)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mcentral.go:106 +0x338 fp =0x7fda5973e0 sp=0x7fda597390 pc=0x25e68
runtime.(*mcache).refill(0x7fb4616108, 0x2a)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mcache.go:138 +0xa4 fp=0x 7fda597410 sp=0x7fda5973e0 pc=0x258b4
runtime.(*mcache).nextFree(0x7fb4616108, 0xffffffffffffff2a, 0x936d18, 0x938720, 0x7fda5974a8)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/malloc.go:868 +0x8c fp=0x 7fda597460 sp=0x7fda597410 pc=0x1b19c
runtime.mallocgc(0x180, 0x502e80, 0x7fda597501, 0x7fda597568)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/malloc.go:1036 +0x688 fp= 0x7fda597520 sp=0x7fda597460 pc=0x1b9b8
runtime.newobject(0x502e80, 0x7f8fcf6000)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/malloc.go:1165 +0x38 fp=0 x7fda597550 sp=0x7fda597520 pc=0x1bd48
runtime.malg(0x8000, 0x0)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/proc.go:3354 +0x2c fp=0x7 fda5975a0 sp=0x7fda597550 pc=0x4b3ec
runtime.mpreinit(0x938720)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/os_linux.go:339 +0x28 fp= 0x7fda5975c0 sp=0x7fda5975a0 pc=0x3e258
runtime.mcommoninit(0x938720)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/proc.go:630 +0x108 fp=0x7 fda597610 sp=0x7fda5975c0 pc=0x44528
runtime.schedinit()
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/proc.go:547 +0x9c fp=0x7f da597680 sp=0x7fda597610 pc=0x440dc
runtime.rt0_go(0x7fda597ddb, 0x7fda597df9, 0x0, 0x7fda597e02, 0x7fda597e23, 0x7f da597e30, 0x7fda597e38, 0x7fda597e55, 0x7fda597e60, 0x7fda597e73, ...)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/asm_arm64.s:70 +0xb8 fp=0 x7fda5976b0 sp=0x7fda597680 pc=0x6d378
amtm 3.1.6 FW by thelonelycoder


What can I do? Reinstall does not work because of this error. But over 200mb Ram are still free!

Many thanks
 
Hello, I have a problem. And that comes since the firmware update and new configuration of the dnscrypt installer:

**In the Asus Log:**

Apr 16 20:54:35 GLM2900: Warning: dnscrypt-proxy is dead
Apr 16 20:54:35 GLM2900: Start dnscrypt-proxy
Apr 16 20:54:45 GLM2900: Warning: dnscrypt-proxy is dead
Apr 16 20:54:45 GLM2900: Start dnscrypt-proxy
Apr 16 20:54:56 GLM2900: Warning: dnscrypt-proxy is dead
Apr 16 20:54:56 GLM2900: Start dnscrypt-proxy

**Putty:**

Enter option di
_____________________________________________

Info: Detected ARMv8 architecture.
Info: JFFS custom scripts and configs are already enabled
Info: DNS Environment is Ready.
Info: DI_VERSION=v2.1.4
fatal error: out of memory allocating heap arena map

runtime stack:
runtime.throw(0x518803, 0x27)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/panic.go:1114 +0x54 fp=0x 7fda5970f0 sp=0x7fda5970c0 pc=0x40a64
runtime.(*mheap).sysAlloc(0x94fc00, 0x400000, 0x7fda597208, 0x34528)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/malloc.go:725 +0x5f0 fp=0 x7fda5971a0 sp=0x7fda5970f0 pc=0x1aed0
runtime.(*mheap).grow(0x94fc00, 0x1, 0x0)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mheap.go:1286 +0x134 fp=0 x7fda597210 sp=0x7fda5971a0 pc=0x349a4
runtime.(*mheap).allocSpan(0x94fc00, 0x1, 0x2a00, 0x9641e8, 0x0)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mheap.go:1124 +0x610 fp=0 x7fda597290 sp=0x7fda597210 pc=0x34710
runtime.(*mheap).alloc.func1()
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mheap.go:871 +0x60 fp=0x7 fda5972f0 sp=0x7fda597290 pc=0x6ac60
runtime.(*mheap).alloc(0x94fc00, 0x1, 0x7fda59012a, 0x25b84)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mheap.go:865 +0x64 fp=0x7 fda597340 sp=0x7fda5972f0 pc=0x33d14
runtime.(*mcentral).grow(0x960ad8, 0x0)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mcentral.go:255 +0x74 fp= 0x7fda597390 sp=0x7fda597340 pc=0x26374
runtime.(*mcentral).cacheSpan(0x960ad8, 0x1c410)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mcentral.go:106 +0x338 fp =0x7fda5973e0 sp=0x7fda597390 pc=0x25e68
runtime.(*mcache).refill(0x7fb4616108, 0x2a)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/mcache.go:138 +0xa4 fp=0x 7fda597410 sp=0x7fda5973e0 pc=0x258b4
runtime.(*mcache).nextFree(0x7fb4616108, 0xffffffffffffff2a, 0x936d18, 0x938720, 0x7fda5974a8)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/malloc.go:868 +0x8c fp=0x 7fda597460 sp=0x7fda597410 pc=0x1b19c
runtime.mallocgc(0x180, 0x502e80, 0x7fda597501, 0x7fda597568)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/malloc.go:1036 +0x688 fp= 0x7fda597520 sp=0x7fda597460 pc=0x1b9b8
runtime.newobject(0x502e80, 0x7f8fcf6000)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/malloc.go:1165 +0x38 fp=0 x7fda597550 sp=0x7fda597520 pc=0x1bd48
runtime.malg(0x8000, 0x0)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/proc.go:3354 +0x2c fp=0x7 fda5975a0 sp=0x7fda597550 pc=0x4b3ec
runtime.mpreinit(0x938720)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/os_linux.go:339 +0x28 fp= 0x7fda5975c0 sp=0x7fda5975a0 pc=0x3e258
runtime.mcommoninit(0x938720)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/proc.go:630 +0x108 fp=0x7 fda597610 sp=0x7fda5975c0 pc=0x44528
runtime.schedinit()
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/proc.go:547 +0x9c fp=0x7f da597680 sp=0x7fda597610 pc=0x440dc
runtime.rt0_go(0x7fda597ddb, 0x7fda597df9, 0x0, 0x7fda597e02, 0x7fda597e23, 0x7f da597e30, 0x7fda597e38, 0x7fda597e55, 0x7fda597e60, 0x7fda597e73, ...)
/opt/hostedtoolcache/go/1.14.1/x64/src/runtime/asm_arm64.s:70 +0xb8 fp=0 x7fda5976b0 sp=0x7fda597680 pc=0x6d378
amtm 3.1.6 FW by thelonelycoder


What can I do? Reinstall does not work because of this error. But over 200mb Ram are still free!

Many thanks
First off What is the Make and Model of your router?
It really looks like your JFFS or NVRAM is full. we need to see a screenshot of
Untitled.jpg

Untitled3.jpg


If this is ram related, do you have a swap configured?
I don't think this was caused by Dnscrypt-proxy, but I do believe Dnscrypt-proxy suffered side effect because of what ever issue your router is experiencing in association to some form of lack of memory in with your router.
 
Last edited:
Model RT-AC86U
Firmware Version 384.16
Firmware Build Sun Apr 5 17:38:01 UTC 2020 merlin@2c43617
Bootloader (CFE) 1.0.0.6

Okay a swap is not set up yet. I would have to do that then?

lg.
 

Attachments

  • 1.png
    1.png
    255.7 KB · Views: 173
  • 22.png
    22.png
    304.8 KB · Views: 153
Model RT-AC86U
Firmware Version 384.16
Firmware Build Sun Apr 5 17:38:01 UTC 2020 merlin@2c43617
Bootloader (CFE) 1.0.0.6

Okay a swap is not set up yet. I would have to do that then?

lg.
I recommend using AMTM to setup your swap file. If AMTM is giving you issues, then I am wont be much help.
 
@Kenji you may want to fully wipe the router (M&M Config and Nuclear Reset), at least the JFFS partition and your USB drive before you begin again.

The following posts may be useful to you to get a good/known install of the firmware and amtm + USB drive format + swap file + script(s). :)

https://www.snbforums.com/threads/ax88-packet-loss.62891/#post-563326

amtm Step-by-Step https://www.snbforums.com/threads/amtm-step-by-step-install-guide-l-ld.56237/#post-483421

M&M Config https://www.snbforums.com/threads/n...l-and-manual-configuration.27115/#post-205573

WPS NVRAM Erase https://www.snbforums.com/threads/b...eta-is-now-available.55520/page-9#post-473141

Nuclear Reset https://www.snbforums.com/threads/major-issues-w-rt-ac86u.56342/page-4#post-495710
 
amtm scripts
these scripts run on it. Can it be that the logs consume the RAM?
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top