<?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: New ASA installation in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889918#M955513</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; What you can do is, just check the gateway of that 192.168.1.0 clients it should be 192.168.1.22 if that clients have different gateway address (another router) then that router should have route back to the ASA for your 192.168.10.0 network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for an example in the router command should be&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip route 192.168.10.0 255.255.255.0 192.168.1.22&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Feb 2008 18:53:07 GMT</pubDate>
    <dc:creator>patil_pritam</dc:creator>
    <dc:date>2008-02-05T18:53:07Z</dc:date>
    <item>
      <title>New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889912#M955504</link>
      <description>&lt;P&gt;I have a new ASA 5510 that is behind our router/firewall.  I am having some problems with configuration and not sure where I am hung up. I can't ping the internal Lan, 192.168.1. addresses. I have attached my configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:59:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889912#M955504</guid>
      <dc:creator>jglover72</dc:creator>
      <dc:date>2019-03-11T11:59:29Z</dc:date>
    </item>
    <item>
      <title>Re: New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889913#M955507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seeing as you're not natting, the clients on 192.168.1.0 that you are trying to ping would have to have a route to the 192.168.10.0 network via the outside interface of the ASA, 192.168.1.22.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, this route stament is not correct as 192.168.1.0 is on the outside of the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route inside 192.168.0.0 255.255.0.0 192.168.10.1 1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Feb 2008 18:23:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889913#M955507</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-02-05T18:23:52Z</dc:date>
    </item>
    <item>
      <title>Re: New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889914#M955508</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;copy paste this two lines&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list acl_in permit ip any any&lt;/P&gt;&lt;P&gt;access-group acl_in in interface inside&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Feb 2008 18:30:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889914#M955508</guid>
      <dc:creator>patil_pritam</dc:creator>
      <dc:date>2008-02-05T18:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889915#M955509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for my ignorance as I am new to the ASA's.  I have attached my "new" config. I tried adding the two lines and had no luck. I also changed the route inside to outside and had no luck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Feb 2008 18:37:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889915#M955509</guid>
      <dc:creator>jglover72</dc:creator>
      <dc:date>2008-02-05T18:37:30Z</dc:date>
    </item>
    <item>
      <title>Re: New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889916#M955510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would disregard the previous post, as you do not need that inside acl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is not right either...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route outside 192.168.0.0 255.255.0.0 192.168.10.1 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can put back what you had, but would be a good idea to be more specific as all 192.168.0.0/16 networks are not on the inside as 192.168.1.0 is on the outside. For exmaple, if the networks accessed by 192.168.10.1 were 192.168.2.0 and 192.168.3.0 then...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route inside 192.168.2.0 255.255.255.0 192.168.10.1&lt;/P&gt;&lt;P&gt;route inside 192.168.3.0 255.255.255.0 192.168.10.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need a way for the clients on 192.168.1.0 to route to 192.168.1.22 when accessing 192.168.10.0. For example, if you had an outside router you could do...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip route 192.168.10.0 255.255.255.0 192.168.1.22&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Feb 2008 18:41:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889916#M955510</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2008-02-05T18:41:23Z</dc:date>
    </item>
    <item>
      <title>Re: New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889917#M955511</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; What you can do is, just check the gateway of that 192.168.1.0 clients it should be 192.168.1.22 if that clients have different gateway address (another router) then that router should have route back to the ASA for your 192.168.10.0 network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for an example in the router command should be&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip route 192.168.10.0 255.255.255.0 192.168.1.22&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Feb 2008 18:51:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889917#M955511</guid>
      <dc:creator>patil_pritam</dc:creator>
      <dc:date>2008-02-05T18:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889918#M955513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; What you can do is, just check the gateway of that 192.168.1.0 clients it should be 192.168.1.22 if that clients have different gateway address (another router) then that router should have route back to the ASA for your 192.168.10.0 network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for an example in the router command should be&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip route 192.168.10.0 255.255.255.0 192.168.1.22&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Feb 2008 18:53:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889918#M955513</guid>
      <dc:creator>patil_pritam</dc:creator>
      <dc:date>2008-02-05T18:53:07Z</dc:date>
    </item>
    <item>
      <title>Re: New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889919#M955515</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;remove your current nat statement&lt;/P&gt;&lt;P&gt;and add the following statement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 192.168.10.0 192.168.10.0 netmask 255.255.255.0 0 0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 15:21:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889919#M955515</guid>
      <dc:creator>patil_pritam</dc:creator>
      <dc:date>2008-02-06T15:21:04Z</dc:date>
    </item>
    <item>
      <title>Re: New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889920#M955518</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, got it working.  I need to know the ports than I need to pass to the ASA with my existing router/firewall as the ASA will be behind the existing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you help me with that?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 15:26:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889920#M955518</guid>
      <dc:creator>jglover72</dc:creator>
      <dc:date>2008-02-06T15:26:54Z</dc:date>
    </item>
    <item>
      <title>Re: New ASA installation</title>
      <link>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889921#M955521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;which command solved your pinging problem?&lt;/P&gt;&lt;P&gt; from inside ping to outside?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2008 15:32:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/new-asa-installation/m-p/889921#M955521</guid>
      <dc:creator>patil_pritam</dc:creator>
      <dc:date>2008-02-06T15:32:44Z</dc:date>
    </item>
  </channel>
</rss>

