Gargoyle Forum

From an OpenWrt 23.05 point of view there are many options. One that is particularly interesting is the GLiNet Flint 2 (aka MT6000). Wifi 6, loads of flash storage and processing power, 2.5gbps WAN and LAN, and a built in recovery method making it very difficult to brick. It is gaining a lot of popu...

I’ve been told that this problem should now be resolved!

I don’t have that many users to test with. Would you dump your data file and send it to me so I can do some checking on my end? /etc/init.d/bwmon_gargoyle stop Export the data from /usr/data/bwmon /etc/init.d/bwmon_gargoyle start It would also be worth checking on 1.14 or 1.15 for the same error. I ...

What’s the build error? Would help narrow it down too. It shouldn’t be looping under this: make FULL_BUILD=true ath79.default Once it fails, re run as make BUILD_THREADS=1 ath79.default This should then make the error that is stopping the build the last thing on screen (as it now runs single threade...

I have a prototype of this working locally. Here's a diff if you want to try it yourself. There's currently ZERO error checking. You need to enter a proper ip/subnet for it to work e.g. 192.168.10.0 255.255.255.0 Note the trailing zero on the IP. I will write code that checks and fixes this later an...

mvebu works now.
Someone at OpenWrt has "fixed" WPA3 on these devices so it now "works".
It looks like all it does is not crash, and offload the cryptographic operations to the CPU. Surprisingly this router can't seem to handle that and it runs terribly slow.
Stick with WPA2.

I’m looking at mvebu today.
I think it is just wpad missing. Should know by tonight.

To make it clear, you will not be able to install the driver from any location as the kernel is incompatible.
You must compile your own version of the firmware and include the driver.

So your problem is a missing driver? The system otherwise boots and operates fine?
You must custom compile the driver you need in.