Gargoyle Forum

I can confirm the last message.

Was having this problem with Chrome on Linux. From this thread I took a look and the router and PC disagreed on the time by about 15 minutes.

Changed the time at the Linux end, now login works fine.

I am about to embark on setting up OpenVPN to allow access to my home network when I am out and about. It sounds somewhat complex and I want to minimize unnecessary 'issues'. I currently have firmware 1.5.11 on a WNDR3800. I'm happy to start with just 1 client (A Windows7 laptop), accessing my netwo...

OK, this matches with me too - I am using Avast on my Win PC!

I will linger until someone comes up with a solution... Or Avast fix the problem...

Note that I don't think this is a 'New Year' triggered thing.

Look at start of thread - First report was 2/Oct/2013.

Rewind... I was wrong with that last post. (I think Chrome auto-completed to include the "/login.sh" which works... to some degree at least) Chrome IS still exhibiting the bad behaviour I screen-grabbed earlier. So, any wisdom on why Chrome doesn't work right with the Gargoyle GUI??? Getti...

OK - I think I have figured this out. Windows had decided my cabled LAN connection was a 'Public Network', and this was causing other weird behaviour with some things I was working on (pyTivo to be precise). One I set it to 'Home Network', Chrome started to behave. Very strange that Chrome behaved l...

For any future travellers this way... The answer seems to be here:
Forum thread: Forced DNS Exceptions

Basically, turn off the "Force Clients To Use Router DNS Servers" option, but block Port 53, for the clients you want to restrict.

Seems to work.

FYI - I finally got around to putting Gargoyle on my WNDR3800. Took a while because the family were not really up to the risk of the Internet being out for a day/evening while I mucked around! And I almost just used the built-in Netgear 'parental control' stuff, but decided I wanted more control via...

Small update: If in Chrome I use the URL: http://192.168.1.1/login.sh I do get the login screen, but then, when I click Login I get the same sort of result with "301 Moved Permanently". It's strange - I can then get some of the screens up by explicitly putting in URLs like "192.168.1....

I just started using Gargoyle 1.5.11 last night on a WNDR3800, and am having this same annoying problem as @jsaville. Basically, if I go to "192.168.1.1" in Chrome "Version 31.0.1650.63 m" from my main PC (Win7-64), I get: Server: httpd_gargoyle/1.0 14mar2008 Date: Mon, 30 Dec 20...

drawz wrote:I again suggest the TP-Link WDR4300 or WDR3600.

They are not even listed in the Gargoyle page of "Supported Routers"??? So I kind-of ignored your first mention of them.
Though I now see that there are firmware files for them.

So confusing for the uninitiated...