Because Entware only installs to a filesystem that is supported. In *nix systems, file owners and permissions is a native way to control access. Not so much on our routers, but we are just one device group of many that use Entware.I never found a solid reason why only ext formats were originally supported by the entware installer (which I based the swap code off and added *fat support). I assume ntfs would work too for both entware and swap files, I honestly forgot to follow up on it.
Symlinks will also not work on non supported filesystems.I never found a solid reason why only ext formats were originally supported by the entware installer (which I based the swap code off and added *fat support). I assume ntfs would work too for both entware and swap files, I honestly forgot to follow up on it.
dnscrypt-proxy does not need that anymore. The problem is elsewhere, do you have any kind of network configuration on top of your ISP, such as VPN? Also there might be some problem with the 384 branch that I don't know of, still running 380.xx on my AC56U.Recently upgraded the firmware on a 68u to 384.beta
DNScrypt with server set as google and wan dns set as 192.168.1.1 was working fine. DNSleak showed approx 60 google servers and no other servers. After upgrading the firmware DOH doesn't work anymore. nslookup yahoo.com in SSH doesn't resolve the address. I removed the dnscrypt directory and reinstalled RC3 but google as the server still doesn't work. I changed the server to cisco in the config file and restarted the service and it started working again.
I have already preresolved dns.google.com in /jffs/configs/dnsmasq.conf.add by adding the below lines.
Code:server=/dns.google.com/8.8.8.8 server=/download.dnscrypt.info/8.8.8.8
TIA
dnscrypt-proxy does not need that anymore. The problem is elsewhere, do you have any kind of network configuration on top of your ISP, such as VPN? Also there might be some problem with the 384 branch that I don't know of, still running 380.xx on my AC56U.
Just an FYI... this doesn't really "pre-resolve" anything, it just sends the query to 8.8.8.8 to resolve that specific domain name. Know the difference between "server=/domain/ip" and "address=/domain/ip".... I have already preresolved dns.google.com in /jffs/configs/dnsmasq.conf.add by adding the below lines.
Code:server=/dns.google.com/8.8.8.8 server=/download.dnscrypt.info/8.8.8.8
This is kinda obvious, but are you able to access dns.google.com from your browser?I know I no longer need to pre resolve google in dnsmasq as it's already there in the toml file to help the system / scripts boot but tried it since nothing else worked. No VPN / AI protect etc. Only AB and skynet. DNScrypt works fine if I use cisco/other server as the resolver but not if I change it to google. Only thing that's changed is the upgrade to 384.beta so maybe it's something to do with the new GPL.
Not if I use google as the server in dnscrypt. Yes if I use cisco/other serversThis is kinda obvious, but are you able to access dns.google.com from your browser?
2.0 final out.
Has V2 final been released yet?
Weird I'm gonna try the new beta soon on my AC56U. Hopefully I can reproduce it then. Waiting for a more stable beta or final.Not if I use google as the server in dnscrypt. Yes if I use cisco/other servers
@all I updated to 2.0.0 final and update the first post. The script is now out of beta as well .
Worked without a problem on RT-AC1900P on 384.3_beta1.@all I updated to 2.0.0 final and update the first post. The script is now out of beta as well .
=> Do you want to install dnscrypt-proxy to /jffs [y/n]: y
Info: Downloading manager
Info: Downloading nonroot
Info: Downloading dnscrypt-proxy-linux_arm64-2.0.0.tar.gz
[: <!267752: bad number
Info: Downloading public-resolvers.md
[: <!267752: bad number
Info: Downloading public-resolvers.md.minisig
linux-arm64/
linux-arm64/dnscrypt-proxy
linux-arm64/LICENSE
linux-arm64/example-dnscrypt-proxy.toml
linux-arm64/example-blacklist.txt
linux-arm64/example-cloaking-rules.txt
linux-arm64/example-forwarding-rules.txt
Info: Configure dnsmasq.postconf file for dnscrypt
Info: Creating wan-start file
Info: Configure wan-start file for dnscrypt
Info: Configuring dnscrypt-proxy...
Info: Set a DNS server for initializing dnscrypt-proxy
Info: and router services (e.g. ntp) at boot
=> Default is 8.8.8.8:
dnscrypt-proxy
dnscrypt-proxy.toml
example-blacklist.txt
example-cloaking-rules.txt
example-dnscrypt-proxy.toml
example-forwarding-rules.txt
LICENSE
manager
nonroot
public-resolvers.md
public-resolvers.md.minisig
I did the above with unaltered current amtm version. No need for a change as the installer URL never changed for the stable installer.Calling @thelonelycoder so hopefully he can include this in amtm
No need for a change as the installer URL never changed for the stable installer.
amtm has no option to install a dnscrypt-proxy beta version:... unless you would want to remove the menu option for the dnscrypt-proxy beta version
SNBForum scripts
1 open AB-Solution
2 install dnscrypt installer
3 update Entware
4 install pixelserv-tls beta version
5 install Skynet
Info: Detected ARMv7 architecture.
Info: JFFS custom scripts and configs are already enabled
Info: Choose what you want to do:
1) Install dnscrypt-proxy
2) Configure dnscrypt-proxy
3) Configure timezone
4) Install (P)RNG
5) Install swap file
q) Quit
=> Please enter the number designates your selection:
amtm has no option to install a dnscrypt-proxy beta version:
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!