This is something I’ve noticed on Core 189, and at least 188 aswell. (See the image)
I know the topic of Wireguard being included on IPFire has come up a number of times before on the forum. My understanding is that it’s planned to be included in IPFire 3, and at some point in IPFire 2.XX when time & resources allow.
Does it showing up like this is the Web UI have any significance that it’ll be included sooner or is it just a typo?
It has been added in there so it is ready for when it does come. You will also see that Wireguard is also there in the Connections WUI page. Those things are the relatively easy steps to do.
As you say there have been other post threads on wireguard
where wireguard has been asked for and donations to support us have been requested but as the last post in the above list indicates there has not been any real indication of interest based on the donations. So it will have to get worked on when free time occurs to apply some focus and time to it.
Exactly this. We have a working prototype which is really nice and easy to use and we have started to integrate it into some parts of the OS which we have already shipped. I agree that this us very confusing now, but there was the hope that we can fast-track this project a lot more, but sadly there has been very little interest since the development team decided to actually work on this, which is surprising to at least me considering the attention this got before.
wireguard has been asked for and donations to support us have been requested but as the last post in the above list indicates there has not been any real indication of interest based on the donations.
What is the amount you need to make Wireguard a fully-fledged option in IPFire? Some several thousand euro, I would guess, no?
Thank you both for the updates. It is definitely a little confusing to have the Option in certain pages of the WebUI if it doesn’t do anything.
I would be very excited about the inclusion of Wireguard in IPFire. I moved over to it from OpenVPN after many issues with the connection hanging, and it’s been quite flawless since I started using it. I’m currently running it in a Virtual Machine running on my IPFire system, it would be nice to be able to shut that Virtual Machine down.
I will send a donation to you guys to help it happen sooner. (As I usually do this time of year)
I have WireGuard running through MVPS @ $4pm. I tried WG with HomeBrew, MacPorts, WireGuard itself and Terminal reported it was not encrypting although the App green dot was visible! On the other hand the MVPS connection with the WireGuard App from the Apple Store took a minute to install and worked immediately. It connects through the router but not through IPFire.
That is because IPFire does not have Wireguard installed yet. Some WUI menu’s have had Wireguard implemented but the capability itself is not yet available.
There was a lot of initial interest expressed in Wireguard but, as mentioned earlier in this thread, when donations to support the work were requested there was no increase in the donation level.
So Wireguard will be worked on when it can be fitted in amongst the other things that need to be worked on. The last commits to the development branch for wireguard were from early Dec 2024.
The IPFire-3.x Pakfire build system is where the focus has been lately with around 650 commits since the start of 2025.
Without donations then wireguard will eventually be done but on the basis of being fitted in between all the other development activities and IPFire-2.x maintenance activities that are on the list needing to be done.
I was drawing the readership’s attention that Wireguard via MVPS was created easily and instantly but your IP address is visible. Then
dropped MVPS for Proton as Wireguard IP is then hidden.