Hi.
I have Redmi AX6S and newly installed (reinstalled) OpenWRT 23.05. After adding a Wireguard connection with "Bring on boot" on the router does not boot anymore. Instead it goes to a reboot cycle: orange LED, then short blue blink, then the LEDs turn off, and then it cycles again forever.
I tried to reboot with "Bring on boot" set to off. It boots. After I set "Bring on boot" to on, the router does not boot anymore, and I have to unbrick it. Please help.
Failsafe does not work, it reboots too early. It even does not bring wired interfaces on. Only debricking through installing stock firmware and then reinstalling OpenWRT works.
Anyway I know how to debrick it. I want to add a Wireguard connection on boot, but this bricks the router.
By the way, Wireguard worked for a month, then I cycled the router, and it did not boot anymore. After investigations I've come to an assumption that Wireguard set with "bring on boot" on does not allow router to boot anymore.
This is very important. OpenWRT does not boot after adding a VPN interface. This is critical
You probably have a typo or other element in one of your config files that is invalid.
Try failsafe again. Typically, you start pressing a button (often wps, sometimes a reset button) repeatedly immediately upon applying power until you see a rapidly flashing led.
There are no other reports about this, as far as I am aware. So I highly doubt this is a universal issue.
Can you tell us exactly what you did (every step) as you were installing the vpn?
Blockquote
Can you tell us exactly what you did (every step) as you were installing the vpn?
Just imported the wireguard.conf file and reboot. Nothing else. Clean install. That's why it is important. The router should boot even if a VPN config is not good. Now the router reboots in cycle, and I have no access to it serial console.
Blockquote
You probably have a typo
A typo shouldn't reboot my router in cycle. The .conf file I'm loading is from PiVPN, anyway it's just a config file. For now I'm sure that "on boot" is the only thing that causes my router nt to boot anymore.
If there is invalid syntax, it could choke when the file is parsed, leading to a reboot and boot loop.
Importing a config file is usually the last step.
What did you do, start to finish?
Last step to killing the router is setting "bring on boot". Before this, I've jist imported Wireguard VPN file. Clean install. Only "bring on boot" kills my router and causes it to reboot in cycle forever.
Wireguard under OpenWrt does not use .conf files. OpenWrt integrates Wireguard into its UCI configuration system. A wireguard interface should be instantiated by declaring an interface of proto wireguard in /etc/config/network. Convert the setup in the VPN provider's .conf file to UCI statements.
Blockquote
What did you do, start to finish?
I have reinstalled OpenWRT. Installed wireguard-luci and all dependencies. It's ok. When I add a connection, it does not boot EARLY.
It's lucy. I've added the interface, and the router does not boot anymore after adding the WG.
I do not agree. OpenWRT still should boot even with false WG. It does not boot, and the trigger is — for sure — a WG connection
What happens if you manually configure the interface?
Have not tried yet. What should I try? I have imported wg111111.conf.
Don't import the config. Add the details from it manually.
Anyway, whatever I add to intefaces, the router still have to boot.
Before going any further....
let's see your current config:
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
My config is basic after a reinstall. Ok I try to follow you
Can you share the config as it is right now?
It's basic. Now I'm try to gather it.