| ▲ | emilburzo 4 hours ago |
| Or, buy a TP-Link router and flash it with OpenWrt. Best of both worlds. |
|
| ▲ | alias_neo 7 minutes ago | parent | next [-] |
| I did that once or twice, but I got fed up of finding the correct hardware revision of a particular router that supports OpenWRT, and I much prefer OPNSense anyway, and it runs on commodity hardware that you have full control over. |
|
| ▲ | xattt 2 hours ago | parent | prev [-] |
| Then every upgrade flash becomes an ass-clenching experience. I’ve been down this path. It’s a lifestyle choice… until you’re up at 3 AM rebuilding everything because you bricked your AP by flashing openwrt-24.10.0-ath79-generic-tplink_archer-c7-v2-squashfs-factory-FOR-C7-V5-EU-NOT-V2-US.bin and not openwrt-24.10.0-ath79-generic-tplink_archer-c7-v2-squashfs-sysupgrade.bin. |
| |
| ▲ | ac29 2 hours ago | parent | next [-] | | There is a one click update in the WebUI now, no need to flash random bins | |
| ▲ | emilburzo 2 hours ago | parent | prev [-] | | I mean, these days you can just let Claude do it if you don't care for such minutiae... I was skeptical, but it got it done perfectly. It also discovered my fast roaming settings were incompletely setup and that I was using a 5GHz channel that needed 60s to turn on due to regulations (DFS channels). | | |
| ▲ | smallerize 14 minutes ago | parent [-] | | I'm at a loss why you would put a random number generator in front of such a sensitive operation. It's literally a matter of time before the output sampler chooses a somewhat-less-probable string like the one xatt posted. Or just deletes your stuff. | | |
| ▲ | emilburzo 3 minutes ago | parent [-] | | Because I've done it a million times and wanted to see what the "random number generator" is capable of? Because I have config backups/know how to unbrick? You should try it, you might be surprised how thorough it is. It certainly checked more things pre/during/post-upgrade than I did to make sure everything goes smoothly. And definitely more than xattt, apparently ;) |
|
|
|