Attempted this on my WRT610N running Kong's 19277M and I get a segmentation fault.
Perhaps I didn't upload the binary correctly? I downloaded it from http://lancethepants.com/files/index.php?dir=Binaries (DNSCrypt)/DNSCrypt-Proxy/0.10.1/, uploaded it to my web server and used wget to get it to my router.
Would really love to get this working, so any advice would be appreciated.
Try the (K2.4 toolchain) version if you're running K2.4 kernel. Do you have V1 or V2?
The difference was that dnscrypt-proxy version 0.9.3 could daemonize on port 53, even if it is used by DNSMasq, but version 0.10.1 cannot do it, so it has to have its own port. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
Happens for me either way. And this is with using the new 0.10.1 DD-WRT Toolchain version:
root@nevermore:/opt/script# ./dnscrypt-proxy -a 172.17.50.1 -P 40 -d
Segmentation fault
root@nevermore:/opt/script# ./dnscrypt-proxy -a 172.17.50.1
Segmentation fault
root@nevermore:/opt/script# ./dnscrypt-proxy
Segmentation fault
I have the same version of Kong firmware. For me, it works without problem. But I also have OTRW installed according to the Basmaf's OTRW take2. So, maybe it is missing some library, maybe your /jffs has some libraries which mess with the libraries loaded by dnscrypt-proxy.
Use your router's (gateway) IP instead of 172.17.50.1. dnscrypt-proxy cannot run on any IP, but only on IPs which are already available, like private networking IPs. Ok, 172.17.50.1 is private, but it has to belong to your router (br0). _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
Posted: Mon Jul 02, 2012 20:15 Post subject: working on wrt350n
I have it running on a 15k era build on a wrt350n. I am running OTRWtake2 and dnscrypt-proxy. It appears to Just Work.
I have been unable to get it to work on an Eko 18946 (17990 also) Mega VINT on a WRT54GS v1. The problem is not dnscrypt-proxy but jffs. As I understand it, this is a 32MB router so I would think it should have enough space but, jffs is acting all wonky: chmod doesn't work, only partial file copies, etc.
Posted: Mon Jul 02, 2012 22:00 Post subject: Re: working on wrt350n
rearden wrote:
I have it running on a 15k era build on a wrt350n. I am running OTRWtake2 and dnscrypt-proxy. It appears to Just Work.
I have been unable to get it to work on an Eko 18946 (17990 also) Mega VINT on a WRT54GS v1. The problem is not dnscrypt-proxy but jffs. As I understand it, this is a 32MB router so I would think it should have enough space but, jffs is acting all wonky: chmod doesn't work, only partial file copies, etc.
rearden
According to http://en.wikipedia.org/wiki/Linksys_WRT54G_series#WRT54GS , it has 32 MB RAM and 8 MB flash. Jffs is stored in the flash memory, not in the RAM. This means that on a Mega build there is almost no space left for jffs. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
I also found in the jffs wiki (about the 4th time through it) that a BS build has 640k /jffs but an Eko build has 1640k.
What is confusing is that when I first enable and clean jffs, it reports 6,400.00kb as total. Later it reports 768 or 640kb. I think I need a bit under 1mb to fit dnscrypt-proxy and filesystem.
I have the same version of Kong firmware. For me, it works without problem. But I also have OTRW installed according to the Basmaf's OTRW take2. So, maybe it is missing some library, maybe your /jffs has some libraries which mess with the libraries loaded by dnscrypt-proxy.
Use your router's (gateway) IP instead of 172.17.50.1. dnscrypt-proxy cannot run on any IP, but only on IPs which are already available, like private networking IPs. Ok, 172.17.50.1 is private, but it has to belong to your router (br0).
172.17.50.1 is my router's IP. I don't use the standard 192.168.x.x addresses.
I installed OTRW take2 tonight as well, and enabled jffs (which I hadn't been using before, as I'm running Optware off my USB drive connected to the router) and am getting the same result. Segmentation fault.