<?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 PIX515 NATing VLAN ? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix515-nating-vlan/m-p/1427998#M659407</link>
    <description>&lt;P&gt;I am have problems connecting to my webpage (NAT) after setting up VLANing of my network. I have a PIX515 that is connected to a 4507 switch. I have everything VLANed off at the 4507 and divided off into10.20.0.0 /20 subnets. 10.20.0.0 - 10.20.15.255 is the original network work that was first broken down and everyone was place there for the big division and everything was working fine. But now only 10.20.0.0 - 10.20.15.255 can connect. All the other subnets can get to the internet and do work as normal execpt get to the NAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a VLAN 10.10.10.0/24 that was running with the original VLAN and was able to connect to the NAT. When all the other subnets were unable to connect I tried to remove global (DMZ) 1 192.168.254.254 and replace with global (DMZ) 1 192.168.254.100 - 192.168.254.200 netmask 255.255.255.0. That did not work and blocked me from accessing NAT. I placed global (DMZ) 1 192.168.254.254 back in and I still am unable to connect from my own subnet. Again everything is working except NAT connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there something special I need to do since the VLAN router is behind the firewall? I have been working on this for several days and stumped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firewall route table&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; outside 0.0.0.0 0.0.0.0 10.20.1.1 1 OTHER static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inside 10.20.0.0 255.255.240.0 10.20.5.254 1 CONNECT static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inside 10.20.0.0 255.255.0.0 10.20.2.1 1 OTHER static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; outside 10.20.1.0 255.255.255.0 10.20.1.2 1 CONNECT static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inside 10.10.10.0 255.255.255.0 10.20.2.1 1 OTHER static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DMZ 192.168.254.0 255.255.255.0 192.168.254.1 1 CONNECT static&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip address outside 10.20.1.2 255.255.255.0&lt;BR /&gt;ip address inside 10.20.5.254 255.255.240.0&lt;BR /&gt;ip address DMZ 192.168.254.1 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 1 10.20.2.2-10.20.2.254 netmask 255.255.255.0&lt;BR /&gt;global (outside) 1 10.20.3.2-10.20.3.254 netmask 255.255.255.0&lt;BR /&gt;global (outside) 1 10.20.4.2-10.20.4.254 netmask 255.255.255.0&lt;BR /&gt;global (outside) 1 10.20.5.2-10.20.5.254 netmask 255.255.255.0&lt;BR /&gt;global (outside) 1 interface&lt;BR /&gt;global (outside) 7 webmail&lt;BR /&gt;global (DMZ) 1 192.168.254.254&lt;BR /&gt;nat (inside) 7 exchange 255.255.255.255 0 0&lt;BR /&gt;nat (inside) 1 0.0.0.0 0.0.0.0 0 0&lt;BR /&gt;nat (DMZ) 1 192.168.254.0 255.255.255.0 0 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4507 routes&lt;/P&gt;&lt;P&gt;Gateway of last resort is 10.20.5.254 to network 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.192.0/24 is directly connected, Vlan193&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.208.0/24 is directly connected, Vlan209&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.128.0/24 is directly connected, Vlan129&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.247.0/24 is directly connected, Vlan247&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.144.0/24 is directly connected, Vlan145&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.10.0/24 is directly connected, Vlan11&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.160.0/24 is directly connected, Vlan161&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.0.0.0/8 is variably subnetted, 13 subnets, 2 masks&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.32.0/20 is directly connected, Vlan32&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.0.0/20 is directly connected, Vlan10&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.64.0/20 is directly connected, Vlan64&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.160.0/20 is directly connected, Vlan160&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.176.0/20 is directly connected, Vlan176&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.10.10.0/24 is directly connected, Vlan55&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.128.0/20 is directly connected, Vlan128&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.144.0/20 is directly connected, Vlan144&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.192.0/20 is directly connected, Vlan192&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.208.0/20 is directly connected, Vlan208&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.34.0/24 is directly connected, Vlan1&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.32.0/24 is directly connected, Vlan33&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.252.0/30 is subnetted, 1 subnets&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.252.4 is directly connected, FastEthernet5/48&lt;BR /&gt;S*&amp;nbsp;&amp;nbsp; 0.0.0.0/0 [1/0] via 10.20.5.254&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;192.168.x.x/24 are the network management devices.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 18:27:28 GMT</pubDate>
    <dc:creator>jmaurer1205</dc:creator>
    <dc:date>2019-03-11T18:27:28Z</dc:date>
    <item>
      <title>PIX515 NATing VLAN ?</title>
      <link>https://community.cisco.com/t5/network-security/pix515-nating-vlan/m-p/1427998#M659407</link>
      <description>&lt;P&gt;I am have problems connecting to my webpage (NAT) after setting up VLANing of my network. I have a PIX515 that is connected to a 4507 switch. I have everything VLANed off at the 4507 and divided off into10.20.0.0 /20 subnets. 10.20.0.0 - 10.20.15.255 is the original network work that was first broken down and everyone was place there for the big division and everything was working fine. But now only 10.20.0.0 - 10.20.15.255 can connect. All the other subnets can get to the internet and do work as normal execpt get to the NAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a VLAN 10.10.10.0/24 that was running with the original VLAN and was able to connect to the NAT. When all the other subnets were unable to connect I tried to remove global (DMZ) 1 192.168.254.254 and replace with global (DMZ) 1 192.168.254.100 - 192.168.254.200 netmask 255.255.255.0. That did not work and blocked me from accessing NAT. I placed global (DMZ) 1 192.168.254.254 back in and I still am unable to connect from my own subnet. Again everything is working except NAT connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there something special I need to do since the VLAN router is behind the firewall? I have been working on this for several days and stumped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firewall route table&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; outside 0.0.0.0 0.0.0.0 10.20.1.1 1 OTHER static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inside 10.20.0.0 255.255.240.0 10.20.5.254 1 CONNECT static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inside 10.20.0.0 255.255.0.0 10.20.2.1 1 OTHER static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; outside 10.20.1.0 255.255.255.0 10.20.1.2 1 CONNECT static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inside 10.10.10.0 255.255.255.0 10.20.2.1 1 OTHER static&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DMZ 192.168.254.0 255.255.255.0 192.168.254.1 1 CONNECT static&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip address outside 10.20.1.2 255.255.255.0&lt;BR /&gt;ip address inside 10.20.5.254 255.255.240.0&lt;BR /&gt;ip address DMZ 192.168.254.1 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;global (outside) 1 10.20.2.2-10.20.2.254 netmask 255.255.255.0&lt;BR /&gt;global (outside) 1 10.20.3.2-10.20.3.254 netmask 255.255.255.0&lt;BR /&gt;global (outside) 1 10.20.4.2-10.20.4.254 netmask 255.255.255.0&lt;BR /&gt;global (outside) 1 10.20.5.2-10.20.5.254 netmask 255.255.255.0&lt;BR /&gt;global (outside) 1 interface&lt;BR /&gt;global (outside) 7 webmail&lt;BR /&gt;global (DMZ) 1 192.168.254.254&lt;BR /&gt;nat (inside) 7 exchange 255.255.255.255 0 0&lt;BR /&gt;nat (inside) 1 0.0.0.0 0.0.0.0 0 0&lt;BR /&gt;nat (DMZ) 1 192.168.254.0 255.255.255.0 0 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4507 routes&lt;/P&gt;&lt;P&gt;Gateway of last resort is 10.20.5.254 to network 0.0.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.192.0/24 is directly connected, Vlan193&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.208.0/24 is directly connected, Vlan209&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.128.0/24 is directly connected, Vlan129&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.247.0/24 is directly connected, Vlan247&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.144.0/24 is directly connected, Vlan145&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.10.0/24 is directly connected, Vlan11&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.160.0/24 is directly connected, Vlan161&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.0.0.0/8 is variably subnetted, 13 subnets, 2 masks&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.32.0/20 is directly connected, Vlan32&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.0.0/20 is directly connected, Vlan10&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.64.0/20 is directly connected, Vlan64&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.160.0/20 is directly connected, Vlan160&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.176.0/20 is directly connected, Vlan176&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.10.10.0/24 is directly connected, Vlan55&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.128.0/20 is directly connected, Vlan128&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.144.0/20 is directly connected, Vlan144&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.192.0/20 is directly connected, Vlan192&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.20.208.0/20 is directly connected, Vlan208&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.34.0/24 is directly connected, Vlan1&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.32.0/24 is directly connected, Vlan33&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.252.0/30 is subnetted, 1 subnets&lt;BR /&gt;C&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.252.4 is directly connected, FastEthernet5/48&lt;BR /&gt;S*&amp;nbsp;&amp;nbsp; 0.0.0.0/0 [1/0] via 10.20.5.254&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;192.168.x.x/24 are the network management devices.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:27:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix515-nating-vlan/m-p/1427998#M659407</guid>
      <dc:creator>jmaurer1205</dc:creator>
      <dc:date>2019-03-11T18:27:28Z</dc:date>
    </item>
    <item>
      <title>Re: PIX515 NATing VLAN ?</title>
      <link>https://community.cisco.com/t5/network-security/pix515-nating-vlan/m-p/1427999#M659410</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you provide the full configuation from both PIX and Switch?&lt;/P&gt;&lt;P&gt;What version your PIX is running?&lt;/P&gt;&lt;P&gt;When you were failed to connect to web server in DMZ network from inside, what log message did you see?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Aug 2010 17:19:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix515-nating-vlan/m-p/1427999#M659410</guid>
      <dc:creator>Yudong Wu</dc:creator>
      <dc:date>2010-08-18T17:19:28Z</dc:date>
    </item>
  </channel>
</rss>

