<?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: ASR-1009-X ssh all interface in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4995285#M586297</link>
    <description>&lt;LI-CODE lang="markup"&gt;in vty i used standard ACL only source only defined.&lt;/LI-CODE&gt;
&lt;P&gt;can you show us what ACL is that ?&lt;/P&gt;
&lt;P&gt;below example onlu 192.168.10.100 will be allowed to SSH to device.&lt;/P&gt;
&lt;P&gt;access-list 10 permit 192.168.10.100&lt;BR /&gt;!&lt;BR /&gt;line vty 0 4&lt;BR /&gt;access-class 10 in&lt;/P&gt;
&lt;P&gt;you can also do other ACL (which i do not recomment)&lt;/P&gt;
&lt;P&gt;you can have ACL and bind to interface where the traffic you looking to coming in for SSH request for the device. (best is VTY lines always).&lt;/P&gt;</description>
    <pubDate>Fri, 12 Jan 2024 15:21:45 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2024-01-12T15:21:45Z</dc:date>
    <item>
      <title>ASR-1009-X ssh all interface</title>
      <link>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4993812#M586228</link>
      <description>&lt;P&gt;HI ,&lt;/P&gt;&lt;P&gt;i have ASR-1009-X and C9K both connected OSPF and LAN segment L3 in C9K.&lt;/P&gt;&lt;P&gt;ASR and C9K both in OSPF and LAN segment advertise in OSPF.&amp;nbsp;&lt;/P&gt;&lt;P&gt;when i taking ssh through p2p interface IP&amp;nbsp; both device access from my LAN. Requirement is ssh should happen through mgmt interface only.&amp;nbsp;&lt;/P&gt;&lt;P&gt;But i have ACL in line vty 0 4 my ASR and C9K. transport input ssh and output non only. Still im getting ssh p2p ip interface.&lt;/P&gt;&lt;P&gt;Kindly suggest&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2024 18:07:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4993812#M586228</guid>
      <dc:creator>Sureshbabu</dc:creator>
      <dc:date>2024-01-10T18:07:41Z</dc:date>
    </item>
    <item>
      <title>Re: ASR-1009-X ssh all interface</title>
      <link>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4993814#M586229</link>
      <description>&lt;P&gt;Share the acl you use for vty and ip you use to access&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2024 18:11:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4993814#M586229</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-01-10T18:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: ASR-1009-X ssh all interface</title>
      <link>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4995261#M586292</link>
      <description>&lt;P&gt;in vty i used standard ACL only source only defined.&lt;/P&gt;&lt;P&gt;As per my understand for this case extended ACL will play role..... Is there is any way specific source to destination permit in standard&amp;nbsp; ACL.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2024 14:40:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4995261#M586292</guid>
      <dc:creator>Sureshbabu</dc:creator>
      <dc:date>2024-01-12T14:40:57Z</dc:date>
    </item>
    <item>
      <title>Re: ASR-1009-X ssh all interface</title>
      <link>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4995285#M586297</link>
      <description>&lt;LI-CODE lang="markup"&gt;in vty i used standard ACL only source only defined.&lt;/LI-CODE&gt;
&lt;P&gt;can you show us what ACL is that ?&lt;/P&gt;
&lt;P&gt;below example onlu 192.168.10.100 will be allowed to SSH to device.&lt;/P&gt;
&lt;P&gt;access-list 10 permit 192.168.10.100&lt;BR /&gt;!&lt;BR /&gt;line vty 0 4&lt;BR /&gt;access-class 10 in&lt;/P&gt;
&lt;P&gt;you can also do other ACL (which i do not recomment)&lt;/P&gt;
&lt;P&gt;you can have ACL and bind to interface where the traffic you looking to coming in for SSH request for the device. (best is VTY lines always).&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2024 15:21:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4995285#M586297</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2024-01-12T15:21:45Z</dc:date>
    </item>
    <item>
      <title>Re: ASR-1009-X ssh all interface</title>
      <link>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4995290#M586298</link>
      <description>&lt;P&gt;standard ACL is OK with direction IN it work&lt;BR /&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2024 15:24:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4995290#M586298</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-01-12T15:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: ASR-1009-X ssh all interface</title>
      <link>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4996205#M586331</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1426919"&gt;@Sureshbabu&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I understood correctly, you want to SSH to the network devices only via the management interfaces but not the others. The ACL that we associated with VTY lines can control the SSH clients that they would accept connections from. AFAIK IOS-XE has no option to bind or restrict SSH server port to specific IP address(es). As a result, even though BB considered it a bad idea, you would likely need to put ACL on the other interfaces or put ACL or firewall rule on some other network devices between you and these two network devices.&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jan 2024 19:19:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4996205#M586331</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2024-01-13T19:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: ASR-1009-X ssh all interface</title>
      <link>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4996264#M586333</link>
      <description>&lt;P&gt;I see this Q alot and I decide to test something in my mind and I was right&amp;nbsp;&lt;BR /&gt;VTY is like interface when we apply ACL (standard) to specific VTY line and config other VTY without ACL we can Access !!!!!!&lt;BR /&gt;YES WE can&lt;BR /&gt;when we access to SW/R the first VTY line number use but what if this line not idle (still connect to some user)&lt;BR /&gt;the SW/R use other Line here the issue&amp;nbsp;&lt;BR /&gt;when we config a gourp of VTY some with ACL and other without, and there line is still connect not idle we can access and Engineer claim the ACL not work.&amp;nbsp;&lt;BR /&gt;NO it work but we need to tune the ACL and apply it to all VTY&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;below LAB VTY 0 use ACL and VTY 1 4 not use it&amp;nbsp;&lt;/P&gt;
&lt;P&gt;when I access via R2 I can access since ACL allow that&amp;nbsp;&lt;BR /&gt;then I try access from R3 and also I can access because R1 will use second VTY line group 1 4 which is without ACL&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Hope this Clear Issue of NON work ACL&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;MHM&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot (87).png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/207275iB901A0BD2D4788A2/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot (87).png" alt="Screenshot (87).png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot (88).png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/207276i4835F54E3B6A3B91/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot (88).png" alt="Screenshot (88).png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot (89).png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/207278iDBE4CA0DC313A859/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot (89).png" alt="Screenshot (89).png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot (91).png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/207280i22BCE80D77704EB3/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot (91).png" alt="Screenshot (91).png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot (90).png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/207281i9BD6DBFF29592026/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot (90).png" alt="Screenshot (90).png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jan 2024 22:43:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asr-1009-x-ssh-all-interface/m-p/4996264#M586333</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-01-13T22:43:09Z</dc:date>
    </item>
  </channel>
</rss>

