Hi @Clive_A and thank you for taking the time to answer to my post.
Lets focus on the WG experience in conjunction with a good DDNS update service for easy of use.
Let me clarify that I provide IT services to many small to medium size companies of 5~50 employees and literally most of them don't/wont pay for static IP (high cost here in Greece) because its like half the price of the already high ISP sub( I know they should but I cant force them and I have to work with what I have)
For starters as I understand it the controller is the part of the omada SDN experience that pings info back you your servers + manages all the SDN devices. What I meant in the previous post is that if only the controller manages the whole stack and talks back to the omada service then it should check the IP on the router and pass that back to you. Sorry for not being clear enough
So for the DDNS part my request is as follows.
Provide a new "Omada DDNS" service to your clients like Synology, fritz etc already does for free. For example.
That way I can:
1. Login to the omada interface
2. Navigate to the services in my site
3. Select DDNS
4. Instead of the other services just select the Omada DDNS and add just the hostname e.g. xarishark[dot]omada[dot]com
That way your client wont have to sign up for a separate service and make the whole process far better for your clients.
Also add some kind of feedback to the current DDNS page that shows that the DDNS is getting update and is in working order ( a green dot or whatever would be totaly fine)
What my WG VPN DDNS setup entailed before acquiring Omada:
My fritzbox router has a super easy one click config generator (downloads a zip with a QR image and wg*[dot]conf file) that uses its own intergrated DDNS service with the choice if you want to replace that with a static IP or a Hostname .I also have the choice for my synology to do the same thing OR my server to run a container with cloudflare/duckdns DDNS.
For the WG part
Include a easy wg rollout process. I dont mean remove the advanced options. What I would like is:
Open the VPN menu. Create new WG server. Input Server name, generate pKey( already automatic GOOOOOD). Instead of only accepting the WAN static address do the following:
1. Allow for hostname instead of IP (you already do that on SOME other vpn types)
2. Add a button on the right to open a small drop down and select one of the activated DDNS services eg NO-IP currently for me (Thats where your own DDNS service would come in and make the whole process SUPER fast and easy).
What we do now with Omada if we want WG VPN with a DDNS service:
1. Go to supported DDNS service create account create hostname
2. Go to omada DDNS page and login to that DDNS account and add the hostname
3. Go and create NON WG vpn server because hostnames are NOT ACCEPTED currently
4. Manually write the hostname that is already imported to the DDNS omada interface (not big deal but would be awesome to fix)
5. Manually roll out keys and info for each VPN user and manually write their ip space for when they login to the VPN
What the perfect process would go like:
1α. Go to the DDNS settings page in omada (already logged in so the credentials are already there)
1β. Create "Omada DDNS" hostname (controller gets ip from router and passes it to your own DDNS service)
2α. Go to the WG VPN settings page and create server
2β. If there is only one Hostname in the DDNS page then auto select that hostname and generate the pKey (User literally only has to select server Name). Otherwise offer a dropdown with a list of hostnames and an option for manual input OR add a button on the right that opens a list of imported hostnames (most people use one hostname at all times for DDNS anyway)
3α. Go to the WG Peers page and press Create New Peer
3β. Menu asks if you want to auto generate or manually generate the Conf file
3γ. Select auto generate open the same menu as the manual but everything other than Name and Comment is generated automatically.
3δ. On save give the option to download a zip with QR code and . conf file or show the qr code and conf file contents on the screen for copying instead of downloading.
This way you can still do all the advanced tuning you want and create whatever you want but also have the option to one click generate everything and have it still working perfectly!
I create new VPN peers for my clients almost daily and I would love to integrate them in the Omada SDN ( each client will be a separate site on my work Omada account)
That way when not only I can manage ALL MY CLIENTS from one Omada account but when I setup a new client I just have to setup the hardware and add the controller to my work account and setup everything else remotely (already able to do that)
And when they ask me to roll a new VPN peer for the laptop of their new employee ( I get asked to do that daily because of the number of clients I have) I just have to open their Omada site for that office and generate a new WG peer download/copy it and import it to the employees laptop or my deploy it with MS Intune during endpoint creation.
I can totally understand if its not viable economically to create your own free DDNS Service (Synology is a company that sells MOSTLY to companies and provides it tho so I believe that they ARE your competitor as they provide both routers Ap and cameras now and also NAS servers etc)
But the interface of DDNS - VPN server creating - Client config auto generation is a no brainer IMHO. WG server is already super simple.
The first step for the better would be to allow WG to accept a HOSTNAME on the address asap. Everything else I get that needs dev time and if it helps I can create a feature request on the forum to get voted on so you can scope the community response. Would that help you. If you have any questions I would be happy to hear them and answer!
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
