This clearly indicates that there is no problem with cabling etc., but rather a problem internal to the MacPro itself. I've done each of the following with the indicated results:ģ) Rebooted using a FW hard drive as startup volume– problem persistsĤ) Substituted one of the Macbook Pros for the MacPro by re-connecting the ethernet cable to the MBP in place of the MacPro. But I think I have isolated the problem to a hardware issue with the MacPro. I have done all of the troubleshooting efforts I know of without resolving the issue. The MacPro is able to connect to the other computers on the LAN. All other computers on the network function properly and are able to access the internet normally. Suddenly for no apparent reason the MacPro has lost the ability to connect to the internet, either via ethernet or wirelessly. Hello.I have a home LAN with a MacPro connected by ethernet/WiFi and three Macbook Pros connected by WiFi. Please refer to the File Versions table to see which builds include JFFS. Generally you micro or mini builds should allow for more jffs space. if the year is 1970 it loops back to checking the time). Time is synchronized from an IP number and the router checks the time before starting dnscrypt (i.e. I don't use hostip, since I want no unencrypted DNS requests. I don't think they have gone for good, but it seems to have helped a bit. I used the Tomato build most, but I have switched to #4 since I had some very short periods of the router being unresponsive.
Opendns dnscrypt tomato shibby code#
Which means ~40% of original binary code is not used.Īll work for me, except #5. TARGET_CFLAGS += -fdata-sections -ffunction-sections For this round of binaries I decided to not add a few addition flags (LDFLAGS) just to make sure they're not messing anything up, but this also resulted in bigger binaries.Īnother way to make the dnscrypt-proxy smaller is excluding code sections from binary which not really used. I can compile them to be aproximatley 1/2 their current size. Some routers simply may not simply have the space for sufficient jffs, though I would imagine that the e2000/e3000 with their 8MB could.Īlso, by throwing off some linker flags from original configure.ac we'll able to pack it with $ upx -ultra-brute. If you would like to test the binaries for me, you can also load them to /tmp (ram) for testing purposes. See if you can acquire a firmware that will allow around. For this round of binaries I decided to not add a few addition flags (LDFLAGS) just to make sure they're not messing anything up, but this also resulted in bigger binaries. The binaries I uploaded for DD-WRT right now are a little bigger, I can compile them to be aproximatley 1/2 their current size. I can use nv60k builds, but which one? Eko or Brainslayer? I've read somewhere that Brainslayer builds give more jffs2 space than EKO's. So, E2000 is out of option.įor DNScrypt, one need a jffs space of around 1MB. I'm just planning to run OTRW and DNScrypt.įor OTRW, one need a USB enabled router. So which firmware can I use to increase my jffs? I'm not many of router's services (e.g. Posted: Sat 15:37 Post subject: Re: confused! ipkg-entware/dnscrypt-proxy/opt/sbin/dnscrypt-proxy ipkg-entware/dnscrypt-proxy/opt/sbin/dnscrypt-proxyĤ32K. Posted: Sat 15:00 Post subject: Re: confused! I am also skeptical about which firmware builder to choose. There are five DD-WRT 0.12 version binaries which are available here : Now, I am unclear which files to put where and what scripts to run where. If I enable jffs2, I only get the following space: I just need some guidance before I mess around with my router in regards to DNScrypt Posted: Sat 14:14 Post subject: confused! Toolchain-mipsel_gcc-linaro_uClibc-0.9.32 #4 I downloaded from DD-WRT site and tried any that would work. Does anyone know what is different between the versions? He just mentions ddwrt toolchains. Lancethepants has several different variants including 5 different ddwrt versions. I see that opendns released two revisions in the last week or so, the latest being 0.12 Posted: Thu 17:23 Post subject: new version Tomato K26): works fine on my routers.Ģ times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)Į4200 V1 running freshtomato 2020.8 (bridged with LAN cable)ģ times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable) Version compiled with DD-WRT toolchain: segmentation fault Tried dnscrypt-proxy from /files with the following result: