<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Openconnect on Raven's Blog | Linux and IT</title><link>https://r4ven.me/en/tags/openconnect/</link><description>Recent content in Openconnect on Raven's Blog | Linux and IT</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://r4ven.me/en/tags/openconnect/index.xml" rel="self" type="application/rss+xml"/><item><title>Configuring an OpenConnect middle server for access to a closed network</title><link>https://r4ven.me/en/networking/nastraivaem-openconnect-middle-server-dlya-dostupa-k-zakrytomu-konturu/</link><pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate><guid>https://r4ven.me/en/networking/nastraivaem-openconnect-middle-server-dlya-dostupa-k-zakrytomu-konturu/</guid><description>&lt;strong&gt;Greetings! &lt;i class="fa-solid fa-crow"&gt;&lt;/i&gt;
&lt;/strong&gt;

&lt;p&gt;In this note, we will look at using an &lt;a href="https://r4ven.me/en/networking/podnimaem-openconnect-ssl-vpn-server-ocserv-v-docker-dlya-vnutrennih-proektov/"&gt;OpenConnect&lt;/a&gt; server as an intermediate server for access to closed infrastructure.&lt;/p&gt;
&lt;p&gt;I will point out an important detail right away: the main goal here is not to bring up a regular &lt;strong&gt;ocserv&lt;/strong&gt; once again. I already have a separate guide for that. The more interesting part here is the &lt;strong&gt;middle server&lt;/strong&gt;, which accepts user connections, establishes its own client OpenConnect connection to the closed network, and then routes traffic further.&lt;/p&gt;</description></item></channel></rss>