307 redirects have been created, in order to provide a consistent link scheme for the devicepages.
Please let me know when a link that has been created according the scheme does not work, I will then adjust the redirect accordingly.
307 redirects have been created, in order to provide a consistent link scheme for the devicepages.
Please let me know when a link that has been created according the scheme does not work, I will then adjust the redirect accordingly.
Thank you for the effort, but most links still seem to be non-existent. E.g. https://openwrt.org/toh/tplink/tplink_tl-wr841n-v13
tp-link
, not tplink
, see https://www.tp-link.com/
In order to converge quicker, can you please create a CSV list with the following information and send it to me?
brand;model;version;expected devicepage URL
It's not possible to upload CSV files in the forum, maybe that could be allowed somehow. Meanwhile does this help? https://share.riseup.net/#IEv7ID5IwQL5N-0JNDPmcw
1&1;HomeServer;;avm_fritz7320
7Links;PX-4885;8M;7links_px-4885-8m
8devices;Carambola2;;8dev_carambola2
8devices;Carambola;;8devices_carambola
8devices;Habanero DVK;;8dev_habanero-dvk
8devices;Jalapeno;;8dev_jalapeno
8devices;Lima;;8dev_lima
8devices;Rambutan;;8dev_rambutan
Accton;WR6202;;accton_wr6202
Actiontec;R1000H;;actiontec_r1000h
Actiontec;R1000H;;actiontec_r1000h
ADB;P.DG A4001N1;;adb_a4001n1
ADB;P.DG A4001N1;;adb_a4001n1
ADB;P.DG A4001N A-000-1A1-AX;;adb_pdg-a4001n-a-000-1a1-ax
ADB;P.DG A4001N A-000-1A1-AX;;adb_pdg-a4001n-a-000-1a1-ax
ADB;P.DG A4001N;;adb_a4001n
ADB;P.DG A4001N;;adb_a4001n
ADB;P.DG A4101N A-000-1A1-AE;;adb_pdg-a4101n-a-000-1a1-ae
ADB;P.DG A4101N A-000-1A1-AE;;adb_pdg-a4101n-a-000-1a1-ae
ADB;P.DG AV4202N;;adb_av4202n
ADB;P.DG AV4202N;;adb_av4202n
ADSLR;G7;;adslr_g7
Adtran/Bluesocket;BSAP-1800;v2;adtran_bsap1800-v2
Adtran/Bluesocket;BSAP-1840;;adtran_bsap1840
Aerohive;HiveAP 121;;aerohive_hiveap-121
Aerohive;HiveAP-330;;aerohive_hiveap-330
AFOUNDRY;EW1200;;afoundry_ew1200
Aigale;Ai-BR100;;aigale_ai-br100
AirTight Networks;C-75;;airtight_c-75
Akitio;MyCloud Mini;;akitio_mycloud
Alcatel;RG100A;;alcatel_rg100a
Alcatel;RG100A;;alcatel_rg100a
ALFA Network;AC1200RM;;alfa-network_ac1200rm
[...]
hi @aparcar, I have already send a list by email. I think @tmomas likes to use the vendor and model name in the link. But the problem is, vendor names and device name spellings have changed a lot during the latest releases to make it more consistent. And this effort is still ongoing.
Imho, we should use target and device id to reduce the amount of URL aliases for a device. But for everyone reading the URL this will look a bit funny. And of course in same (rare) instances the device id has been changed.
@tmomas what do you think?
Ooops, I was of the opinion that something like toh/brand/model_version
was expected.
Example:
https://openwrt.org/toh/8devices/carambola
https://openwrt.org/toh/8devices/carambola2
Can you change your expected devicepage URL according to that toh/brand/model_version
scheme and create a CSV again?
Hmm... when was that? I've got nothing in my inbox or spam folder...
i'm loving the ability to customize. i find it much faster than having to download the imagebuilder into ubuntu. brilliant.
When a router is selected, really like the included/corresponding Info: link.
Quicker to access ToH page for the device.
@wireless thanks a lot: https://gitlab.com/openwrt/web/firmware-selector-openwrt-org/-/merge_requests/52
Well done on the new page, it's slick and pretty easy to navigate.
One small gripe however, which is something that really isn't specific to this page or even the OpenWrt project in general, is that the digest / hash sum is served on the same page, which is not idea: if someone had managed to compromise the binary sysupgrade file, they likely also could replace the sha sum.
One thing that could be neat to consider here is to use sigstore, which will provide a public third party transparency ledger to store these hashes / signatures and make it easy to sign this sort of stuff.
Full disclosure, i currently work on sigstore for my employer, but i genuinely think it could be cool to have the hashes of OpenWrt releases recorded on a publicly verifiable log, as it would make compromising them a lot harder. Happy to discuss tihs some more if anyone is interested!
https://openwrt.org/docs/guide-user/security/release_signatures
The security system with sha256 is actually dual function that the firmware selector kind of short circuit.
The security idea is to verify the sha256 file in the first place but to do that you need to go to the download page to get the files required, but then you donβt really need the firmware selector since you have found the files to download anyway.
But after Solarwind this kind of cyber threat is something to think about.
It is great the possibility to choose packages, would it be possible to add 18.06.9
branch? thanks
18.06 is end-of-life.
As @flygarn12 already mentioned, 18.06.9 is end of life and does not receive any support.
There is a merge request for this, but it is probably never going to be merged: https://gitlab.com/openwrt/web/firmware-selector-openwrt-org/-/merge_requests/14
I have added 18.06.9 to my selector setup: https://mwarning.github.io/openwrt-firmware-selector/www/, but not all devices are included, due to missing json output support of the build system.
Many thanks to your quick effort.
I thought it might help old devices owner to select only needed packages hence fit the firmware in low flash size.
21.02.0-rc2 is missing for Xiaomi Mi Router 4A Gigabit Edition even though the files are available here:
https://downloads.openwrt.org/releases/21.02.0-rc2/targets/ramips/mt7621/openwrt-21.02.0-rc2-ramips-mt7621-xiaomi_mi-router-4a-gigabit-initramfs-kernel.bin
https://downloads.openwrt.org/releases/21.02.0-rc2/targets/ramips/mt7621/openwrt-21.02.0-rc2-ramips-mt7621-xiaomi_mi-router-4a-gigabit-squashfs-sysupgrade.bin
rc2 is not even announced, so please be patient.
I have always used https://chef.libremesh.org/ to build custom firmware image for my Raspberry Pi 4B with usb-ethernet adapter driver included. However I do not see 21.02.0-rc2 option in https://chef.libremesh.org/ . I see the option in https://firmware-selector.openwrt.org though. Are both these websites managed by the same person/team? Can someone please enable 21.02-0-rc2 option in https://chef.libremesh.org/ ? Thanks in advance.
Patience