<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Office Networks on VPN Works</title>
    <link>https://vpnw.com/tags/office-networks/</link>
    <description>Recent content in Office Networks on VPN Works</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vpnw.com/tags/office-networks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Office Route Case Study: Ticket Filed Through the Office Exit, With the Deploy Token Still Blocked</title>
      <link>https://vpnw.com/office-route-case-study-ticket-filed-through-the-office-exit-with-the-deploy-token-still-blocked/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/office-route-case-study-ticket-filed-through-the-office-exit-with-the-deploy-token-still-blocked/</guid>
      <description>&lt;p&gt;Some of an agent&amp;rsquo;s work lives inside a company network: an issue tracker, a package mirror, an internal API. The usual way in is the company VPN, and it takes the whole machine along. Every program on the laptop, the browser included, now goes through the office, and the agent can reach everything on that network that the laptop can.&lt;/p&gt;&#xA;&lt;p&gt;In the Alpha demo one program at a time goes through the office. The office network has an exit, a SOCKS5 proxy inside it at 10.8.0.1, which knows internal names such as &lt;code&gt;tracker.office.internal&lt;/code&gt;. vpnw sends the agent there and nothing else. The agent files its ticket, and its policy still stops the deploy token.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
