But I'd make sure internet is accessible (using its wifi) though it, with the ethernet port configured as WAN. Then start the wireguard setup, then there's only one source of error, instead of two.
Remember to use a different subnet on the 802ACs LAN, than on the rest of your network.
No luck, unfortunately. When I delete the LAN interface I can't login even though the wifi was OK before deletion.192.168.1.1 just gives me the livebox interface not luci. I originally reset the LAN IpV4 to 192.168.1.2 to avoid this conflict but I presume this was deleted along with the LAN interface. Is it possible to somehow set the WAN to 192.168.1.2?
OK. Here's what I've done:
1 Reflashed the openwrt rom.
2 Executed your SSH .
3 Opened openwrt on 192.168.10.1 and turned on wifi etc.
4 Connected TL-WR902AC to livebox and checked wifi which is OK.
I can open openwrt with a wired connection but when I type 192.168.10.1 in my browser with just wifi I get the message: "This site canβt be reached 192.168.10.1 refused to connect."
I haven't changed anything else (ie tried to delete the LAN etc)
Only reason for it to happen, would be if you're connected to the wrong wifi.
Assuming the 902ACs wifi's up and running, and you can connect to it, it should work.
if your 902AC wifi have the same SSID and pass as the working one, your computer (at least in windows) will disconnect from 902s wifi, because there's no internet access, and connect to the other one.
a way to test it, is obviously to try to access your other router at 192.168.1.1, while connected.
I've changed the password on the 902AC - it was the same!. It still won't connect on wifi, though. However the Livebox on 192.168.1.1 comes up while connected to Openwrt wifi.
then it probably connects, disconnect, and swaps over to your other wifi.
would be better if you changed the SSID altogether, so you know where you're connected.
you'd want that for your firestick and TV anyway, otherwise you won't know where they connect.
disable the main wifi, or force the computer to forget it.
sorry, but this is an os issue, not really openwrt.