I'm not going to argue either side here, just note that your email client's filters can easily delete any specific subject line, perhaps with a user or set of users as to and from entries as well. I would remove the filter[s] after a week to avoid missing future, completely different conversations.

On 08/05/2016 01:22 PM, P. Larry Nelson wrote:

[log in to unmask]" type="cite">With all due respect, and not interested at all in flaming or starting
one of those wars, I, and I think most folks on this list, find that the
occasional dip into topics slightly off of SL issues can be very educational.
And for me, that's what it's all about. The sharing of knowledge, tools,
hints, tricks, whatever... Because I know just enough about most things
to be a little dangerous, and it's wonderful to find out more so I can be
even more dangerous!

- Larry

stroe wrote on 8/5/16 9:38 AM:

Could you please stop this, which is not an SL issue?

On 2016-08-05 17:19, Lamar Owen wrote:

On 07/30/2016 06:35 PM, ToddAndMargo wrote:

I am looking to do network discovery. Basically, everything
on the interface, regardless of what network it belongs to
or if even has an ip assigned. Like AutoScan Network, only
not abandoned.

I have a dedicated install of NetworkSecurityToolkit (NST) on a box
connected to two ports on one of our core switches. One port is the
admin port that NST serves its web GUI on; the second port is a
capture-only port and connects to a SPAN port on the core switch
(Cisco terminology, as it's a Cisco 7609). I set up the SPAN to
redirect traffic for the ports and/or VLANs I'm interested in looking
at, and then capture all the traffic (I capture all traffic then
filter it out). Not as clean as some other solutions, but it does get
everything.

--
Miles O'Neal
CAD Systems Engineer
Cirrus Logic | cirrus.com | 1.512.851.4659