Friends, I would like to indicate which version is running better on Archer C7v2, because from what I understand there is another variant of the one made by @root.
so if anyone can quickly update me on this new vs, what are the differences, benefits etc .... I am grateful because I want to leave the router to use with the standardized FW.
I already thank you for the help, and please send the download link and if you need any different procedures to be used.
I'd rather use gargoyle than some of the crap I've seen produced here.
Stick with ddwrt man. Only thing good that came from this forum was the
breed bootloader.
hey if you guys use bcp38 with hue devices and connect to their servers, here is a way to control it via debug api, i had issues with bcp38 constantly disconnecting the bridge from the servers because it acquires your local ip address, in order to link with the bridge.
Hej everybody, first off: thanks @root for your efforts! it enabled me to actually build my own firmware! good job with the optimisations!
Unfortunately, I ended up locking myself out of my device and I am therefore unable to even connect to it or make any changes to the settings. I tried to enter filesafe mode but I am unable to. I tried every thing I could find online and before I get out my usb2serial adapter: can anyone confirm that failsafe does not work with this build? If it does with your device: when did you push that pesky button? Thanks!
I have never used Gargoyle, but in your opinion, what makes Gargoyle better than LEDE/OpenWRT? It has any fuction that we can't find in LEDE (HW NAT, better WiFi....)?
As for @r00t image, its a little smaller by around 3 -4 mb, but is also on a later kernel with his stable release 4.9.67.(nightlys are not patched), so no real improvements other than an upgraded kernel, or the latest snapshot of ledes builds 4.9.82, i believe is the most current.
i myself am currently using cliobrando's build because of the newer kernel, but i dont mind the bulk, because i use an overlay on usb stoarge, it has patches and seems to be pretty stable at the moment.
not sure if my last post by email ever got here, so if theres 2 posts i apologize in advance. but @klingon, I really have no idea i was just giving @gu3d3s more options, since nobody would respond to him lol, gargoyle just seemed to fit, since he was basically just a statue people would look at and walk by. im sure i come off as an ass hat, but it got a response, interesting eh? Anyways also like the brilliant fruttifresh stated, which is kinda pinning the tail on donkey so to say. gargoyle is over a year old, like @r00t image is on an older build. whos to say whats better and whats not? sometimes an older kernel has all the bugs worked out, or at least we know of the bugs and how to resolve them by now.
I've been having issues w/ this firmware over the last few weeks. My Wireless-N 2.5Ghz will drop to crawling speeds, and generally I can't get it back even with rebooting. All of my IOT devices (a couple cameras, Ecobee, some sensors) also get disconnected for a bit. Sometimes speeds end up just coming back randomly for a few days, then revert back again, seemingly randomly. Rebooting DOES reconnect the IOT devices typically, but it may not last too long.
This firmware had been working well for months before hand... anyone else experiencing similar?
It seems like v2 and v4 are relatively similar, and I need fastpath. Right now I'm running a binary OpenWRT build with FP patches but it breaks any existing networking modules from loading due to unknown symbols.
So I guess I'd either have to compile my own or use a different build?
Tried to make a new build but it failed, so it's time to fix the patches.
I'll do it but don't know when, my current build is running fine, so I don't need to rush.