<?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: Quagga NED ssh in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757569#M3010</link>
    <description>&lt;P&gt;Simple as that &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; I've added&amp;nbsp;/usr/bin/vtysh as the shell for my user inside /etc/passwd. Works as expected.&lt;/P&gt;
&lt;P&gt;Thanks for pointing me in the right direction.&lt;/P&gt;</description>
    <pubDate>Tue, 04 Dec 2018 15:15:52 GMT</pubDate>
    <dc:creator>sspehar</dc:creator>
    <dc:date>2018-12-04T15:15:52Z</dc:date>
    <item>
      <title>Quagga NED ssh</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757347#M2998</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm interested in how would you connect to quagga router using ssh from NSO? So quagga runs multiple daemons for each functionality it provides (bgpd, ospfd, zebra..), and these daemons are accessible on their associated telnet ports, so I can add a device to NSO on telnet port 2605(bgpd) and using the quagga-bgp NED manage that daemon, that works.&lt;/P&gt;
&lt;P&gt;But I see that the NED has the&amp;nbsp;setupSSH method, so I guess there is a way to use ssh? Is it able to connect to vtysh on quagga? I wasn't successfull with ssh, so any help would be appreciated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Simon&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 12:14:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757347#M2998</guid>
      <dc:creator>sspehar</dc:creator>
      <dc:date>2019-03-01T12:14:46Z</dc:date>
    </item>
    <item>
      <title>Re: Quagga NED ssh</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757440#M3000</link>
      <description>&lt;P&gt;It is true that each Quagga component has a telnet style CLI of its own. Most Quagga users, however, setup Quagga with a central proxy component (I forget the name of the component right now) that supports SSH and forwards all commands to the correct sub component(s) in the framework.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Dec 2018 11:58:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757440#M3000</guid>
      <dc:creator>Jan Lindblad</dc:creator>
      <dc:date>2018-12-04T11:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: Quagga NED ssh</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757536#M3007</link>
      <description>&lt;P&gt;Hi Jan, thanks! Looking for this kind of proxy component, the only thing I found resembling is vtysh, which is the quagga integrated shell for handling all daemons. But that's just 'frontend', and I think you can't remotely ssh to it so neither can NED.&lt;/P&gt;
&lt;P&gt;If you happen to remember the name of that component I would appreciate if you let me know. Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 04 Dec 2018 14:39:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757536#M3007</guid>
      <dc:creator>sspehar</dc:creator>
      <dc:date>2018-12-04T14:39:53Z</dc:date>
    </item>
    <item>
      <title>Re: Quagga NED ssh</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757549#M3008</link>
      <description>&lt;P&gt;"vtysh" was the component I couldn't remember the name of, and yes, that's just a proxy. I admit I haven't set this up myself, but I can't imagine it being difficult to place SSH (e.g. OpenSSH) in front of vtysh. A small matter of system configuration? Have you tried setting up vtysh as the login shell on the Linux system hosting your Quagga?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Dec 2018 14:53:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757549#M3008</guid>
      <dc:creator>Jan Lindblad</dc:creator>
      <dc:date>2018-12-04T14:53:32Z</dc:date>
    </item>
    <item>
      <title>Re: Quagga NED ssh</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757569#M3010</link>
      <description>&lt;P&gt;Simple as that &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; I've added&amp;nbsp;/usr/bin/vtysh as the shell for my user inside /etc/passwd. Works as expected.&lt;/P&gt;
&lt;P&gt;Thanks for pointing me in the right direction.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Dec 2018 15:15:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/quagga-ned-ssh/m-p/3757569#M3010</guid>
      <dc:creator>sspehar</dc:creator>
      <dc:date>2018-12-04T15:15:52Z</dc:date>
    </item>
  </channel>
</rss>

