Sorry, the switch leds are not controllable at the moment. Use a black tape as described above...
What is MC?
Midnight Commander =MC
Keep in mind that most of the wireless code is provided by the mac80211 package (backports), which replaces the kernel's own wireless drivers (so any updates/ fixes there are not directly reflected in the mac80211/ backports variant).
Hey there!
Thank you for this firmware @juppin!
I have Archer c7 v4 already openwrt installed. I am using this as a main router and I suffer from the speed issue discussed before. I would like to try your firmware on my device but I see that there is no support available. I tried to sysupgrade with -F flag over my existing AR71xx installation, and I bricked my device. Luckily, I have enough power user capability to restore it via TFTP.
If you have your github repository for your project, I'd really like to access it to try to compile it for device. If it's not possible, could you please add support for Archer c7 v4 (AC1790)? I can try this firmware. Should something goes wrong, I can easily restore my firmware. I already have snapshot release with openwrt with 4.9.14 kernel.
Thank you!
No im just a user who may help to test builds for dir-505
I'm having trouble setting dnscrypt up. Some issue with libsodium.
Anyone else having this issue (testing on an Archer C7V2)
Error relocating /usr/lib/libsodium.so.23: explicit_bzero: symbol not found
Unbound is crashing also. Something is borked, getting a similar error
Error relocating /usr/lib/libunbound.so.8: getentropy: symbol not found
Error relocating /usr/sbin/unbound: getentropy: symbol not found
I can't install it on my wndr3800... the sysupgrade is an invalid image
@juppin it seems that libc/libgcc are compiled with slightly different flags in trunk. Particularly the HAVE_EXPLICIT_BZERO (a safe memory clear). Could you compile-in libsodium as well next time you do a release?
The relevant code is here: libsodium source
nevermind, I learned, installed fine, setting MTU in LAN to anything except default crashes the firmware on the WNDR3800
EDIT...
flashed stable 18.06.1
resetted everything in the GUI
then copied THIS firmware into the router
and then flashed with only the -F flag
runs SMOOTH
Did you figure this out?
The C library in these builds uses slightly different configuration. It's fine for most packages, but not for libsodium particularly. My guess is that we'd either need juppin to compile these packages together or start using the same build flags as trunk. I might end up building my own firmware, which I did when gwlim first posted the fastpath patches. It's just a bit of a hassle to get everything, but it might be worth it (or not, my connection is not even close to gigabit, so I'm fine without offloading).
1 Like
Building your own firmware is not particularly hard, specially if you are already familiar with Linux. This guide is a little older, but it's a little more complete than the new one.
@juppin, could you share your .config file in your website as well, so those of us who need different packages can just modify it?
3 Likes
@juppin I would like to test it on https://openwrt.org/toh/buffalo/wzr-hp-g300h
It's 9132rev2 but there is not a dts of its own.
I would like also to test it, because it works with kernel 4.4 but not with kernel 4.9 (18.06.1) due to some strange SPI/mtd/jffs2 errors installing packages. Maybe 4.14 it's working fine
thank you
Fabio
But how do I use the normal packages from TRUNK with @juppin 's Ath79 build? I built my own Ath79 for archerC7 v2 but now I cannot use any of the packages.... Also Why isn't the Ath79 the standard build for all of these hardware's at this point. Who can we talk to about making it the standard build for these devices so @juppin doesn't have to support it alone anymore.
The idea is that you should be able to simply use opkg to install the packages. The problem is that some packages like unbound and libsodium use specific functionalities that seem to be missing from juppin's builds (getentropy and explicit_bzero). My guess is that either his compile flags (-nomips16) or simply because we are using a different arch (ath79 instead of ar71xx) cause these functions not to be compiled in.
From what I understand, juppin sets his firmwares to point to his repo for the kernel module packages and for the openwrt snapshots for the other packages. You should be able to do the same by editing the /etc/opkg/distfeeds.conf file.
At least in libsodium's case, explicit_bzero is not necessary for it to work, but since the version from trunk was compiled assuming the function was present, it fails when it doesn't find it. If you compile the firmware
My guess is that ar71xx is considered stable (and well tested) and available for all supported boards, so they are keeping it there. It is also possible they're planning another point release before the next openwrt version (19?), so they'll keep things as they are.
1 Like
Any chance to add WD My Net N750 support? I think it needs to be added to ath79 in general (ar71xx already works)
1 Like
I'd love to get @juppin's firmware support for WD My Net N750 router as well, please. As fair I as know it is very simillar, almost identical to TP-Link WDR4300 it ust has additional 8 MB of FLASH so it has 16MB of flash.
Hello,
I'm running
Firmware Version: OpenWrt SNAPSHOT r7966-01793e8752 / LuCI Master (git-18.232.74480-b93d3f3)
Kernel Version: 4.14.67
on my Archer C7 v2 which should be 2018/08/29 (4.14.67-1-b35fbde0a7eb854da54ccd985ccb2705) build linked as current build in this thread.
Performing a
opkg update && opkg list-upgradable | cut -f 1 -d ' ' | xargs opkg upgrade
via ssh leads to an error while upgrading netifd but successfully upgrades all packages after a second run. But I cannot reach the router via ssh nor via LUCI after a reboot.
Are the symptoms when you do this that it halts seemingly midway through the upgrade process and then after a hard reboot you're unable to SSH or connect via the web interface?
If so, I suspect that the upgrade script that you're using is consuming all the storage space you have on your limited flash. Maybe try the failsafe option to login (https://wiki.openwrt.org/doc/howto/generic.failsafe), clear some packages and then reboot normally to see if that gets it to a workable state again?