<?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 Re: PIX and Vlans. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165554#M612719</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list routing permit ip ...  The "ip" was missing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure about the necessity to have the access-list permit ip 20.20.20.0 255.255.255.0 10.10.10.0 255.255.255.0 but i suggest you keep it for test purpose, and when you will get perfect routing between both VLAN, try to remove this line to check the behavior without it.  Also, i'm interested to know the result about this issue, if you can post later the result, i will appreciate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Aug 2003 17:12:04 GMT</pubDate>
    <dc:creator>bdube</dc:creator>
    <dc:date>2003-08-21T17:12:04Z</dc:date>
    <item>
      <title>PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165545#M612710</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have one question that as to do with the way that vlans work with PIX, that is, when it&amp;#146;s configured in PIX.&lt;/P&gt;&lt;P&gt;I have a PIX that, beside other things, as two (2) vlans configured on it, in the same interface (inside).&lt;/P&gt;&lt;P&gt;But the problem is that these two vlans cannot communicate between them. &lt;/P&gt;&lt;P&gt;I put a router in one vlan and another router in the other vlan. Then I tray to do a simple connection test between them (a ping between them) and I cannot succeed.&lt;/P&gt;&lt;P&gt;I read some documentation from Cisco and, apparently, in theory, they say that I can.&lt;/P&gt;&lt;P&gt;As any one could tell me, why cannot?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:56:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165545#M612710</guid>
      <dc:creator>rcapao</dc:creator>
      <dc:date>2020-02-21T06:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165546#M612711</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rui,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First, you only need 1 router to route traffics between both VLAN, not 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Second, by default, PIX doesn't route traffic between VLANs which would result to a security breach.  If it's really what you are looking for, make PIX routing between both, you have to configure this manually.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have some routers, why don't you use them between LANs, not VLANs, and connect 1 Eth port to the PIX, this port can be a router port or switch port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Aug 2003 12:30:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165546#M612711</guid>
      <dc:creator>bdube</dc:creator>
      <dc:date>2003-08-19T12:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165547#M612712</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thanks for the replay.&lt;/P&gt;&lt;P&gt;But the thing is like this.&lt;/P&gt;&lt;P&gt;The question that I put as to do with a lab.&lt;/P&gt;&lt;P&gt;I talked about the two router as an example. I used these two routers to have something to connect to between the two Vlans.&lt;/P&gt;&lt;P&gt;In my opinion, it was the simplest way to do a test. Nothing more.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Aug 2003 13:15:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165547#M612712</guid>
      <dc:creator>rcapao</dc:creator>
      <dc:date>2003-08-19T13:15:50Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165548#M612713</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ben,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you said that if I which to have routing, in the PIX, between the two Vlans I had to route traffic between them. I had to do that in the PIX and manually.&lt;/P&gt;&lt;P&gt;How can I do that?&lt;/P&gt;&lt;P&gt;Can you tell me, or some one can tell me? &lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Rui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Aug 2003 15:07:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165548#M612713</guid>
      <dc:creator>rcapao</dc:creator>
      <dc:date>2003-08-19T15:07:06Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165549#M612714</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can try "NAT (inside) 0 access-list acl_id"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The access-list must permit ip addresses coming from any VLANs with destination to the other VLANs. Example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list full-routing permit ip 10.1.0.0 255.0.0.0 10.2.0.0 255.0.0.0&lt;/P&gt;&lt;P&gt;access-list full-routing permit ip 10.2.0.0 255.0.0.0 10.1.0.0 255.0.0.0&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list full-routing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the syntax to be sure because i have write it fast.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Aug 2003 17:35:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165549#M612714</guid>
      <dc:creator>bdube</dc:creator>
      <dc:date>2003-08-19T17:35:10Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165550#M612715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had applied that solution to the PIX, but that don&amp;#146;t worked.&lt;/P&gt;&lt;P&gt;Did I miss something?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2003 08:12:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165550#M612715</guid>
      <dc:creator>rcapao</dc:creator>
      <dc:date>2003-08-21T08:12:40Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165551#M612716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rui, this should work fine.  Any chance you can attac the relevant config info?  (interface settings and security levels, nat/global or statics, and access-lists)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2003 09:56:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165551#M612716</guid>
      <dc:creator>scoclayton</dc:creator>
      <dc:date>2003-08-21T09:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165552#M612717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the configuration that I&amp;#146;m using in the PIX is like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX Version 6.3(1)&lt;/P&gt;&lt;P&gt;interface ethernet0 10baset&lt;/P&gt;&lt;P&gt;interface ethernet1 10baset&lt;/P&gt;&lt;P&gt;interface ethernet1 vlan2 physical&lt;/P&gt;&lt;P&gt;interface ethernet1 vlan3 logical&lt;/P&gt;&lt;P&gt;interface ethernet2 10baset&lt;/P&gt;&lt;P&gt;nameif ethernet0 outside security0&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;nameif ethernet2 DMZ security20&lt;/P&gt;&lt;P&gt;nameif vlan3 intf3 security99&lt;/P&gt;&lt;P&gt;enable password Yxxxxx encrypted&lt;/P&gt;&lt;P&gt;passwd xxxxxxx encrypted&lt;/P&gt;&lt;P&gt;hostname PIX-LAB&lt;/P&gt;&lt;P&gt;domain-name porto.convex.pt&lt;/P&gt;&lt;P&gt;fixup protocol ftp 21&lt;/P&gt;&lt;P&gt;fixup protocol h323 h225 1720&lt;/P&gt;&lt;P&gt;fixup protocol h323 ras 1718-1719&lt;/P&gt;&lt;P&gt;fixup protocol http 80&lt;/P&gt;&lt;P&gt;fixup protocol ils 389&lt;/P&gt;&lt;P&gt;fixup protocol rsh 514&lt;/P&gt;&lt;P&gt;fixup protocol rtsp 554&lt;/P&gt;&lt;P&gt;fixup protocol sip 5060&lt;/P&gt;&lt;P&gt;fixup protocol sip udp 5060&lt;/P&gt;&lt;P&gt;fixup protocol skinny 2000&lt;/P&gt;&lt;P&gt;fixup protocol smtp 25&lt;/P&gt;&lt;P&gt;fixup protocol sqlnet 1521&lt;/P&gt;&lt;P&gt;names&lt;/P&gt;&lt;P&gt;access-list routing remark ****************** ACL para routing *****************&lt;/P&gt;&lt;P&gt;access-list routing permit 10.10.10.0 255.255.255.0 20.20.20.0 255.255.255.0&lt;/P&gt;&lt;P&gt;access-list routing permit 20.20.20.0 255.255.255.0 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;access-list routing deny tcp any any&lt;/P&gt;&lt;P&gt;access-list routing deny udp any any&lt;/P&gt;&lt;P&gt;access-list routing remark ***********************************&lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;mtu DMZ 1500&lt;/P&gt;&lt;P&gt;ip address outside xxx.xxx.xxx.xxx 255.255.255.0&lt;/P&gt;&lt;P&gt;ip address inside 10.10.10.254 255.255.255.0&lt;/P&gt;&lt;P&gt;ip address DMZ 50.50.50.254 255.255.255.0&lt;/P&gt;&lt;P&gt;ip address intf3 20.20.20.254 255.255.255.0&lt;/P&gt;&lt;P&gt;ip audit info action alarm&lt;/P&gt;&lt;P&gt;ip audit attack action alarm&lt;/P&gt;&lt;P&gt;no failover&lt;/P&gt;&lt;P&gt;failover timeout 0:00:00&lt;/P&gt;&lt;P&gt;failover poll 15&lt;/P&gt;&lt;P&gt;no failover ip address outside&lt;/P&gt;&lt;P&gt;no failover ip address inside&lt;/P&gt;&lt;P&gt;no failover ip address DMZ&lt;/P&gt;&lt;P&gt;no failover ip address intf3&lt;/P&gt;&lt;P&gt;pdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list routing&lt;/P&gt;&lt;P&gt;nat (inside) 1 0.0.0.0 0.0.0.0 0 0&lt;/P&gt;&lt;P&gt;nat (DMZ) 1 0.0.0.0 0.0.0.0 0 0&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 172.16.1.1 1&lt;/P&gt;&lt;P&gt;timeout xlate 3:00:00&lt;/P&gt;&lt;P&gt;timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00&lt;/P&gt;&lt;P&gt;timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00&lt;/P&gt;&lt;P&gt;timeout uauth 0:05:00 absolute&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ protocol tacacs+&lt;/P&gt;&lt;P&gt;aaa-server RADIUS protocol radius&lt;/P&gt;&lt;P&gt;aaa-server LOCAL protocol local&lt;/P&gt;&lt;P&gt;aaa-server ACS protocol tacacs+&lt;/P&gt;&lt;P&gt;no snmp-server location&lt;/P&gt;&lt;P&gt;no snmp-server contact&lt;/P&gt;&lt;P&gt;snmp-server community public&lt;/P&gt;&lt;P&gt;no snmp-server enable traps&lt;/P&gt;&lt;P&gt;floodguard enable&lt;/P&gt;&lt;P&gt;console timeout 0&lt;/P&gt;&lt;P&gt;terminal width 80&lt;/P&gt;&lt;P&gt;Cryptochecksum:xxxx&lt;/P&gt;&lt;P&gt;: end&lt;/P&gt;&lt;P&gt;[OK]&lt;/P&gt;&lt;P&gt;PIX-LAB(config)#&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see it&amp;#146;s a simple configuration.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2003 13:10:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165552#M612717</guid>
      <dc:creator>rcapao</dc:creator>
      <dc:date>2003-08-21T13:10:17Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165553#M612718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Rui, looks good.  A couple of comments:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These entries in the ACL are not needed and can be removed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list routing permit 20.20.20.0 255.255.255.0 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;access-list routing deny tcp any any&lt;/P&gt;&lt;P&gt;access-list routing deny udp any any &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With this config in place, you should be able to get from a host on the 10.10.10.0 network to a host on the 20.20.20.0 network (assuming default gateways on the host are correct).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One item to note here is that you do have a vlan assigned to the physical interface (which is fine).  The important item to remember is that when you do this, the PIX will no longer accept packets from the native VLAN on the switch so make sure that all packets coming in on vlan2 are tagged as such.  A 'sh int' may help in determining any errors such as this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2003 13:23:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165553#M612718</guid>
      <dc:creator>scoclayton</dc:creator>
      <dc:date>2003-08-21T13:23:05Z</dc:date>
    </item>
    <item>
      <title>Re: PIX and Vlans.</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165554#M612719</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list routing permit ip ...  The "ip" was missing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure about the necessity to have the access-list permit ip 20.20.20.0 255.255.255.0 10.10.10.0 255.255.255.0 but i suggest you keep it for test purpose, and when you will get perfect routing between both VLAN, try to remove this line to check the behavior without it.  Also, i'm interested to know the result about this issue, if you can post later the result, i will appreciate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2003 17:12:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-vlans/m-p/165554#M612719</guid>
      <dc:creator>bdube</dc:creator>
      <dc:date>2003-08-21T17:12:04Z</dc:date>
    </item>
  </channel>
</rss>

