Let's use this topic to collect impression and experience about the OpenWrt One. (Or open a separate bug report if that's warranted.) Thanks
First of all I wanna thanks to everyone for openwrt in general and for having now the option to use an openwrt hardware with openwrt software!
I'm really happy about that possibility now!
I got the One router a few days ago and hooked in to my network yesterday.
The first thing I noticed that I couldn't install any software:
Collected errors:
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/packages/Packages.gz, wget returned 8.
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/base/Packages.gz, wget returned 8.
I already did some changes (mainly wan access via ssh and GUI) so I did a backup and installed the newest snapshot ("Keep settings ..." works as well) and was able to install some software.
I guess it's just bad timing to switch to apk yet 
or having a stable version installed (which isn't available yet) on the One router instead of a snapshot for shipping one day.
Is a stable version planned for this or is this little superbox “only” intended for developers?
So far, I haven't done anything else yet but now I'm going to try "this and that".
Again, a big thank you to everyone who made this possible! As you can probably hear from this little text, at least one person is happy
24.10.0-rc2 is currently available. It’s just a short time to full stable.
To expand on @RuralRoots' post...
- OpenWrt One shipped with a snapshot version. Because snapshot versions change frequently (nightly), the corresponding packages may not be available any longer.
- OpenWrt 24.10.0-rc5 is now available from the Firmware Selector
- All OpenWrt kernel packages are built to match that version, and are saved permanently.
- Most ordinary packages are stable and will continue to work with other release candidates. Packages for the final stable release are permanently archived.
The best advice for the "unavailable package" problem is to install the the newest release candidate, or the final stable release when it becomes available. Go to the Firmware Selector and flash the SYSUPGRADE file. It should be safe to keep settings during the installation.
1 Like
First part of the sentence is true, but the second is not fully correct.
Regarding packages' longer term availability:
-
The kernel packages (kmod-xxxxx) in the main repo and selected few target-specific packages are available permanently in https://downloads.openwrt.org/releases/24.10.0-rc2/targets/mediatek/filogic/kmods/ and https://downloads.openwrt.org/releases/24.10.0-rc2/targets/mediatek/filogic/packages/
-
But the normal/ordinary packages on the 24.10 branch are continuously built by the 24.10 phase2 buildbot, so some of the packages of the 24.10.0-rc2 moment have already been replaced by newer versions.
The https://downloads.openwrt.org/releases/24.10.0-rc2/packages/ directory is just a symlink to https://downloads.openwrt.org/releases/packages-24.10/ , as can be seen from https://downloads.openwrt.org/releases/24.10.0-rc2/ . So there is no permanent archive of all rc2 packages.
For OpenWrt One the direct link to normal packages' download directory is https://downloads.openwrt.org/releases/packages-24.10/aarch64_cortex-a53/
Ps. To large extent, most packages are still the same as on the rc2 moment, and can still be installed, but there may be a few, where dependencies have already changed. (there are a few problematic dependency chains like ABIversioned package X --> normal package --> ABI versioned package Y)
1 Like
Ahhh, yes... I see. What I am really seeking is advice for people who have recently purchased an OpenWrt One.
How can they get to a state where they can install additional packages? Can they install the -rc2 firmware then install packages? Or will those packages "drift away" over time so that people can't rely on them working? Thanks.
-rc2 is still the best option, and naturally the final 24.10.0 itsefl once it gets releases.
Like I described above. Some packages will drift away...
But likely at the point when installation would be impossible, e.g. at an annoying ABI change, the rc3 or final release (or a maintenance release afterwards) gets released.
Different question, yet related: Does anybody have recommendations for 2230 and 2242 M.2 ssds, are there meaningful differences (unlike 2280 these seem to be generally rarer)?
I am not looking for ultimate performance, more reliability and lowish price...
1 Like
There isn't much of a technical difference between SSDs in 2230/ 2242 form-factor, due to their size they are generally DRAM-less (which isn't as bad as many reviews claim it to be, even less for this use case). So basically get whatever you can get easier/ cheaper.
Based on my experiences (albeit with SATA SSDs), I would prefer models from name-brand vendors who do have their own production lines of flash chips, but even no-name NVMe/ M.2 SSDs aren't really 'bad' these days anymore - so for this use case, there's little reason to ignore them ('anything' is better than sdhc or USB stick, which take the garbage chips that didn't pass QC for SSDs).
Keep in mind that the M.2 slot of the OpenWrt is 'only' PCIe v2 x1, so high-end SSDs would be a waste - so gen2/ gen3/ gen4 NVMe SSDs are just fine (gen5 just runs hot). PCIe v2 x1 bottlenecks the SSD to 500 MBit/s (as I don't own the OO, I have no idea about the actual throughput (which might also be limited by the SOC's speed)), so roughly (slightly better) than SATA3, any semi-recent NVMe SSD can do that easily.
2 Likes
So... forgive me if this is answered elsewhere, but I couldn't find the answer. Anyway, I see that the OpenWRT One has two ethernet ports, but does that mean that one of them has to be used for the WAN connection from the Modem? Is it possible to actually have two devices (ie my desktop and Home Assistant box) plugged in via Ethernet at the same time?
This is not really on topic for this thread, but.
You have two ethernet ports, which you can configure as you like. Realistically you do want to connect your LAN port to a switch to distribute this further (in the easiest case a cheap unmanaged one, but if you have multiple internal VLANs in mind, it can be sensible to choose a (smart-/ L2-) managed switch instead of an unmanaged one). But if you only use the OO as AP or have an alternative means to connect to the wan side (e.g. 4g/ 5g M.2 modem or wifi uplink), there is no reason not to assign both ethernet ports to a common lan bridge.
The physical number of ethernet ports is clear (1+1), how you assign them is just a policy decision for you to configure as you like/ need it.
3 Likes
AliExpress free shipping HUADISK ~$10USD PCIe3/128GB/128K DRAM works fine for me. Can't buy a USB drive for that.
Never any issue after 10 weeks on the OO.
Openwrt One - Build 004 r28200+5-c857145e03, 11-27-2024 SNAPSHOT
-----------------------------------------------------
root@RuralRoots:~# nvme smart-log /dev/nvme0n1 -vH
latency : 1759 us
Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning : 0
Available Spare[0] : 0
Temp. Threshold[1] : 0
NVM subsystem Reliability[2] : 0
Read-only[3] : 0
Volatile mem. backup failed[4] : 0
Persistent Mem. RO[5] : 0
temperature : 47 °C (320 K)
available_spare : 100%
available_spare_threshold : 10%
percentage_used : 0%
endurance group critical warning summary: 0
Data Units Read : 802 (410.62 MB)
Data Units Written : 14142 (7.24 GB)
host_read_commands : 27257
host_write_commands : 1097488
controller_busy_time : 41
power_cycles : 12
power_on_hours : 842
unsafe_shutdowns : 10
media_errors : 0
num_err_log_entries : 0
Warning Temperature Time : 0
Critical Composite Temperature Time : 0
Temperature Sensor 1 : 47 °C (320 K)
Temperature Sensor 2 : 43 °C (316 K)
Thermal Management T1 Trans Count : 0
Thermal Management T2 Trans Count : 0
Thermal Management T1 Total Time : 0
Thermal Management T2 Total Time : 0
2 Likes
I updated the description. Is this better? Thanks.
1 Like
So, just want to say the USB console is fun!
To elaborate, I have one dumb AP in action, that somehow still operates fully, but stopped responding to SSH or HTTP attempts to access it, with a true console, all I will need to do is lug my laptop to the AP to debug/fix this. (I guess this might be a side effect of me doing "dumb AP" without a receipt, so I might accidentally have configured "way too dumb AP" out of hybris (who needs the howto in the wiki)).
1 Like
So, I am running a local crusader test through my One (all wired), and I see it struggling with bidirectional traffic at 1 Gbps, I see aggregate 1315 Mbps compared to around 925 Mbps for the unidirectional tests, so I would expect something in the 1800 Mbps range.
Part of this might be my low-end USB3 Gigabit ethernet dongle, but looking at htop during the test, the one was doing well above 90% load on both cores during the bidirectional test so was pretty maxed out. This was with firewall/NAT but without PPPoE and without active traffic shaping.
Note, this is not a complaint, I am just trying to figure out its limits...
P.S.: Since IPv6 prefix delegation from my primary router worked out of the box (yeah!) I tried IPv6 on the theory that it might lessen the firewalling load a bit and hence allow more throughput, but alas aggregate throughput was even less.
P.P.S.: I tested with rc2, and just noticed rc4 is out, time to update...
firmware selector does not seem to like my configuration:
Unsupported profile: openwrt_one
could this happen if not all packets are built yet?
P.P.P.S.: Just ran the wireguard benchmark for fun:
OpenWrt One | MT7981B (Filogic 820)
(DualCore ARMv8 A53, 1.3 GHz) | 24.10.0-rc2 | 337Mbps
as expected the dual a53 @1.3 GHz falls a bit short of the dual a9 @1.6 GHz in my turris omnia:
Turris Omnia
(CZ11NIC13, 2016) Marvell Armada 385
(Dual Core ARMv7, 1.6 GHz) 23.05.4 371 Mbps
but not all that much (showing that Arm's claim the a53 approaches a9 performance at lower power consumption might well be true, but we are still talking about a decade old core designs here that IMHO are beginning to show their age...)
P.P.P.P.S: Re ran the wireguard test with OpenWrt 24.10.0 and RPS, RFS and irqbalance enabled:
|OpenWrt One | Mediatek MT7981BA (Dual Core A53, 1.3 GHz) | 24.10.0 | 372Mbps|
a decent improvement mainly by better multicore configuration, but nothing earth shattering either.
Hello everyone,
I'm trying to add a USB drive to my OpenWrt One device, but I'm facing an issue where my device is not recognizing the USB drive. I've tried formatting the drive with both ext4 and FAT32 file systems and have installed the necessary extensions, but it still doesn't work.
Has anyone else encountered a similar problem? Or can anyone offer some advice on how to resolve this issue?
Thank you in advance for your help!
Have you followed the https://openwrt.org/docs/guide-user/storage/usb-drives-quickstart wiki?
1 Like
Hi everyone,
as there was some nvme discussion, I might as well ask here:
I'm trying to add a 2242 M2 (transcend TS128GMTS400S) to my OpenWrt One (24.10.0-rc4)
regardless if the disk is inserted or not, dmesg output remains exactly the same:
[ 0.076930] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
[ 0.076960] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[ 0.076975] mtk-pcie-gen3 11280000.pcie: MEM 0x0020000000..0x002fffffff -> 0x0020000000
[ 3.273917] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
[ 3.281289] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[ 3.287562] mtk-pcie-gen3 11280000.pcie: MEM 0x0020000000..0x002fffffff -> 0x0020000000
[ 3.629488] mtk-pcie-gen3 11280000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[ 3.638315] mtk-pcie-gen3: probe of 11280000.pcie failed with error -110
I was able to confirm the nvme works in another device, however i dont have a different nvme with that form factor to crosscheck.
Is this output expected when the nvme is not recognized?
Thanks for any hints!
Not sure whether it helps, but here are the relevant lines from my dmesg (rc04):
[ 3.268574] phy phy-soc:usb-phy@11e10000.1: type_sw - reg 0x218, index 0
[ 3.276218] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
[ 3.283584] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[ 3.289869] mtk-pcie-gen3 11280000.pcie: MEM 0x0020000000..0x002fffffff -> 0x0020000000
[ 3.560042] mtk-pcie-gen3 11280000.pcie: set MEM trans window[0]: cpu_addr = 0x20000000, pci_addr = 0x20000000, size = 0x10000000
[ 3.572065] mtk-pcie-gen3 11280000.pcie: PCI host bridge to bus 0000:00
[ 3.578680] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 3.584178] pci_bus 0000:00: root bus resource [mem 0x20000000-0x2fffffff]
[ 3.591049] pci_bus 0000:00: scanning bus
[ 3.595074] pci 0000:00:00.0: [14c3:1f32] type 01 class 0x060400
[ 3.601096] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit]
[ 3.607931] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 3.614026] pci 0000:00:00.0: PME# disabled
[ 3.619402] pci_bus 0000:00: fixups for bus
[ 3.623608] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 0
[ 3.630306] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 3.638303] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 1
[ 3.645097] pci_bus 0000:01: scanning bus
[ 3.649133] pci 0000:01:00.0: [144d:a80b] type 00 class 0x010802
[ 3.655172] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[ 3.662144] pci 0000:01:00.0: PME# supported from D0 D3hot
[ 3.667622] pci 0000:01:00.0: PME# disabled
[ 3.671853] pci 0000:01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 63.012 Gb/s with 16.0 GT/s PCIe x4 link)
[ 3.709517] pci_bus 0000:01: fixups for bus
[ 3.713700] pci_bus 0000:01: bus scan returning with max=01
[ 3.719261] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 3.725880] pci_bus 0000:00: bus scan returning with max=01
[ 3.731477] pci 0000:00:00.0: BAR 8: assigned [mem 0x20000000-0x200fffff]
[ 3.738256] pci 0000:00:00.0: BAR 0: assigned [mem 0x20100000-0x20107fff 64bit]
[ 3.745568] pci 0000:01:00.0: BAR 0: assigned [mem 0x20000000-0x20003fff 64bit]
[ 3.752882] pci 0000:00:00.0: PCI bridge to [bus 01]
[ 3.757838] pci 0000:00:00.0: bridge window [mem 0x20000000-0x200fffff]
[ 3.764790] pcieport 0000:00:00.0: assign IRQ: got 84
[ 3.769853] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[ 3.775946] pcieport 0000:00:00.0: enabling bus mastering
[ 3.781969] mtk-pcie-gen3 11280000.pcie: msi#0x0 address_hi 0x0 address_lo 0x11280c00 data 0
[ 3.790414] mtk-pcie-gen3 11280000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11280c00 data 1
[ 3.798839] mtk-pcie-gen3 11280000.pcie: msi#0x2 address_hi 0x0 address_lo 0x11280c00 data 2
[ 3.807270] mtk-pcie-gen3 11280000.pcie: msi#0x3 address_hi 0x0 address_lo 0x11280c00 data 3
[ 3.815700] mtk-pcie-gen3 11280000.pcie: msi#0x4 address_hi 0x0 address_lo 0x11280c00 data 4
[ 3.824130] mtk-pcie-gen3 11280000.pcie: msi#0x5 address_hi 0x0 address_lo 0x11280c00 data 5
[ 3.832564] mtk-pcie-gen3 11280000.pcie: msi#0x6 address_hi 0x0 address_lo 0x11280c00 data 6
[ 3.840995] mtk-pcie-gen3 11280000.pcie: msi#0x7 address_hi 0x0 address_lo 0x11280c00 data 7
[ 3.849418] mtk-pcie-gen3 11280000.pcie: msi#0x8 address_hi 0x0 address_lo 0x11280c00 data 8
[ 3.857848] mtk-pcie-gen3 11280000.pcie: msi#0x9 address_hi 0x0 address_lo 0x11280c00 data 9
[ 3.866277] mtk-pcie-gen3 11280000.pcie: msi#0xa address_hi 0x0 address_lo 0x11280c00 data 10
[ 3.874794] mtk-pcie-gen3 11280000.pcie: msi#0xb address_hi 0x0 address_lo 0x11280c00 data 11
[ 3.883310] mtk-pcie-gen3 11280000.pcie: msi#0xc address_hi 0x0 address_lo 0x11280c00 data 12
[ 3.891829] mtk-pcie-gen3 11280000.pcie: msi#0xd address_hi 0x0 address_lo 0x11280c00 data 13
[ 3.900346] mtk-pcie-gen3 11280000.pcie: msi#0xe address_hi 0x0 address_lo 0x11280c00 data 14
[ 3.908857] mtk-pcie-gen3 11280000.pcie: msi#0xf address_hi 0x0 address_lo 0x11280c00 data 15
[ 3.917373] mtk-pcie-gen3 11280000.pcie: msi#0x10 address_hi 0x0 address_lo 0x11280c00 data 16
[ 3.925976] mtk-pcie-gen3 11280000.pcie: msi#0x11 address_hi 0x0 address_lo 0x11280c00 data 17
[ 3.934580] mtk-pcie-gen3 11280000.pcie: msi#0x12 address_hi 0x0 address_lo 0x11280c00 data 18
[ 3.943182] mtk-pcie-gen3 11280000.pcie: msi#0x13 address_hi 0x0 address_lo 0x11280c00 data 19
[ 3.951789] mtk-pcie-gen3 11280000.pcie: msi#0x14 address_hi 0x0 address_lo 0x11280c00 data 20
[ 3.960393] mtk-pcie-gen3 11280000.pcie: msi#0x15 address_hi 0x0 address_lo 0x11280c00 data 21
[ 3.968990] mtk-pcie-gen3 11280000.pcie: msi#0x16 address_hi 0x0 address_lo 0x11280c00 data 22
[ 3.977593] mtk-pcie-gen3 11280000.pcie: msi#0x17 address_hi 0x0 address_lo 0x11280c00 data 23
[ 3.986196] mtk-pcie-gen3 11280000.pcie: msi#0x18 address_hi 0x0 address_lo 0x11280c00 data 24
[ 3.994799] mtk-pcie-gen3 11280000.pcie: msi#0x19 address_hi 0x0 address_lo 0x11280c00 data 25
[ 4.003402] mtk-pcie-gen3 11280000.pcie: msi#0x1a address_hi 0x0 address_lo 0x11280c00 data 26
[ 4.012009] mtk-pcie-gen3 11280000.pcie: msi#0x1b address_hi 0x0 address_lo 0x11280c00 data 27
[ 4.020612] mtk-pcie-gen3 11280000.pcie: msi#0x1c address_hi 0x0 address_lo 0x11280c00 data 28
[ 4.029211] mtk-pcie-gen3 11280000.pcie: msi#0x1d address_hi 0x0 address_lo 0x11280c00 data 29
[ 4.037814] mtk-pcie-gen3 11280000.pcie: msi#0x1e address_hi 0x0 address_lo 0x11280c00 data 30
[ 4.046417] mtk-pcie-gen3 11280000.pcie: msi#0x1f address_hi 0x0 address_lo 0x11280c00 data 31
[ 4.055778] mtk-pcie-gen3 11280000.pcie: msi#0x0 address_hi 0x0 address_lo 0x11280c00 data 0
[ 4.064386] pcieport 0000:00:00.0: PME: Signaling with IRQ 85
[ 4.070496] pcieport 0000:00:00.0: AER: enabled with IRQ 85
[ 4.076197] pcieport 0000:00:00.0: save config 0x00: 0x1f3214c3
[ 4.082148] pcieport 0000:00:00.0: save config 0x04: 0x00100406
[ 4.088059] pcieport 0000:00:00.0: save config 0x08: 0x06040001
[ 4.093982] pcieport 0000:00:00.0: save config 0x0c: 0x00010000
[ 4.099901] pcieport 0000:00:00.0: save config 0x10: 0x20100004
[ 4.105809] pcieport 0000:00:00.0: save config 0x14: 0x00000000
[ 4.111722] pcieport 0000:00:00.0: save config 0x18: 0x00010100
[ 4.117630] pcieport 0000:00:00.0: save config 0x1c: 0x000001f1
[ 4.123544] pcieport 0000:00:00.0: save config 0x20: 0x20002000
[ 4.129457] pcieport 0000:00:00.0: save config 0x24: 0x0001fff1
[ 4.135365] pcieport 0000:00:00.0: save config 0x28: 0x00000000
[ 4.141277] pcieport 0000:00:00.0: save config 0x2c: 0x00000000
[ 4.147184] pcieport 0000:00:00.0: save config 0x30: 0x00000000
[ 4.153096] pcieport 0000:00:00.0: save config 0x34: 0x00000080
[ 4.159003] pcieport 0000:00:00.0: save config 0x38: 0x00000000
[ 4.164919] pcieport 0000:00:00.0: save config 0x3c: 0x00020154
[...]
[ 7.435986] nvme 0000:01:00.0: assign IRQ: got 84
[ 7.440934] nvme nvme0: pci function 0000:01:00.0
[ 7.445646] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[ 7.451445] nvme 0000:01:00.0: enabling bus mastering
[ 7.456602] mtk-pcie-gen3 11280000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11280c00 data 1
[ 7.465095] nvme 0000:01:00.0: save config 0x00: 0xa80b144d
[ 7.470678] nvme 0000:01:00.0: save config 0x04: 0x00100406
[ 7.476240] nvme 0000:01:00.0: save config 0x08: 0x01080202
[ 7.481810] nvme 0000:01:00.0: save config 0x0c: 0x00000000
[ 7.487371] nvme 0000:01:00.0: save config 0x10: 0x20000004
[ 7.492938] nvme 0000:01:00.0: save config 0x14: 0x00000000
[ 7.498499] nvme 0000:01:00.0: save config 0x18: 0x00000000
[ 7.504073] nvme 0000:01:00.0: save config 0x1c: 0x00000000
[ 7.509641] nvme 0000:01:00.0: save config 0x20: 0x00000000
[ 7.515203] nvme 0000:01:00.0: save config 0x24: 0x00000000
[ 7.520769] nvme 0000:01:00.0: save config 0x28: 0x00000000
[ 7.526331] nvme 0000:01:00.0: save config 0x2c: 0xa80b144d
[ 7.531897] nvme 0000:01:00.0: save config 0x30: 0x00000000
[ 7.537458] nvme 0000:01:00.0: save config 0x34: 0x00000040
[ 7.543025] nvme 0000:01:00.0: save config 0x38: 0x00000000
[ 7.548587] nvme 0000:01:00.0: save config 0x3c: 0x00000154
[ 7.556619] nvme nvme0: Shutdown timeout set to 8 seconds
[...]
[ 7.606792] nvme nvme0: allocated 64 MiB host memory buffer.
[ 7.615396] mtk-pcie-gen3 11280000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11280c00 data 1
[ 7.623886] mtk-pcie-gen3 11280000.pcie: msi#0x2 address_hi 0x0 address_lo 0x11280c00 data 2
[ 7.632353] mtk-pcie-gen3 11280000.pcie: msi#0x3 address_hi 0x0 address_lo 0x11280c00 data 3
[ 7.641075] nvme nvme0: 2/0/0 default/read/poll queues
[ 7.652326] nvme nvme0: Ignoring bogus Namespace Identifiers
[ 7.664806] nvme0n1: p1
That appears to be a SATA device not PCIe...