@Clive_A 

Hi Clive,

Thanks for the update ad looking forward to both these .... hopefully they'll arrive on the ER605 platform coupled with an OC200 controller.

Kind regards,

Mike

  Hi,

My vote for FQDN !!

My best regards

  @Clive_A to consolidate the conversation, Mullvad VPN announced end of life for OpenVPN support,

so more number of users it's time sensetive topic:

https://www.reddit.com/r/mullvadvpn/comments/1gmf2id/removing_openvpn_15th_january_2026_blog_mullvad/

As for UI improvements, there is number of open source UI projects that allow easier control of wireguard configuration, including QR Code generators, and config file downloads (and I want to emphasize that QR code by itself, isn't enough, as there are clients that can't work with WG qr codes, and need config files upload).

Good example for the latter is Passepartout (https://passepartoutvpn.app/), it's iOS version doesn't have option to choose Wireguard and scan QRCode, but requires to upload WG config file, and then it enable WG support.

Thank you.

  @Clive_A 

> Sub this to get the update timely: Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates.

Looks like that post is locked and doesn't get posted recent updates, 

Example, for "Recent releases / Early access", it lists v1.2.0 for ER8411 from January of this year (11 months old)

> ER8411 V1_1.2.0_Build 20240112 Beta Firmware for Omada Controller V5.13 (Released on Jan 12th, 2024)

While my current software version for ER8411 is 1.2.2.

And this is the one that has any mentions of the Omada version in the range you posted (v5.15 and 5.16), so it's not clear if there was no version bumped for the whole 2024 from 5.13, and for how long we'd need to wait to get our hands on 5.15 and 5.16, or that updates haven't been posted, and 5.16 is much closer than 2027.

Thank you.

Hi @alexindigo 

Thanks for posting in our business forum.

alexindigo wrote

  @Clive_A 

 

> Sub this to get the update timely: Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates.

 

Looks like that post is locked and doesn't get posted recent updates, 

 

Example, for "Recent releases / Early access", it lists v1.2.0 for ER8411 from January of this year (11 months old)

 

> ER8411 V1_1.2.0_Build 20240112 Beta Firmware for Omada Controller V5.13 (Released on Jan 12th, 2024)

 

While my current software version for ER8411 is 1.2.2.

 

And this is the one that has any mentions of the Omada version in the range you posted (v5.15 and 5.16), so it's not clear if there was no version bumped for the whole 2024 from 5.13, and for how long we'd need to wait to get our hands on 5.15 and 5.16, or that updates haven't been posted, and 5.16 is much closer than 2027.

 

Thank you.

1. I don't decide what dev's project and their progress. I think I cannot answer or reply anything else to what you described here. Nor do I affect the version and firmware release cycles. I am only providing the information and what I have or I could get about the product.

Firmware adaption follows the controller update. When a feature is on the Controller, its adapted firmware follows and will be marked out as adapted to the X.Y.Z Controller.

2. The last public beta was that time ago. And the official firmware release has it clearly on its adaptation. 1.2.1 and 1.2.2 are minors. If they were released with minor changes and fixes, they have the chance to not be opened for public beta. What would be wrong with that?

The latest release actually works well with the V5.14 since it was released. If there are no major features added to V5.14(as an example), it may not specify what firmware it adapted. There were no major GW functions were added during V5.14. That many features were on V5.13 so the release note was written in that way.

3. The post only got updated by the forum mods and we don't intend to open it for users to comment.

My best effort is to get your voice heard. But don't decide when the dev's gonna begin the development of your request. You could happen to request a feature that is on the road or in high priority.

If it is not planned, or it is planned in the long-term future, I may not be able to help you push it as I don't have the power to do so.

Dev shares the information about their plan on what version they plan to release a version. However, due to the division changes, I might soon lose first-hand access to the dev. I am afraid the information down the road is more limited.

Due to previous replies we had with other customers, we no longer provide any guarantee or estimated timeline for any features. We have clearly disclaimed that the development may be advanced or delayed but some users chose to ignore this. We will release the beta/pre-release firmware without any notice. If there is one, I will work with the team and upload it soon. Therefore, please pay attention to the post and pinned threads.

  @Clive_A Now that the beta controller 5.15 is out, do you have an update on FQDN?

If we won't get FQDN, would it be possible to use a script to update the peer IP address using the open API?
If so, do you have an example of what that would look like?

  @ttocsr 

ttocsr wrote

  @Clive_A Now that the beta controller 5.15 is out, do you have an update on FQDN?

If we won't get FQDN, would it be possible to use a script to update the peer IP address using the open API?
If so, do you have an example of what that would look like?

As it explains if you could read it again.

OpenAPI is not a reign of my ability. It's under the controller. AFAIK, we do not support script or API to do that.

  @Clive_A 

This is going to be a long one and I will try to explain everything as clearly as I can because I use this feature almost every day and for every new client I have!

I never answered to you and Im sorry. This website is NOT a part of the official WG. its a website.

An even simpler and better tool is the github com/wg-easy/wg-easy (focus on the download and QR Code buttons not the rest)

What Omada needs to implement from that tool is the QR code ( you scan it and it has all the info for the wg.conf, very usefull for rolling profiles on a mobile device) and the conf download button that downloads the file to be IMPORTED to the wireguard official app.

This way I can roll .conf for my clients and their devices in one place. Many of my clients want the ability to WOL their PCs so they can connect to them and work remotly from their home. For that to work I have to both expose a WOL service like UPSNAP on their local network and the only safe way for that to happen is a VPN connection back to the office.

As it is right now for me to work with the system omada gives me I need to either use some third party webpage or tool to roll credentials or use the official WG method that requires a console and a LOT of copy pasting (official tools are only wg and wg-quick). Also I need to edit and manually write all the conf files for the client devices. This is immensly slow. 

Here is how Omada could speed the whole thing up by A LOT step by step on the Omada UI:
1) On the wireguard page when creating the interface server right now omada already autocompletes the MTU,PORT and Private/Public Key so the admin will have to fill the name and the wg server ip. Instead of asking for the IP it should ask for the IP+RANGE that the server and its clients will be in. That way you input something like 10.0.0.1/24 and that means that the server will have the 10.0.0.1 IP and each clients will have the next one after that(.2 ,.3,.4 etc). 

