ok - have now reloaded on WRT1900ACS and have most functions running. I rebuilt the settings from scratch and tested as they were applied one by one and TOR appears to now be working.
My computer is showing no internet connection on its network icon although there is.
LANTIS - are the https/url blocking bits working in this version? If so will add those back tomorrow and see how it works.
UPDATE - sorry scratch all the above - wthin a few mins all internal dhcp and external dns lost Back to 1.10 for 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.
tried again - reset to default - OK
Set up LAN subnet and wireless - OK
Set up 4 static DHCP leases - OK
Enabled TOR to be triggered per host - dhcp failed
Disabling Tor doesn't restore function nor does reboot afterwards - its as though the TOR enabling is overwriting some config somewhere. Can anyone else replicate this?
ok but can you enable the optin for tor to be triggered by individual hosts (you don't have to trigger any hosts) and see if a new client can join the network and receive an IP address?
(save your config before you do this so you can reload if it messes up)
phgerin wrote:Didn't test with previous builds.
I have tried noip.com and dyndns. It just don't update and the force option does nothing.
Mon May 14 14:02:07 2018 daemon.info ddns_gargoyle[4223]: Successfully retrieved local ip from url: http://www.tracemyip.org
Mon May 14 14:02:07 2018 daemon.info ddns_gargoyle[4223]: local IP = 109.129.yyy.xxx
Mon May 14 14:02:07 2018 daemon.info ddns_gargoyle[4223]: remote IP cannot be determined
Appears to be tied to SSL.
If you change the no-ip service to use http it will be ok.
I will investigate fixing properly.
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.
Can confirm that ddns is broken in earlier (ispy-0425) build and also openwrt trunk (early April). So ddns is probably also broken on your build and it's probably an upstream issue.
Right now I'm on 17.01.4 stable and will test it again when 18.06 RC is released.