<?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 Cannot ssh or ping ASA 5510 from the inside interface. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907205#M457318</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you say that you have been able to manage the ASA directly from Management interface, does that mean also with SSH?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was just wondering if you've issued the "crypto key generate rsa modules 1024" from the console CLI? Or same from the ASDM tools -&amp;gt; Command Line Interface (or something similiar)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Atleast thats the most common mistake I sometimes make when starting configuraitons with ASA on console (forget to create the keys)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Apr 2012 14:44:32 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2012-04-06T14:44:32Z</dc:date>
    <item>
      <title>Cannot ssh or ping ASA 5510 from the inside interface.</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907202#M457312</link>
      <description>&lt;P&gt;The ASA is configured in very simple transparent mode. As desired, traffic can flow in each direction between inside and outside. I can manage the ASA via console and direct connection to the management interface. The problem is that I cannot ping or ssh to the ASA via the inside interface. I need to be able to manage the ASA from any PC on the inside LAN. I suspect I am missing some easy aspect of the configuration but after a lot of hours I'm about at the end of my patience with it. Here is what I believe to be the relevant parts of the config.&amp;nbsp; Any assistance will be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA Version 8.2(1) &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;firewall transparent&lt;/P&gt;&lt;P&gt;hostname issr1&lt;/P&gt;&lt;P&gt;enable password 2alej83t5cqT0FWd encrypted&lt;/P&gt;&lt;P&gt;passwd 4kleUY438I93.4ljdh encrypted&lt;/P&gt;&lt;P&gt;names&lt;/P&gt;&lt;P&gt;name xxx.125.144.0 myLAN&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/0&lt;/P&gt;&lt;P&gt; nameif Outside&lt;/P&gt;&lt;P&gt; security-level 0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/1&lt;/P&gt;&lt;P&gt; nameif inside&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/2&lt;/P&gt;&lt;P&gt; shutdown&lt;/P&gt;&lt;P&gt; no nameif&lt;/P&gt;&lt;P&gt; no security-level&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Ethernet0/3&lt;/P&gt;&lt;P&gt; shutdown&lt;/P&gt;&lt;P&gt; no nameif&lt;/P&gt;&lt;P&gt; no security-level&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Management0/0&lt;/P&gt;&lt;P&gt; nameif management&lt;/P&gt;&lt;P&gt; security-level 100&lt;/P&gt;&lt;P&gt; ip address xxx.125.145.173 255.255.255.0 &lt;/P&gt;&lt;P&gt; management-only&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;dns server-group DefaultDNS&lt;/P&gt;&lt;P&gt; domain-name myLAN.circ6.dcn&lt;/P&gt;&lt;P&gt;object-group protocol TCPUDP&lt;/P&gt;&lt;P&gt; protocol-object tcp&lt;/P&gt;&lt;P&gt;access-list inside_access_in_2 extended permit ip any any &lt;/P&gt;&lt;P&gt;access-list Outside_access_in_1 extended permit ip myLAN 255.255.254.0 any &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 management 1500&lt;/P&gt;&lt;P&gt;ip address xxx.125.145.175 255.255.254.0&lt;/P&gt;&lt;P&gt;icmp unreachable rate-limit 1 burst-size 1&lt;/P&gt;&lt;P&gt;icmp permit host xxx.125.145.175 inside&lt;/P&gt;&lt;P&gt;asdm history enable&lt;/P&gt;&lt;P&gt;access-group Outside_access_in_1 in interface Outside&lt;/P&gt;&lt;P&gt;access-group inside_access_in_2 in interface inside control-plane&lt;/P&gt;&lt;P&gt;route inside myLAN 255.255.254.0 xxx.125.144.240 1&lt;/P&gt;&lt;P&gt;dynamic-access-policy-record DfltAccessPolicy&lt;/P&gt;&lt;P&gt;aaa authentication ssh console LOCAL &lt;/P&gt;&lt;P&gt;http server enable&lt;/P&gt;&lt;P&gt;http xxx.125.144.0 255.255.254.0 management&lt;/P&gt;&lt;P&gt;http myLAN 255.255.254.0 inside&lt;/P&gt;&lt;P&gt;crypto ipsec security-association lifetime seconds 28800&lt;/P&gt;&lt;P&gt;crypto ipsec security-association lifetime kilobytes 4608000&lt;/P&gt;&lt;P&gt;ssh xxx.125.144.14 255.255.255.255 inside&lt;/P&gt;&lt;P&gt;ssh xxx.125.145.174 255.255.255.255 management&lt;/P&gt;&lt;P&gt;ssh timeout 60&lt;/P&gt;&lt;P&gt;console timeout 0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Cryptochecksum:f1c9377arda5b6aef83928h0b0058f9&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:51:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907202#M457312</guid>
      <dc:creator>kywbcisco</dc:creator>
      <dc:date>2019-03-11T22:51:12Z</dc:date>
    </item>
    <item>
      <title>Cannot ssh or ping ASA 5510 from the inside interface.</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907203#M457313</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 have never actually configured a transparent ASA firewall so I am just guessing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I am wondering is that if you have a transparent firewall acting as a L2 device in the network. Shouldnt you just have a default route pointing to the networks only L3 interfaces IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you tried giving the management interface a totally different IP address? Something like 10.10.10.1/24 so it doesnt have anything to do with the actual network you have your ASA connected to?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you ping the IP address mentioned in the global configuration line "ip address" from your computer connected to the L2 network?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Apr 2012 20:00:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907203#M457313</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-04-05T20:00:01Z</dc:date>
    </item>
    <item>
      <title>Cannot ssh or ping ASA 5510 from the inside interface.</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907204#M457315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had an error in a netmask. After fixing that I can ping and connect with ASDM from the inside to the global IP address. I still cannot SSH from the inside but I should be able to figure that out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help. Although your suggestion wasn't exactly the solution, it did prompt me to review all of my network settings and find the immediate problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Apr 2012 14:02:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907204#M457315</guid>
      <dc:creator>kywbcisco</dc:creator>
      <dc:date>2012-04-06T14:02:32Z</dc:date>
    </item>
    <item>
      <title>Cannot ssh or ping ASA 5510 from the inside interface.</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907205#M457318</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you say that you have been able to manage the ASA directly from Management interface, does that mean also with SSH?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was just wondering if you've issued the "crypto key generate rsa modules 1024" from the console CLI? Or same from the ASDM tools -&amp;gt; Command Line Interface (or something similiar)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Atleast thats the most common mistake I sometimes make when starting configuraitons with ASA on console (forget to create the keys)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Apr 2012 14:44:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907205#M457318</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2012-04-06T14:44:32Z</dc:date>
    </item>
    <item>
      <title>Cannot ssh or ping ASA 5510 from the inside interface.</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907206#M457320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From the management interface I can use SSH and ASDM.&lt;/P&gt;&lt;P&gt;I had already done the 'crypto..." command. &lt;/P&gt;&lt;P&gt;After tweaking another netmask I can now do SSH and ASDM from the inside interface. So my immediate problems are all resolved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Apr 2012 17:29:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ssh-or-ping-asa-5510-from-the-inside-interface/m-p/1907206#M457320</guid>
      <dc:creator>kywbcisco</dc:creator>
      <dc:date>2012-04-06T17:29:07Z</dc:date>
    </item>
  </channel>
</rss>

