Yea you can just ssh into the router after the install and paste something like this and you'll have almost everything. This is what I use:
opkg update && opkg install luci irqbalance luci-app-advanced-reboot luci-app-sqm luci-app-adblock luci-app-upnp luci-app-samba4 kmod-usb-storage kmod-usb-storage-uas kmod-usb-ohci kmod-usb-ohci-pci kmod-ata-ahci kmod-usb-uhci kmod-usb3 block-mount usbutils mount-utils luci-app-hd-idle kmod-fs-exfat iperf3 nano
All you really need is luci to get luci up and running, the rest are absolutely not required - though luci-app-advanced-reboot is probably useful
I also took the plunge with the latest master snapshot (OpenWrt SNAPSHOT r17756) on the WRT1900ACSv2 trying to fix a DSA multiple network bridge setup (didn't fix, but got a work-around using VLANs). Took me a second to figure out that I needed to install luci over ssh. But I agree everything seems to be working so far. Have not tested my OpenVPN setup and finished configuring my Samba4. A project for another day.
opkg update && opkg install luci irqbalance luci-app-advanced-reboot luci-app-sqm luci-app-samba4 block-mount kmod-usb-storage kmod-usb-storage-uas kmod-usb-ohci kmod-usb-ohci-pci luci-app-hd-idle kmod-usb3 kmod-fs-ext4 nano openvpn-openssl luci-app-openvpn luci-app-statistics luci-app-adblock luci-app-ddns luci-app-wol
Run above twice to complete install
echo "0" >> /sys/kernel/debug/ieee80211/phy0/mwlwifi/tx_amsdu
echo "0" >> /sys/kernel/debug/ieee80211/phy1/mwlwifi/tx_amsdu
And for what it's worth, I am getting substantially faster 5GHz performance with my laptop. Same patch required.
I upgraded my Buffalo WBMR-HP-G300H today, from 19.07.6, kept the settings. The upgrade itself was smooth, it even retained the custom ADSL firmware that I have to use (the stock one does not connect at all on my noisy line). I was presented by a few prompts about the required configuration changes, accepted them, and... it just works.
My custom script for re-installing previous packages also worked flawlessly.
However, there is one bad news. The curl and ddns-scripts packages are in a sorry state. The default installation includes uclient-fetch which does pretend to be a "wget", and is installed if I run opkg install wget. However, ddns-scripts still complain that neither wget nor curl is installed. OK, so I installed curl. I also have both ca-certificates and ca-bundle (yes I know that work is underway to eliminate the duplication). Result: ddns-scripts now try to use curl, and fail, because SSL support in curl does not really work.
To reproduce the curl problem:
root@Buffalo:~# curl https://google.com/
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="https://www.google.com/">here</A>.
</BODY></HTML>
root@Buffalo:~# curl https://ya.ru/
curl: (77) CA signer not available for verification
root@Buffalo:~# curl https://dynv6.com/
curl: (77) CA signer not available for verification
I installed wget-ssl, and it is able to validate these certificates:
root@Buffalo:~# wget --spider --max-redirect=0 --content-on-error https://google.com/
Spider mode enabled. Check if remote file exists.
--2021-10-17 10:39:35-- https://google.com/
Resolving google.com... 2a00:1450:4010:c06::66, 2a00:1450:4010:c06::8a, 2a00:1450:4010:c06::65, ...
Connecting to google.com|2a00:1450:4010:c06::66|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.google.com/ [following]
0 redirections exceeded.
root@Buffalo:~# wget --spider --max-redirect=0 --content-on-error https://ya.ru/
Spider mode enabled. Check if remote file exists.
--2021-10-17 10:39:54-- https://ya.ru/
Resolving ya.ru... 2a02:6b8::2:242, 87.250.250.242
Connecting to ya.ru|2a02:6b8::2:242|:443... connected.
HTTP request sent, awaiting response... 200 Ok
Length: 60835 (59K) [text/html]
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.
root@Buffalo:~# wget --spider --max-redirect=0 --content-on-error https://dynv6.com/
Spider mode enabled. Check if remote file exists.
--2021-10-17 10:40:08-- https://dynv6.com/
Resolving dynv6.com... 2a01:4f8:1c1c:4c96::, 2a01:4f9:c010:95b::, 2a03:4000:6:569::, ...
Connecting to dynv6.com|2a01:4f8:1c1c:4c96::|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.
You have to install "wget-ssl" for "ddns" to work. Curl currently fails due to some issue with SSL certificate included in OpenWRT installation and the wolfssl library to which curl is linked to. Looks like curl linked to openssl (instead of wolfssl) does not have this issue, but there's no curl-openssl package available in the repos.
Upgrade an Netgear Nighthawk X4S R7800 from 19.01 to 21.02 and everything worked like a charm.
Thank you to everyone who supported this great work!
See details her:
After almost 2months of upgrades after the 21.02.0 release.
Do anyone know if there is a general roundup 21.02.1 release planned soon?
Is there a way to run the migration script after restoring 19.07 settings?
I have a TP-Link WDR3600 with an extroot. I normally upgrade this by:
But it seems doing this will not be possible due to the changes in the UCI syntax.
Are there any recommendations for upgrading for extroot users?
Two ideas for you.
50-dnsmasq-migrate-resolv-conf-auto.sh from /rom/etc/uci-defaults back to /etc/uci-defaults, so that it will be again run at the next boot. After that your could restore the old 19.07 settings and reboot.Just watched shortlog for 21.02.1.
Can anyone explain why 21.02.1 not use Kernel 5.10 as default, but 5.4? It's just doesn't make a sense, every 5.10 related post on this forum about how good it work..
My opinion not use 5.10 as default ASAP was a major mistake for a whole OpenWrt project, mark my words.
And don't tell me anyone who want can use snapshot, anyone who want can build OpenWrt with any kernel he want, we talk about project..
According to the Wiki, even now most targets in master are not on 5.10 yet, so switching to 5.10 in 21.01.1 means dropping most targets, or involves a lot of work.
No. The target specific patches don't fit on just any kernel.
If you browse the snapshot files, you'll see that only a few targets have moved to 5.10 kernel. It is not ready yet for general purpose, a lot of work is still needed. I'm not even sure that every targets can be ported to 5.10 kernel, so some may be deprecated in future.
Let's assume that the port to 5.10 will be a goal for the next major release. Hence next 21.02 service releases will likely still use the 5.4 kernel.
Ho ? that was the document I was looking for !
21.02 has been branched off from master in February 2021. It reflects mainly that status. There have been later backports of some features & packages into 21.02, but the major kernel version will not be upgraded into the stable release branch. 21.02.1 is simply the head of that Feb 2021 branch, not the current master.
All 21.02.x maintenance releases will still use the current 5.4 kernel.
Master has roughly half of the targets upgraded to 5.10, so likely the next release 22.0x will have 5.10 as the default. (And the targets with no working 5.10 will be dropped. This is a community effort... Somebody needs to author and test the kernel bumps with the necessary modifications to the target-specific 50-100 patches for each target.)
But 5.10 works so smooth on my mediatek and x86 devices.. i didn't felt such a improvement even with transit from 4.14 to 5.4!
Then just use master snapshots and be done with it. openwrt-21.02 will remain on the 5.4 lts kernels for the remainders of its life cycle.
But, does it work as smoothly for everybody's else devices...? A new kernel requires extensive testing on all platforms.
Anyone know why 21.02.1 disappeared from the main page?
AFAIK, the release hasn't officially landed yet. It's almost there, but the build-bots may still be working to compile all the images and packages. If you look, you'll see that the downloads are available, but the link from the main page has not yet been added.
