is there a breakdown in plain language on how to set one of these up?
It seems like the configuration information is scattered to the wind with multiple articles all over the place on setting these up. I have found several that are useful, but things are not labeled in a consise manner to make it easy to understand just what is placed where. One of them i think got my config 90% of the way but it says to modify the private cert on the client, but i cant modify the private cert.
Also many say to use an unused ip, but none specify if i need to create a new dhcp scope / interface.
the setup has significantly less requirements than openvpn but its poorly labeled and explained. for example i just found out that the endpoint on my client device would point to my home vpn server that was not obvious to me since i would consider the endpoint to be the actual end device i wish to connect to ( my emby server ).
The export button is also missing on my omada controller which is weird with how much documentation says to just export the config.
One big question i have on all of this, when it comes to the wireguard ip address on the router is that a ip address that has to already exist in a dhcp scope on the router? For example i use 192.168.1.1/24 on my lan side of the router, do i have to select an unused ip from that pool? Can i use virtually anything like 192.168.3.1?
I found a online configuration builder, i cant import into omada but it was really helpful in getting me to understand just where things were going wrong for me, and i had the certs almost all in the wrong places. The weird part is wireguard did not give any authentication errors at least none that pop up on the screen maybe there is a log file somewhere full of them. I would still call wireguard easy to set up by comparison to openvpn aside from omada's itteration of openvpn because omada does a good 90% of the work for you.
Thank you all very much for the referance material, i would suggest people google wireshark configuration generator and throw in some bogus yet easy to spot information ( like i want to connect to ham dot com with dns of 1234 ) to see where everything gets placed. It says it doesnt hold onto any of the info, but if the info isnt valid anyway you never need to worry and its better to use as a learning tool than a crutch and never create your own.
