<?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 Access list for SSH vty lines in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/access-list-for-ssh-vty-lines/m-p/3990447#M925084</link>
    <description>&lt;P&gt;Hi All,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can someone please help me understand this access list for the VTY lines? Previous network engineer has this in our switches on the VTY lines, the part I don't quite understand is the host 0.0.0.0?&amp;nbsp; It's been working and then a few of our switches rebooted then we were not able to SSH in and I had to remove the host 0.0.0.0 and add in "any" but not sure why?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;10 permit tcp 192.168.0.0 0.0.255.255 host 0.0.0.0 eq 22 log-input&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 17:43:54 GMT</pubDate>
    <dc:creator>Eddie Sardinha</dc:creator>
    <dc:date>2020-02-21T17:43:54Z</dc:date>
    <item>
      <title>Access list for SSH vty lines</title>
      <link>https://community.cisco.com/t5/network-security/access-list-for-ssh-vty-lines/m-p/3990447#M925084</link>
      <description>&lt;P&gt;Hi All,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can someone please help me understand this access list for the VTY lines? Previous network engineer has this in our switches on the VTY lines, the part I don't quite understand is the host 0.0.0.0?&amp;nbsp; It's been working and then a few of our switches rebooted then we were not able to SSH in and I had to remove the host 0.0.0.0 and add in "any" but not sure why?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;10 permit tcp 192.168.0.0 0.0.255.255 host 0.0.0.0 eq 22 log-input&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:43:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-list-for-ssh-vty-lines/m-p/3990447#M925084</guid>
      <dc:creator>Eddie Sardinha</dc:creator>
      <dc:date>2020-02-21T17:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: Access list for SSH vty lines</title>
      <link>https://community.cisco.com/t5/network-security/access-list-for-ssh-vty-lines/m-p/3990507#M925099</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;Using the "host 0.0.0.0" as destination in that matter makes absolutely no sense there.&lt;/P&gt;&lt;P&gt;The old ACL would have allowed TCP/22 sourcing from 192.168.x.x/24 towards 0.0.0.0/32.&lt;/P&gt;&lt;P&gt;Now with your new ACL you are allowing the traffic towards any destination, which makes the SSH connection work.&lt;/P&gt;&lt;P&gt;Instead of &lt;STRONG&gt;any&lt;/STRONG&gt; you could also do "&lt;STRONG&gt;host &amp;lt;IP of the Switch&amp;gt;&lt;/STRONG&gt;" - but then you would have to modify it for every device..&lt;/P&gt;&lt;P&gt;Be sure to read through the following document to fully understand ACLs:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/ios-firewall/23602-confaccesslists.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/ios-firewall/23602-confaccesslists.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Here you also find the following:&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;FONT size="3"&gt;&lt;EM&gt;A source/source-wildcard setting of 0.0.0.0/255.255.255.255 can be specified as &lt;STRONG&gt;any&lt;/STRONG&gt;. The wildcard can be omitted if it is all zeros. Therefore, host 10.1.1.2 0.0.0.0 is the same as host 10.1.1.2.&lt;/EM&gt; &lt;/FONT&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;That sentence also states that "host 0.0.0.0" makes no sense since it would kind of block everything.&lt;/P&gt;&lt;P&gt;I hope this helps you.&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;Julian&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 01:22:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-list-for-ssh-vty-lines/m-p/3990507#M925099</guid>
      <dc:creator>julian.bendix</dc:creator>
      <dc:date>2019-11-28T01:22:51Z</dc:date>
    </item>
    <item>
      <title>Re: Access list for SSH vty lines</title>
      <link>https://community.cisco.com/t5/network-security/access-list-for-ssh-vty-lines/m-p/3990522#M925112</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/260726"&gt;@Eddie Sardinha&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ACE indicates that packets with source 192.168.0.0 and with destination the default network, through port 22 will be allowed.&lt;BR /&gt;When changing the destination to any, the packets that reach the vty lines with any destination, through port 22 will be allowed.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;You must be clear about what you are looking for with the ACL.&lt;BR /&gt;My recommendation is that the source of the allowed packets is not so wide, moreover, it should be only a very limited range of IPs, as that will contribute to the security of your network.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 02:30:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-list-for-ssh-vty-lines/m-p/3990522#M925112</guid>
      <dc:creator>luis_cordova</dc:creator>
      <dc:date>2019-11-28T02:30:12Z</dc:date>
    </item>
  </channel>
</rss>

