Hello, I just tried to switch from latest asus firmware to MerlinWRT on my RT-ac86u - mainly because of wireguard and entware.
I followed this: https://github.com/RMerl/asuswrt-merlin.ng/wiki/Installation - and just rebooted before uploading firmware, according to this doc nothing special was needed to switch.
It flashed without any issue and all settings were right on place, the only thing I noticed was turned off openvpn server, but new version has much more options. I just turned that on and everything was ok.
Later, next day I installed entware and wireguard, tested that and it was way easier than openvpn for setup and use it on mobile devices.
I was able to connect via wireguard on external network and access router admin panel via it's internal ip. Great and much easier than OpenVPN. I needed to add some usb3 drive for entware but it installed with no problem just like in docs.
Then I noticed that some devices are disconnected from network and they are not able to reconnect anymore. Checked few of them and quickly discoved that they autenticate but can't get IP or anything from DHCP server. On mobile phones it stuck at "obtaining ip address". With manual ip setup they were able to connect to wifi and Internet.
I checked manu threads on dhcp, tried to alter many options on lan, wan, vpn.. nothing helped
Also there was no clue in logs, all dhcp leases eventually were empty and nothing could connect automatically.
Home router without dhcp is not much usable, of course I got idea to just turn off dhcp and run some dhcp on kubernetes, but it would take some time to find good services and configure it. I found one thread about similar issue and advice to hard reset device, I still didn't wanted to lose all settings. Instead of that I decided to do "downgrade" to asus original firmware. That process was successful, and DHCP started to work again. Bye wireguard and entware
Ok, I got reverted router to original firmware, all basic stuff works now, but I still would like to get those two features. Any idea what was wrong on this upgrade? Anything else I should try other than hard reset right before (or after) upgrade? Anyone tried 386.4 on AC86U with no dhcp problems?
I followed this: https://github.com/RMerl/asuswrt-merlin.ng/wiki/Installation - and just rebooted before uploading firmware, according to this doc nothing special was needed to switch.
It flashed without any issue and all settings were right on place, the only thing I noticed was turned off openvpn server, but new version has much more options. I just turned that on and everything was ok.
Later, next day I installed entware and wireguard, tested that and it was way easier than openvpn for setup and use it on mobile devices.
I was able to connect via wireguard on external network and access router admin panel via it's internal ip. Great and much easier than OpenVPN. I needed to add some usb3 drive for entware but it installed with no problem just like in docs.
Then I noticed that some devices are disconnected from network and they are not able to reconnect anymore. Checked few of them and quickly discoved that they autenticate but can't get IP or anything from DHCP server. On mobile phones it stuck at "obtaining ip address". With manual ip setup they were able to connect to wifi and Internet.
I checked manu threads on dhcp, tried to alter many options on lan, wan, vpn.. nothing helped
Also there was no clue in logs, all dhcp leases eventually were empty and nothing could connect automatically.
Home router without dhcp is not much usable, of course I got idea to just turn off dhcp and run some dhcp on kubernetes, but it would take some time to find good services and configure it. I found one thread about similar issue and advice to hard reset device, I still didn't wanted to lose all settings. Instead of that I decided to do "downgrade" to asus original firmware. That process was successful, and DHCP started to work again. Bye wireguard and entware
Ok, I got reverted router to original firmware, all basic stuff works now, but I still would like to get those two features. Any idea what was wrong on this upgrade? Anything else I should try other than hard reset right before (or after) upgrade? Anyone tried 386.4 on AC86U with no dhcp problems?