@David-TP I recently purchased this device, but I have issues with Wireguard. It simply does not connect. I tried configuring it from config file or just manually entering required details. It shows "connected" but it is not the case. There are even no attempts made to my WG Server. I know that configuration is correct since when I load it on any device that's connected to M8550, it works.

I tried pinging my wg gateway from diagnostics menu and that works. Am I missing something, or is that some known bug perhaps?

  @David-TP I received the device today. Compared to my Netgear Nighthawk M6 Pro, it gets very warm even without any load – both with and without the battery. It doesn't take much to trigger a temperature warning. Will this be fixed with an update soon?

  @David-TP Perhaps I could try that too? Mine was also getting warm and received several warnings about temperature even if it was just sitting on the desk, barely doing anything.

In any case, I also want to say that my previously reported issue with Wireguard was related to the MTU (don't use anything else than 1500 otherwise it won't work).

I have the same issue here. The device does not even try to connect to my wireguard server running on opnsense, but in the web ui it shows, that the connection is active. Pinging my server is sucessfull. I also noticed that the provided configuration file was not properly parsed. The port was displayed as "1820" but was "51820" in the file. Also the first letter of the server name was truncated.

And last but not least the device gets really warm in idle state. Would be glad to test the beta firmware.

  @LutzB issue with WG is related to MTU. You need to keep it at 1500. Anything else causes tunnel to not work.

Also make sure you enable client to communicate within tunnel.