<?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: SSH to a specific host IP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ssh-to-a-specific-host-ip/m-p/4265154#M1076944</link>
    <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;common practice is to use standard ACL based on allowed source IP (management subnet/NMS).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ip access-list standard SSH_Access_Control&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;permit 192.168.1.0 0.0.0.255&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;deny any log&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 30 Dec 2020 12:19:34 GMT</pubDate>
    <dc:creator>johnlloyd_13</dc:creator>
    <dc:date>2020-12-30T12:19:34Z</dc:date>
    <item>
      <title>SSH to a specific host IP</title>
      <link>https://community.cisco.com/t5/network-security/ssh-to-a-specific-host-ip/m-p/4263955#M1076909</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I'm trying to limit SSH access to my router.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Router IP is 192.168.1.254&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My access list for SSH:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ip access-list extended &lt;STRONG&gt;SSH_Access_Control&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;permit tcp 192.168.1.0 0.0.0.255 any eq 22&lt;/STRONG&gt;&lt;BR /&gt;deny tcp any any eq 22 log&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;line vty 0 4&lt;BR /&gt;&lt;STRONG&gt;access-class SSH_Access_Control in&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it matters, I'm using aaa.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above works.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the ACL I remove this:&lt;/P&gt;&lt;P&gt;permit tcp 192.168.1.0 0.0.0.255 &lt;STRONG&gt;any&lt;/STRONG&gt; eq 22&lt;/P&gt;&lt;P&gt;and add this:&lt;/P&gt;&lt;P&gt;permit tcp 192.168.1.0 0.0.0.255 &lt;STRONG&gt;host 192.168.1.254&lt;/STRONG&gt; eq 22&lt;/P&gt;&lt;P&gt;Annnndddddd...I'm locked out of the router. Console time for me.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm permitting any IP in the subnet to connect to this specific router &lt;STRONG&gt;ON&lt;/STRONG&gt; this specific router.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone know why this doesn't work?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Sat, 26 Dec 2020 18:01:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-to-a-specific-host-ip/m-p/4263955#M1076909</guid>
      <dc:creator>kirm</dc:creator>
      <dc:date>2020-12-26T18:01:54Z</dc:date>
    </item>
    <item>
      <title>Re: SSH to a specific host IP</title>
      <link>https://community.cisco.com/t5/network-security/ssh-to-a-specific-host-ip/m-p/4263961#M1076910</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1073057"&gt;@kirm&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Refer to the previous post, VTY lines have no IP address:-&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/switching/vty-extended-acl-with-destination-address/td-p/1163772" target="_self"&gt;https://community.cisco.com/t5/switching/vty-extended-acl-with-destination-address/td-p/1163772&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Enable logging with your ACL and I'd expect to see something similar to this: %SEC-6-IPACCESSLOGP: list VTY denied tcp 192.168.10.201(1096) -&amp;gt; &lt;EM&gt;&lt;STRONG&gt;0.0.0.0(22), 1 packet&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you want to control SSH to 192.168.1.254 use an interface ACL to permit/deny and/or set transport input ssh under the vty line, with the VTY ACL to permit the source IP addresses.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;HTH&lt;/P&gt;</description>
      <pubDate>Sat, 26 Dec 2020 18:41:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-to-a-specific-host-ip/m-p/4263961#M1076910</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2020-12-26T18:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: SSH to a specific host IP</title>
      <link>https://community.cisco.com/t5/network-security/ssh-to-a-specific-host-ip/m-p/4264008#M1076912</link>
      <description>&lt;P&gt;Like it says here?:&lt;/P&gt;&lt;P&gt;"VTY lines have no IP address so what's the benefit to include the destination?"&lt;/P&gt;&lt;P&gt;Very good and thank you. I've marked your answer as the accepted solution.&lt;/P&gt;</description>
      <pubDate>Sun, 27 Dec 2020 03:17:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-to-a-specific-host-ip/m-p/4264008#M1076912</guid>
      <dc:creator>kirm</dc:creator>
      <dc:date>2020-12-27T03:17:18Z</dc:date>
    </item>
    <item>
      <title>Re: SSH to a specific host IP</title>
      <link>https://community.cisco.com/t5/network-security/ssh-to-a-specific-host-ip/m-p/4265154#M1076944</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;common practice is to use standard ACL based on allowed source IP (management subnet/NMS).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;ip access-list standard SSH_Access_Control&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;permit 192.168.1.0 0.0.0.255&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;deny any log&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Dec 2020 12:19:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-to-a-specific-host-ip/m-p/4265154#M1076944</guid>
      <dc:creator>johnlloyd_13</dc:creator>
      <dc:date>2020-12-30T12:19:34Z</dc:date>
    </item>
  </channel>
</rss>

