Gargoyle Forum

I've been looking at this, just wondering if it's something that could be re-set via UCI or something every time the system saves and reloads? Perhaps via a Plugin or something even? Am I right that the following is run, every time the "Save Changes" button is clicked? /usr/lib/gargoyle/re...

Nevermind, repulled, re-ran the commands, did make custom, it's all happy this time around for some odd reason. Cool beans! :) When I try and run "make custom" the first time, it builds successful and I've got that running, flashed, happy on the WDR4300 no worries. However if I try and re...

Chilling_Silence wrote:Trying to build for WDR4300 but not having any luck. Just built OpenWRT a number of times successfully so maketools all there.

Nevermind, repulled, re-ran the commands, did make custom, it's all happy this time around for some odd reason. Cool beans!

Trying to build for WDR4300 but not having any luck. Just built OpenWRT a number of times successfully so maketools all there.

Just so I'm not missing anything, what should I be running to make it for that target and where should I expect the output files to be?

Many thanks

I can confirm it's also working for me, thankyou very much for posting that :-) I've also mirrored that German firmware and included it with the standard TP-Link firmware, as well as 1.5.6 of Gargoyle here in case anybody was after it: https://docs.google.com/open?id=0BxtKTqslmyySN3ZPMHF4b2dOZVU Tha...

If only there was a way to get Gargoyle working with these newer ones in the mean time.

OpenWRT works, but it's not quite the consolation prize I was hoping for right now....

I'm sure progress will come soon enough though.

Yes that'll work fine, you'll just have double-NAT, that's all.

OK, thanks for the heads up. I guess we just sit tight and wait then? :-) EDIT: I'm kinda surprised Eric hasn't run into this himself yet. I've recommended this router to *another* friend who is also in the same boat. However, yesterday this 2nd friend (Yes, more than one friend!! :O ) took his back...

So as somebody with basically zero programming knowledge, I thought I'd give it a crack anyway putting that patch on backfire. Unfortunately it looks like there's been some pretty big changes with the source code in trunk vs backfire and I have absolutely no idea where to pop those commands in. :-/

Not with trunk, only backfire.