<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ASA on Problem of Network</title>
    <link>https://6364c9bf.problemofnetworkdotcom.pages.dev/tags/asa/</link>
    <description>Recent content in ASA on Problem of Network</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 22 May 2015 00:25:00 +0000</lastBuildDate>
    <atom:link href="https://6364c9bf.problemofnetworkdotcom.pages.dev/tags/asa/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>IPv6 on Cisco ASA</title>
      <link>https://6364c9bf.problemofnetworkdotcom.pages.dev/posts/ipv6-on-asa/</link>
      <pubDate>Fri, 22 May 2015 00:25:00 +0000</pubDate>
      <guid>https://6364c9bf.problemofnetworkdotcom.pages.dev/posts/ipv6-on-asa/</guid>
      <description>&lt;p&gt;This is the first in what will no doubt be a many part series on deploying IPv6.  This is a problem I have had to overcome recently, and still to this day I battle with the implementation subtleties.  If you find yourself in my shoes, I hope you find this helpful.&lt;/p&gt;&#xA;&lt;p&gt;So, firstly, you need to consider your architecture. Mine, I am reliably told is totally wrong.&lt;/p&gt;&#xA;&lt;p&gt;I use ASAs as routers in the campus.  Why? Cos shut up - that&amp;rsquo;s why!  I like to maintain user group segmentation, and I also like to maintain security policy quite tightly.  Therefore I put all users in VLANs managed by 802.1x, and all those VLANs gateway on an ASA trunk subinterface.  I then provide an appropriately sized routed L3 subnets from a site specific IPv4 /21 and have ACLs as access-groups.  Voila - policy is maintained at the gateway border.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
