<?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: disabling nat after the pix in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406031#M530919</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thaier&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This article discusses port security on the 2950 switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/hw/switches/ps4916/products_configuration_guide_chapter09186a008017e531.html#1038501" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/hw/switches/ps4916/products_configuration_guide_chapter09186a008017e531.html#1038501&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Although, on second thought - All of the source MAC addresses will be the router anyway. MAC src/dst addresses are always the forwarding and receiving hosts which in your case is the unwanted router and your firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could preconfigure every port with the proper mac address, but that would quickly become far to complex and administratively intense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry - I can't think of an easy way to do this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Nov 2005 16:46:09 GMT</pubDate>
    <dc:creator>brad</dc:creator>
    <dc:date>2005-11-15T16:46:09Z</dc:date>
    <item>
      <title>disabling nat after the pix</title>
      <link>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406026#M530912</link>
      <description>&lt;P&gt;dear sir,&lt;/P&gt;&lt;P&gt;I want to prevent users from connecting routers after my 525 pix firewall,through disabling nat for them or other way?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I appreciate your help in advanced.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thank you,&lt;/P&gt;&lt;P&gt;thaier&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:30:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406026#M530912</guid>
      <dc:creator>thaier1978</dc:creator>
      <dc:date>2020-02-21T08:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: disabling nat after the pix</title>
      <link>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406027#M530913</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you have a public address on the inside network, and you want the inside hosts to go out to the outside without translation, you can disable NAT. You would also need to change the static command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 0 175.1.1.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;If you are using ACLs in PIX software versions 5.0.1 and later, use the following commands.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list 103 permit ip 175.1.1.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list 103&lt;/P&gt;&lt;P&gt;This command disables NAT for the 175.1.1.0 network. The static command for the web server would be changed as shown below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside, outside) 175.1.1.254 175.1.1.254&lt;/P&gt;&lt;P&gt;The following command defines the conduit for the web server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;conduit permit tcp host 175.1.1.254 eq www any&lt;/P&gt;&lt;P&gt;If you are using ACLs in PIX software versions 5.0.1 and later, use the following commannds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list 102 permit tcp any host 175.1.1.254 eq www&lt;/P&gt;&lt;P&gt;access-group 102 in interface outside&lt;/P&gt;&lt;P&gt;Note that the difference between using nat 0 with specifying network/mask as opposed to using an ACL that uses a network/mask that permits initiation of connections from inside only. The use of ACLs permits initiation of connections by inbound or outbound traffic. The PIX interfaces should be in different subnets to avoid reachability issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Nov 2005 22:08:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406027#M530913</guid>
      <dc:creator>pradeepde</dc:creator>
      <dc:date>2005-11-14T22:08:55Z</dc:date>
    </item>
    <item>
      <title>Re: disabling nat after the pix</title>
      <link>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406028#M530914</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear pradeepde &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know how disable the NAT on my pix, I just want to disable the NAT after the pix and keep my pix doning NATing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is that some of my inside users are using routers to establish asmall network inside my network, I want to prevent that with out affecting the other users that are using DHCP to gane their IPs and NATed through the PIX to the outside????&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I appreciate your kind reply...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Thaier&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2005 05:55:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406028#M530914</guid>
      <dc:creator>thaier1978</dc:creator>
      <dc:date>2005-11-15T05:55:45Z</dc:date>
    </item>
    <item>
      <title>Re: disabling nat after the pix</title>
      <link>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406029#M530915</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are two ways of looking at this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where your LAN is 10.1.1.0/24&lt;/P&gt;&lt;P&gt;Where your WAN is 99.99.99.0/24&lt;/P&gt;&lt;P&gt;Where the Routers WAN is 10.1.1.0/24&lt;/P&gt;&lt;P&gt;Where the Routers LAN is 10.1.2.0/24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First perspective:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are working with simple nat configurations on the firewall such as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 99 10.1.1.0 255.255.255.0&lt;/P&gt;&lt;P&gt;global (outside) 99 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this example, users would not be able to configure a router behind your firewall as only the inside LAN addresses are NATed by the firewall. The 10.1.2.0/24 subnet is not valid for NAT translations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Second Perspective:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the router has NAT configured and translates address from 10.1.2.0/24 to 10.1.1.x and then forwards them to the firewall for a second translation (double NAT), then the connection will succeed. You can't really do much about this without somehow identifying valid source addresses or sessions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Consider configuring all of the switch ports to only allow a single mac address? - Presumably the router would be the first and all other connections would fail.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2005 07:54:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406029#M530915</guid>
      <dc:creator>brad</dc:creator>
      <dc:date>2005-11-15T07:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: disabling nat after the pix</title>
      <link>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406030#M530916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;how can I configure the switch ports to only allow a single mac address, Bythe way I have Cisco C2950 switches???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thaier&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2005 11:40:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406030#M530916</guid>
      <dc:creator>thaier1978</dc:creator>
      <dc:date>2005-11-15T11:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: disabling nat after the pix</title>
      <link>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406031#M530919</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thaier&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This article discusses port security on the 2950 switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/hw/switches/ps4916/products_configuration_guide_chapter09186a008017e531.html#1038501" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/hw/switches/ps4916/products_configuration_guide_chapter09186a008017e531.html#1038501&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Although, on second thought - All of the source MAC addresses will be the router anyway. MAC src/dst addresses are always the forwarding and receiving hosts which in your case is the unwanted router and your firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could preconfigure every port with the proper mac address, but that would quickly become far to complex and administratively intense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry - I can't think of an easy way to do this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2005 16:46:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/disabling-nat-after-the-pix/m-p/406031#M530919</guid>
      <dc:creator>brad</dc:creator>
      <dc:date>2005-11-15T16:46:09Z</dc:date>
    </item>
  </channel>
</rss>

