<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Squid on Lead DevOps</title><link>https://lead-devops.blackdevhub.online/en/tags/squid/</link><description>Recent content in Squid on Lead DevOps</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lead-devops.blackdevhub.online/en/tags/squid/index.xml" rel="self" type="application/rss+xml"/><item><title>Squid: Internet Forwarding to Remote VM</title><link>https://lead-devops.blackdevhub.online/en/posts/squid-proxy-remote-vm/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>https://lead-devops.blackdevhub.online/en/posts/squid-proxy-remote-vm/</guid><description>&lt;p&gt;Your VM in the cloud has no public IP or internet access is blocked via NAT, but the deployment needs wget/curl from inside. Squid on an intermediate host with a decent uplink solves this in ten minutes.&lt;/p&gt;&#10;&lt;h2 id="why-this-is-needed"&gt;Why This Is Needed&#10;&lt;/h2&gt;&#10;&lt;p&gt;I forward internet through Squid when a VM sits in an isolated network segment. An intermediate host with a public IP and network access becomes the proxy server. The application on the remote machine routes traffic through the tunnel.&lt;/p&gt;</description></item></channel></rss>