2) On the Peers part where you create the clients interfaces Omada autocompletes nothing other than the Keep alive ping. So the Admin must provide Name, wgserver,AllowedAddress (ip that the client will be allowed to connect as) and the public key. Instead asking all that the omada system could roll the next available IP with the interface selection(eg 10.0.0.2/32 on the first peer) and also roll the private and public key of the peer. Additionally for added security you can add a generate button next to the preshared key and also include that in the downloadable conf file. Everything is ofc editable and someone with a more advanced wireguard setup can input what they prefer as usual and this change wont actually bother them at all as they already had to add all that manually. 

Regarding the Endpoint and Endpoint port the simple solution is to set those settings on the wireguard interface creation and accept static IPS or FQDN for people that use a DDNS service, those are useless for the server so you dont even need to make validations other than what they wrote is either and IP or a FQDN addresses as the server does not use those fields at all and are only text that gets used on the conf files of the peers. That way if you filled those fields on the wg interface creation they get autocomplete on the peer creation too! One last thing that needs to be added is the AllowedIPs option that tells the computer what IPS go throught the tunnel. That could be as simple as a checkbox of the available LANS that you want the peer to have access to and also an option to set the tunnel as a split or full, a simple checkbox next the lan list can set that easily (checking the box adds 0.0.0.0/0, ::/0 into the list of LANS that pass throught the tunnel).

Finally on the Peer tab you present 3 new buttons: 
    BUTTON A) [Quick Create Peer] This rolls literally everything including the name and you are instantly presented with a small modal window with the QR code and the option to download either the QR image or the conf file in a zip. If there are more than one WG intefaces you get precented with a modal to select the one that this peer will connect to with a dropdown as you already do in the peer creation screen.

    BUTTON B) [DOWNLOAD] This just donwloads the conf file so the user can import it to the wireguard app.  

    BUTTON C) [QR CODE] Same as the first modal from the first button you get precented with the same QR code and the options to donwload the qr img or the conf file same as before so you can reuse the same thing. 

Here is a recommendations of where the buttons can be:

Let me clarify that each change here only adds to the usefullness of the omada system and does not detract from an advanced user that wants to roll a fully custom WG interface as they will still have to edit the same exact fields! I feel the bane of the current process to my bones for about a year and a half now. I beg of you to make this process easier. I use Omada with all my clients and I now even have both your OCNA certs! Only reason I have such passion and request those features is because I would love to be able to roll out network for my clients even faster. Help me help you!

Sorry for the huge post   @Clive_A  I Know you have to read LOADS of posts each day. And thanks for your time