<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic VLAN3 Routing Issues ASA5505 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715064#M560893</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A couple of thoughts here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Vlan1&lt;/P&gt;&lt;P&gt;nameif inside&lt;/P&gt;&lt;P&gt;security-level 100&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip address 10.10.16.1 255.0.0.0 &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure why you are using a /8 for the inside interface, as this would include the IP that is assigned to VLAN3 (10.1.6.36/16, which falls within 10.0.0.0/8).&amp;nbsp; VLAN1 and VLAN3 should not be in the same subnet, this needs to be corrected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;nat (inside) 1 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue is you are requiring NAT to take place when traffic is originated from behind the inside interface.&amp;nbsp; You can resolve the issue by PAT'ing traffic to the DMZ interface:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside2) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With this configuration, when traffic from inside is destined to a host behind outside2, the traffic will be PAT'ed to the outside2 interface IP of 10.1.6.36.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you would like the IP to not be PAT'ed, then you can use this static NAT configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside2)&amp;nbsp; &lt;NETWORK_ID of="" inside=""&gt; &lt;NETWORK_ID of="" inside=""&gt; mask &lt;SUBNET mask=""&gt;&lt;/SUBNET&gt;&lt;/NETWORK_ID&gt;&lt;/NETWORK_ID&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will allow traffic to pass from VLAN1 to VLAN3 using its own IP address.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Jun 2011 20:04:09 GMT</pubDate>
    <dc:creator>Allen P Chen</dc:creator>
    <dc:date>2011-06-13T20:04:09Z</dc:date>
    <item>
      <title>VLAN3 Routing Issues ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715063#M560892</link>
      <description>&lt;P&gt;My search-fu has failed me and I'm hoping someone here can point me in the right direction:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.2em;"&gt;I'm having an issue with routing my traffic to a 3rd Vlan on my ASA5505. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have my internal VLAN as VLAN1, it is IP address range 10.10.16.xxx&lt;BR /&gt;I need this network to be able to access resources on 2 seperate outside networks. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VLAN2 is 192.168.16.xx, and I have ZERO problems getting traffic between VLAN1 and VLAN2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VLAN3 is 10.1.xx.xx and I am able to ping addresses on VLAN3 from within the ASA, but I am unable to ping or pass traffic from VLAN1 to VLAN3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My configs (With passwords and outside addresses masked of course) are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA Version 8.0(4) &lt;BR /&gt;!&lt;BR /&gt;hostname ciscoasa&lt;BR /&gt;enable password XXXXXXXXXXXXXX encrypted&lt;BR /&gt;passwd XXXXXXXXXXXXXXX encrypted&lt;BR /&gt;names&lt;BR /&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt;nameif inside&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.10.16.1 255.0.0.0 &lt;BR /&gt;!&lt;BR /&gt;interface Vlan2&lt;BR /&gt;nameif outside&lt;BR /&gt;security-level 0&lt;BR /&gt;ip address 192.168.16.6 255.255.255.0 &lt;BR /&gt;!&lt;BR /&gt;interface Vlan3&lt;BR /&gt;no forward interface Vlan2&lt;BR /&gt;nameif outside2&lt;BR /&gt;security-level 50&lt;BR /&gt;ip address 10.1.6.36 255.255.0.0 &lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/0&lt;BR /&gt;switchport access vlan 2&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/1&lt;BR /&gt;switchport access vlan 3&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/2&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/3&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/4&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/5&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/6&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/7&lt;BR /&gt;!&lt;BR /&gt;ftp mode passive&lt;BR /&gt;dns domain-lookup inside&lt;BR /&gt;dns server-group DefaultDNS&lt;BR /&gt;name-server 10.10.16.10&lt;BR /&gt;access-list INSIDE extended permit icmp any any &lt;BR /&gt;access-list INSIDE extended permit ip any any &lt;BR /&gt;access-list OUTSIDE extended permit icmp any any &lt;BR /&gt;access-list OUTSIDE2 extended permit icmp any any &lt;BR /&gt;pager lines 24&lt;BR /&gt;logging asdm informational&lt;BR /&gt;mtu inside 1500&lt;BR /&gt;mtu outside 1500&lt;BR /&gt;mtu SJC 1500&lt;BR /&gt;icmp unreachable rate-limit 1 burst-size 1&lt;BR /&gt;no asdm history enable&lt;BR /&gt;arp timeout 14400&lt;BR /&gt;global (outside) 1 interface&lt;BR /&gt;nat (inside) 1 0.0.0.0 0.0.0.0&lt;BR /&gt;access-group INSIDE in interface inside&lt;BR /&gt;access-group OUTSIDE in interface outside&lt;BR /&gt;access-group OUTSIDE2 in interface outside2&lt;BR /&gt;route outside 0.0.0.0 0.0.0.0 75.XX.XX.XX 1&lt;BR /&gt;route outside 75.XX.XX.XX 255.255.255.255 192.168.16.22 1&lt;BR /&gt;route outside 192.168.0.0 255.255.0.0 192.168.16.1 1&lt;BR /&gt;timeout xlate 3:00:00&lt;BR /&gt;timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02&lt;BR /&gt;timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00&lt;BR /&gt;timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00&lt;BR /&gt;timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute&lt;BR /&gt;dynamic-access-policy-record DfltAccessPolicy&lt;BR /&gt;http 192.168.1.0 255.255.255.0 inside&lt;BR /&gt;no snmp-server location&lt;BR /&gt;no snmp-server contact&lt;BR /&gt;snmp-server enable traps snmp authentication linkup linkdown coldstart&lt;BR /&gt;crypto ipsec security-association lifetime seconds 28800&lt;BR /&gt;crypto ipsec security-association lifetime kilobytes 4608000&lt;BR /&gt;telnet timeout 5&lt;BR /&gt;ssh timeout 5&lt;BR /&gt;console timeout 0&lt;BR /&gt;dhcpd dns 10.10.16.10&lt;BR /&gt;dhcpd domain sjcca.ad&lt;BR /&gt;!&lt;BR /&gt;threat-detection basic-threat&lt;BR /&gt;threat-detection statistics access-list&lt;BR /&gt;no threat-detection statistics tcp-intercept&lt;BR /&gt;!&lt;BR /&gt;class-map inspection_default&lt;BR /&gt;match default-inspection-traffic&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;policy-map type inspect dns preset_dns_map&lt;BR /&gt;parameters&lt;BR /&gt;message-length maximum 512&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;BR /&gt;class inspection_default&lt;BR /&gt;inspect dns preset_dns_map &lt;BR /&gt;inspect ftp &lt;BR /&gt;inspect h323 h225 &lt;BR /&gt;inspect h323 ras &lt;BR /&gt;inspect rsh &lt;BR /&gt;inspect rtsp &lt;BR /&gt;inspect esmtp &lt;BR /&gt;inspect sqlnet &lt;BR /&gt;inspect skinny &lt;BR /&gt;inspect sunrpc &lt;BR /&gt;inspect xdmcp &lt;BR /&gt;inspect sip &lt;BR /&gt;inspect netbios &lt;BR /&gt;inspect tftp &lt;BR /&gt;!&lt;BR /&gt;service-policy global_policy global&lt;BR /&gt;prompt hostname context &lt;BR /&gt;Cryptochecksum:55e8206ac7f658b009416f6…&lt;BR /&gt;: end&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using the basic license in this ASA, and since VLAN2 and VLAN3 are both outside it's fine for them to not pass traffic to each other. VLAN1 can pass traffic to VLAN2 no problem, and get replies back no problem. However when I try to pass traffic to an address in VLAN3 I get the timed out errors both on ICMP and IP traffic. HOWEVER: From within the ASA I can ping addresses on all 3 VLAN's. What am I missing to allow traffic from VLAN1 access to resources on both VLAN2 and VLAN3?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:44:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715063#M560892</guid>
      <dc:creator>liskoe</dc:creator>
      <dc:date>2019-03-11T20:44:29Z</dc:date>
    </item>
    <item>
      <title>VLAN3 Routing Issues ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715064#M560893</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A couple of thoughts here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Vlan1&lt;/P&gt;&lt;P&gt;nameif inside&lt;/P&gt;&lt;P&gt;security-level 100&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ip address 10.10.16.1 255.0.0.0 &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure why you are using a /8 for the inside interface, as this would include the IP that is assigned to VLAN3 (10.1.6.36/16, which falls within 10.0.0.0/8).&amp;nbsp; VLAN1 and VLAN3 should not be in the same subnet, this needs to be corrected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;nat (inside) 1 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue is you are requiring NAT to take place when traffic is originated from behind the inside interface.&amp;nbsp; You can resolve the issue by PAT'ing traffic to the DMZ interface:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside2) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With this configuration, when traffic from inside is destined to a host behind outside2, the traffic will be PAT'ed to the outside2 interface IP of 10.1.6.36.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you would like the IP to not be PAT'ed, then you can use this static NAT configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside2)&amp;nbsp; &lt;NETWORK_ID of="" inside=""&gt; &lt;NETWORK_ID of="" inside=""&gt; mask &lt;SUBNET mask=""&gt;&lt;/SUBNET&gt;&lt;/NETWORK_ID&gt;&lt;/NETWORK_ID&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will allow traffic to pass from VLAN1 to VLAN3 using its own IP address.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Jun 2011 20:04:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715064#M560893</guid>
      <dc:creator>Allen P Chen</dc:creator>
      <dc:date>2011-06-13T20:04:09Z</dc:date>
    </item>
    <item>
      <title>VLAN3 Routing Issues ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715065#M560894</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This has been a very helpful answer.&amp;nbsp;&amp;nbsp; I'll be trying out your suggestions this afternoon and I'll reply back if this resolved my issues.&amp;nbsp;&amp;nbsp; I hadn't thought of the subnet issues on the VLAN1 interface.&amp;nbsp; (Admittedly I'm weak when it comes to mastering subnets) If I was to stay with the 10.10 scheme would you suggest that I go with 10.10.16.x/24 or should i consider overhauling the whole thing (Now is the time to do so) and go with something smaller like 172.16.0.0/12?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Jun 2011 20:18:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715065#M560894</guid>
      <dc:creator>liskoe</dc:creator>
      <dc:date>2011-06-13T20:18:31Z</dc:date>
    </item>
    <item>
      <title>VLAN3 Routing Issues ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715066#M560895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt; If I was to stay with the 10.10 scheme would you suggest that I go with&amp;nbsp; 10.10.16.x/24 or should i consider overhauling the whole thing (Now is&amp;nbsp; the time to do so) and go with something smaller like 172.16.0.0/12?&lt;/PRE&gt;&lt;P&gt;With subnetting, the important number is the number behind the slash (/).&amp;nbsp; In your example, 10.10.16.x/24 is actually smaller than 172.16.0.0/12.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10.10.16.x/24 will allow 254 hosts within the subnet, while 172.16.0.0/12 will allow 1,048,574 hosts within the subnet.&amp;nbsp; You can use an online subnet calculator to check:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.subnet-calculator.com/"&gt;http://www.subnet-calculator.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The number of hosts that needs to be supported in a subnet should determine the subnet mask to use.&amp;nbsp; For most small networks, /24 is enough.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Jun 2011 20:29:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715066#M560895</guid>
      <dc:creator>Allen P Chen</dc:creator>
      <dc:date>2011-06-13T20:29:03Z</dc:date>
    </item>
    <item>
      <title>VLAN3 Routing Issues ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715067#M560896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you supply us with:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show version&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;output?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is licensing issue that might be at work here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Jun 2011 21:02:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715067#M560896</guid>
      <dc:creator>mile.ljepojevic</dc:creator>
      <dc:date>2011-06-13T21:02:29Z</dc:date>
    </item>
    <item>
      <title>VLAN3 Routing Issues ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715068#M560897</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Cisco Adaptive Security Appliance Software Version 8.0(4)&lt;BR /&gt;Device Manager Version 6.1(5)51&lt;/P&gt;&lt;P&gt;Compiled on Thu 07-Aug-08 20:53 by builders&lt;BR /&gt;System image file is "disk0:/asa804-k8.bin"&lt;BR /&gt;Config file at boot was "startup-config"&lt;/P&gt;&lt;P&gt;ciscoasa up 1 day 2 hours&lt;/P&gt;&lt;P&gt;Hardware:&amp;nbsp;&amp;nbsp; ASA5505, 256 MB RAM, CPU Geode 500 MHz&lt;BR /&gt;Internal ATA Compact Flash, 128MB&lt;BR /&gt;BIOS Flash M50FW080 @ 0xffe00000, 1024KB&lt;/P&gt;&lt;P&gt;Encryption hardware device : Cisco ASA-5505 on-board accelerator (revision 0x0)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Boot microcode&amp;nbsp;&amp;nbsp; : CN1000-MC-BOOT-2.00&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSL/IKE microcode: CNLite-MC-SSLm-PLUS-2.03&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IPSec microcode&amp;nbsp; : CNlite-MC-IPSECm-MAIN-2.05&lt;BR /&gt; 0: Int: Internal-Data0/0&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0023.XXXX.XXXX, irq 11&lt;BR /&gt; 1: Ext: Ethernet0/0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0023.XXXX.XXXX, irq 255&lt;BR /&gt; 2: Ext: Ethernet0/1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0023.XXXX.XXXX, irq 255&lt;BR /&gt; 3: Ext: Ethernet0/2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0023.XXXX.XXXX, irq 255&lt;BR /&gt; 4: Ext: Ethernet0/3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0023.XXXX.XXXX, irq 255&lt;BR /&gt; 5: Ext: Ethernet0/4&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0023.XXXX.XXXX, irq 255&lt;BR /&gt; 6: Ext: Ethernet0/5&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0023.XXXX.XXXX, irq 255&lt;BR /&gt; 7: Ext: Ethernet0/6&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0023.XXXX.XXXX, irq 255&lt;BR /&gt; 8: Ext: Ethernet0/7&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0023.XXXX.XXXX, irq 255&lt;BR /&gt; 9: Int: Internal-Data0/1&amp;nbsp;&amp;nbsp;&amp;nbsp; : address is 0000.XXXX.XXXX, irq 255&lt;BR /&gt;10: Int: Not used&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : irq 255&lt;BR /&gt;11: Int: Not used&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : irq 255&lt;/P&gt;&lt;P&gt;Licensed features for this platform:&lt;BR /&gt;Maximum Physical Interfaces&amp;nbsp; : 8&lt;BR /&gt;VLANs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 3, DMZ Restricted&lt;BR /&gt;Inside Hosts&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 50&lt;BR /&gt;Failover&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&lt;BR /&gt;VPN-DES&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&lt;BR /&gt;VPN-3DES-AES&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&lt;BR /&gt;VPN Peers&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 10&lt;BR /&gt;WebVPN Peers&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 2&lt;BR /&gt;Dual ISPs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&lt;BR /&gt;VLAN Trunk Ports&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 0&lt;BR /&gt;AnyConnect for Mobile&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&lt;BR /&gt;AnyConnect for Linksys phone : Disabled&lt;BR /&gt;Advanced Endpoint Assessment : Disabled&lt;BR /&gt;UC Proxy Sessions&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 2&lt;/P&gt;&lt;P&gt;This platform has a Base license.&lt;/P&gt;&lt;P&gt;Serial Number: JMXXXXXXXXXXXX&lt;BR /&gt;Running Activation Key: XXXXXXXXXXXXXXXXXXXXXXXXX&lt;/P&gt;&lt;P&gt;Configuration register is 0x1&lt;BR /&gt;Configuration last modified by enable_15 at 16:37:44.077 UTC Mon Jun 13 2011&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jun 2011 00:01:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715068#M560897</guid>
      <dc:creator>liskoe</dc:creator>
      <dc:date>2011-06-14T00:01:56Z</dc:date>
    </item>
    <item>
      <title>VLAN3 Routing Issues ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715069#M560898</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you have license issues...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/int5505.html"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/int5505.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know it's an old one, but nothing changed as far as I know. That is not full DMZ, so it cannot initate traffic, it can only reply for request coming from other 2 interaces (or something like that).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, don't mix 10.0.0.0/8 with 10.1.0.0/16 networks. so change your 255.0.0.0 to 255.255.0.0 mask, but I don't think it your issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jun 2011 00:13:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715069#M560898</guid>
      <dc:creator>mile.ljepojevic</dc:creator>
      <dc:date>2011-06-14T00:13:34Z</dc:date>
    </item>
    <item>
      <title>VLAN3 Routing Issues ASA5505</title>
      <link>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715070#M560899</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Thanks to all the great answers everyone.&amp;nbsp; It is indeed the license issue.&amp;nbsp;&amp;nbsp; Sadly, I don't have the $500 to upgrade so I'm trying a different solution which is proving....interesting.&amp;nbsp;&amp;nbsp; I'll be posting a different discussion in the proper section for help with that issue. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Jun 2011 01:17:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan3-routing-issues-asa5505/m-p/1715070#M560899</guid>
      <dc:creator>liskoe</dc:creator>
      <dc:date>2011-06-18T01:17:13Z</dc:date>
    </item>
  </channel>
</rss>

