<?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: Procurve SSH session source in HPE Aruba Networking &amp; ProVision-based</title>
    <link>https://community.hpe.com/t5/hpe-aruba-networking-provision/procurve-ssh-session-source/m-p/5327891#M894</link>
    <description>&lt;P&gt;Did you ever find an answer to this?&lt;/P&gt;</description>
    <pubDate>Sat, 10 Sep 2011 12:16:55 GMT</pubDate>
    <dc:creator>Glenn Sutherland</dc:creator>
    <dc:date>2011-09-10T12:16:55Z</dc:date>
    <item>
      <title>Procurve SSH session source</title>
      <link>https://community.hpe.com/t5/hpe-aruba-networking-provision/procurve-ssh-session-source/m-p/4815435#M595</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm having warnings, "auth: Invalid user name/password on SSH session﻿" on procurve 2510G-24. Is there a way to solve the SSH session source IP by logging/debugging? Source IP shows in the log when SSH connection is established successfully but not when authorization fails.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2011 11:37:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-aruba-networking-provision/procurve-ssh-session-source/m-p/4815435#M595</guid>
      <dc:creator>jahallap</dc:creator>
      <dc:date>2011-07-06T11:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: Procurve SSH session source</title>
      <link>https://community.hpe.com/t5/hpe-aruba-networking-provision/procurve-ssh-session-source/m-p/5327891#M894</link>
      <description>&lt;P&gt;Did you ever find an answer to this?&lt;/P&gt;</description>
      <pubDate>Sat, 10 Sep 2011 12:16:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-aruba-networking-provision/procurve-ssh-session-source/m-p/5327891#M894</guid>
      <dc:creator>Glenn Sutherland</dc:creator>
      <dc:date>2011-09-10T12:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: Procurve SSH session source</title>
      <link>https://community.hpe.com/t5/hpe-aruba-networking-provision/procurve-ssh-session-source/m-p/5332465#M902</link>
      <description>&lt;P&gt;No solution found. This is still open.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2011 05:27:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-aruba-networking-provision/procurve-ssh-session-source/m-p/5332465#M902</guid>
      <dc:creator>jahallap</dc:creator>
      <dc:date>2011-09-15T05:27:25Z</dc:date>
    </item>
    <item>
      <title>Re: Procurve SSH session source</title>
      <link>https://community.hpe.com/t5/hpe-aruba-networking-provision/procurve-ssh-session-source/m-p/5333267#M904</link>
      <description>&lt;P&gt;Hi jahallap,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can suggest port mirroring to a PC with Wireshark or&amp;nbsp;other network analyzer and then look for packets going to tcp port 22.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Oleg&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2011 17:10:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-aruba-networking-provision/procurve-ssh-session-source/m-p/5333267#M904</guid>
      <dc:creator>Oleg Sukharev</dc:creator>
      <dc:date>2011-09-15T17:10:09Z</dc:date>
    </item>
  </channel>
</rss>

