....its a bit half backed. Wireguard is now broken. Previous working accounts now no longer work. Setting up new accounts from scratch don't appear to work. The Client Configurator misses out key details from the client configuration like the port the service listens to (it shows NaN instead) and the Public Key of the Peer. Even if I manually add those in, clients can't connect.

"If PPTP or L2TP is enabled, password cannot be null" is thrown up when creating new Wireguard Accounts even when PPTP and L2TP services are not ticked.

As others have pointed out, Bind to IP Client Comments become corrupt. Seems to include characters from the next entry in the list.

Router has crashed once already. Was rock solid on 4.4.3.x

Still testing the other features so will update here.

Hi pharcyder,

Regarding:

"If PPTP or L2TP is enabled, password cannot be null" is thrown up when creating new Wireguard Accounts even when PPTP and L2TP services are not ticked.

Try enabling the ‘Wireguard’ option in “VPN and Remote Access >> Remote Access Control Setup”, and cancel the request that may pop up to reboot the router, then go back to the profile you’re trying to configure and de-tick the ‘Wireguard’ option (which is ticked and grey-out by default when not using Wireguard globally). Now you should be able to save the profile.

Then de-tick the ‘Wireguard’ option in “VPN and Remote Access >> Remote Access Control Setup” again, cancelling any request to reboot.

This is clearly a stupid oversight by the programmers when they added the ‘Wireguard’ feature in a FW update many months ago; and it’s still not fixed.

Sorry, on re-reading your dilemma again, I see yours is the reverse of what I’m highlighting. Although it may work equally but in reverse, by enabling/disabling the PPTP and/or L2TP options to make changes.

Thanks for sharing....but yes it doesn't help the Wireguard Problem. WG is just fundamentally broken in 4.4.5. Disabling / Enabling the service and setting up Dial in accounts from scratch just doesn't work any more. Rolling back to 4.4.3.2 works just fine for existing and new dial in accounts.

Same here on a 2865Lac, tried firmware 4.4.5 and it crashed and rebooted, not to mention the mess that is the IP Bind comments.

I would advise anyone to stay away from from firmware 4.4.5 until the issues are resolved.

Gone back to 4.4.3.2 and all is good again.

IP binding was corrupted here too but worse still, the two VOIP ports are both failing to register. Settings seem fine and unchanged from before the upgrade but the lines are not registering on the VOIP providers system. I went back to 4.4.3.2 and it all immediately started working again.
I thought the phone was unusually quiet!

If anyone is wondering, 4.4.5.1 is now out for the 2865 & 2866 but does not fix any of the issues reported here.