<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IPSec on Jaymin Patel</title><link>https://jayminpatel.elemprin.com/tags/ipsec/</link><description>Recent content in IPSec on Jaymin Patel</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 22 Aug 2022 00:00:00 +0530</lastBuildDate><atom:link href="https://jayminpatel.elemprin.com/tags/ipsec/index.xml" rel="self" type="application/rss+xml"/><item><title>IPSec VPN on OpenWrt: From Config Files to UCI</title><link>https://jayminpatel.elemprin.com/posts/2022-08-22-libreswan-ipsec-uci/</link><pubDate>Mon, 22 Aug 2022 00:00:00 +0530</pubDate><guid>https://jayminpatel.elemprin.com/posts/2022-08-22-libreswan-ipsec-uci/</guid><description>&lt;p>Setting up an IPSec VPN on OpenWrt used to mean editing &lt;code>/etc/ipsec.conf&lt;/code> by hand -- tracking down the right parameters for your topology, debugging misconfigured secrets, and restarting the service after every change. For site-to-site tunnels between branch offices, or road-warrior access for remote employees, the manual approach worked but didn't scale.&lt;/p>
&lt;p>Libreswan, the IPSec implementation used in OpenWrt, is a battle-tested VPN stack. But until now, it lacked the configuration layer that makes OpenWrt's ecosystem so powerful: UCI (Unified Configuration Interface). With UCI support, Libreswan joins the rest of OpenWrt's services -- configurable through a consistent interface, scriptable for automation, and manageable at scale.&lt;/p></description></item></channel></rss>