<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Vpn on Matt&#39;s Blog</title>
		<link>https://mattdrew.net/tags/vpn/</link>
		<description>Recent content in Vpn on Matt&#39;s Blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 08 Mar 2021 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://mattdrew.net/tags/vpn/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Forcing web traffic to Umbrella proxy tunnel using policy based routing on Cisco ASA</title>
				<link>https://mattdrew.net/posts/pbr-umbrella/</link>
				<pubDate>Mon, 08 Mar 2021 00:00:00 +0000</pubDate>
				<guid>https://mattdrew.net/posts/pbr-umbrella/</guid>
				<description>&lt;p&gt;Network requirement: Stringent control over web traffic, even over clients that are not using the Umbrella roaming security client. Force internal to external web traffic to use the proxy. Exert absolute dominance over your office users!&lt;/p&gt;&#xA;&lt;p&gt;Scratch that last bit, but it DOES feel good, doesn’t it? Let’s get to cracking.&lt;/p&gt;&#xA;&lt;p&gt;Configuring the Umbrella tunnel ‘A side’&lt;/p&gt;&#xA;&lt;p&gt;This guide assumes you have already set up the Umbrella side of the tunnel using the below guide. It is a very simple procedure even without the guide so I’m not going to repeat it here. Your public IP must be configured so that they know to expect the incoming connection. You must also set your tunnel key which must be matched in the config below.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Dynamic Split Tunneling for O365/Teams/Zoom on ASA</title>
				<link>https://mattdrew.net/posts/asa-dst/</link>
				<pubDate>Thu, 09 Jul 2020 00:00:00 +0000</pubDate>
				<guid>https://mattdrew.net/posts/asa-dst/</guid>
				<description>&lt;div class=&#34;retro-alert retro-alert-warning&#34;&gt;&lt;div class=&#34;retro-alert-header&#34;&gt;Careful&lt;/div&gt;&#xA;  &lt;div class=&#34;retro-alert-body&#34;&gt;&lt;p&gt;Be sure that you are basing your ACL on the most current network lists posted by Microsoft/Zoom. These networks do change, and there are automations not mentioned here that can be used to dynamically update your ACL.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&#xA;&lt;p&gt;CustomerA requires their AnyConnect full tunnel be converted to a dynamic split tunnel to improve cloud conferencing performance and to reduce network congestion.&lt;/p&gt;&#xA;&lt;p&gt;Initial config:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;group-policy grpISE internal&#xA;group-policy grpISE attributes&#xA;wins-server value 192.200.22.11 192.200.67.32&#xA;dns-server value 192.200.22.11 192.200.67.32&#xA;vpn-simultaneous-logins 1&#xA;vpn-idle-timeout 30&#xA;vpn-session-timeout 720&#xA;vpn-tunnel-protocol ssl-client ssl-clientless&#xA;split-tunnel-policy excludespecified&#xA;split-tunnel-network-list value SplitTunnelACL&#xA;default-domain value customera.com&#xA;client-bypass-protocol enable&#xA;msie-proxy server value 192.200.72.91:80&#xA;msie-proxy method no-modify&#xA;msie-proxy except-list value 127...*;localhost&#xA;msie-proxy local-bypass enable&#xA;msie-proxy lockdown disable&#xA;webvpn&#xA;anyconnect mtu 1300&#xA;anyconnect ssl keepalive 90&#xA;anyconnect dpd-interval client 90&#xA;anyconnect dpd-interval gateway 90&#xA;anyconnect modules value iseposture&#xA;anyconnect profiles value acVPN type user&#xA;anyconnect ssl df-bit-ignore enable&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Okay, so it’s a split exclude, excluding only 0.0.0.0/32 via SplitTunnelACL&#xA;Excluding this address will result in your LAN subnet being excluded from the tunnel.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
