Building Firmware For WDR6500 v2

Community Builds, Projects & Packages
1

i have been trying to build a custom firmware for TL-WDR6500 V2 (CN) the cpu is Qualcomm Atheros QCA9561, but after i checkout the version i want to build which is v22.03.5 because i intend to use fw3 rules, i selected

Target System → Atheros ATH79
Subtarget→ Generic

but cannot find the wdr6500 profile, please any help on how to build this profile.

2

just so that you don't have any misunderstandings...

  1. 22.03 is EOL and unsupported. It is possible somebody will be able/willing to help, but don't get your hopes up because of the fact that it went officially EOL a year ago.
  2. 22.03 contains known security vulnerabilities that will never be patched (and maybe others yet to be discovered/disclosed). The only way to remain secure is to use a supported release version.
  3. sticking to fw3 is probably not the best plan, given that you'll need to perpetually remain on an old and unsupported version of OpenWrt. It is advisable to update your rules to fw4. (also, fwiw, if your rules are in the higher level UCI constructs, little or no special migrations are required since the UCI level environment essentially abstracts the underlying firewall rules).
3

the profile is still not in v24.10.1, but there is openwrt firmware built for it already in the toh page

4

Also am running a service for so many devices and my service runs well on openwrt 18 for wr841n v9, v10 and i just want to change my router model for new customers to the wdr6500, we already have a predefined firewall rules this is why we needed to build this version, thank you for any help you can render.

5

This is even worse. If you are deploying these to customers, you are putting them at significant risk.

6

so what your professional advice? build 24.10.0 and migrate to fw4

7

Yes. But you might not even need to build the firmware - it is already available via the firmware selector.

8

the reason we build the firmware is because we have configuration files we make for the service to run, so even if the user resets the router the configuration is not wiped.

9

Oh. In that case you can customize your images with the firmware selector or the image builder on your computer. You do not need to build from source.

10

the firmware selector only support uci-defaults scripts, we have multiple shell scripts that runs using cronjobs, like there is a script that run every 5 mins to validate the router on our server and another one that connect the router to the closest server etc.

11

Ok. Than the image builder on your computer will do the trick. You can include arbitrary files and configuration.