Important NetworkManager Changes

Article Description/Outline:

Theres been some changes that affect NetworkManager for F45. An article outlining what they are and how they impact end-users was approved by FESCo to be published for F45 release. I have a draft in a google doc, with some members of the network manager team editing and reviewing it for correctness, as I did use google gemini to pull the information together for me.

If this article is ok to publish in the magazine on release day, pending editor review of course, that would be great and very appreciated.

Im also not sure what to call it, so better title name suggestions are welcome too :slight_smile:

I have read and understand the Ai-Assisted Contributions Policy


For Editor Use Only

Editor: rlengland

Image Editor:

Publication Date: 03 November 2026

Preview Link: Migrating away from unmaintained NetworkManager VPN plugins (vpnc and fortisslvpn) Fedora Magazine

This would be a good article for the Magazine. You might include a reference to your use of gemini, if you feel it is pertinent.

Let us know when you have it ready for review with the preview link in WPEngine.

Thank you.

Ack, will do @rlengland . The draft is currently with the humans who are involved with network manager, so once they are finished their edits I will submit it into wordpress for magazine editor review. I will also add a note to the article that gemini was used creating the article, and knowledgeable humans edited it :slight_smile:

@amoloney I’m content to use the F45 release background for this article but if you want to separate this article from the F45 release, you might canvass the " knowledgeable humans" for ideas for a feature image.

Just a thought.

I’ll ask :slight_smile: Otherwise we can use the F45 one, or even just a standard Fedora Project one … if that exists :sweat_smile:

https://fedoramagazine.org/?p=44587&preview=true&preview_id=44587 is the link to the network manager article.

If you want to change featured image, wording, or anything else, please feel free to :slight_smile:

I’ve had some folks from the network manager team in Red Hat review this content for accuracy. I believe its all fine, however I am waiting on one last verification from the team. One of their engineers left some super helpful, but very technical comments in the doc and theyre now on PTO. Ive included the comments in there, but as they are instructions, I would feel better to get an ack from one of the engineers on the team that I have copied the content accurately.

@amoloney I’ve edited a few things for clarity and word-flow but nothing technical. If changes are needed make them as required. We have until release day (or after, if needed) so make them as required.

After publication the editors will need to help if changes are needed.

The network manager team in RH did some tweaking to the google doc and Ive since updated the article. I cannot format the option 2 section (Cisco IPsec etc) nicely :frowning: line 2 is all messed up. It should look like this:

  1. You may need to create file /etc/ipsec.d/ikev1.conf with this content:

config setup

ikev1-policy=accept

This enables the deprecated IKEv1 protocol. Then restart ipsec.service. Note that the ipsec.service must be running, or the activation will fail.

Or something like it. Could one of you folks make the edit please? The article is good to go then and thank you very much for tidying it up and adding its own feature image :smiling_face:

@amoloney Take a look at that section now and see if I that is what you need,

Yep thats perfect, @rlengland . Thank you!