Another thought for OpenWrt/CeroWrt II: No-Configuration Networking
I desperately want to make it easy for a newcomer to install and configure OpenWrt. But it's still too hard - lots of little bumps in the road decrease the probability of success. It's getting better, but there remains the all-or-nothing dance on the tightrope - replacing or flashing your ISP's equipment.
So I want to focus on the use case where someone buys a new router for OpenWrt and plugs it into their ISP's gear. (Yes, they'd have double-NAT. But lots of people have double-NAT already, and it works fine for the vast majority of situations.)
This makes the instructions simple: First go to the Table of Hardware and select a suitable router. (Or have recommendations for modest price devices that work fine.)
Then go to a (single) page on the OpenWrt wiki that basically says: Use an Ethernet to connect your new router. Flash it with the OpenWrt "factory" image (from https://firmware-selector.openwrt.org). Enable Wi-Fi. Connect the new router's WAN port to the ISP gear, and browse to 192.168.1.1...
OH DRAT! What if the ISP gear is using 192.168.1.0/24? Why do we tell people to use 192.168.1.1, anyway? (It's the 21st century...) Could we simply use a mDNS name instead? Can't we make this simpler?
Here's my desire:
a) The router could use a default algorithm to assign its LAN interface address to be from a different subnet from the ISP gear.
b) OpenWrt can then use mDNS naming for its LuCI interface. We tell people: Just type OpenWrt.lan in your browser (or ssh root@OpenWrt.lan)
c) Newcomers are on the air! Profit!
Does a facility already exist that would accomplish this? Could it be incorporated into the default behavior? Thanks.