<html><body><div style="font-family: Arial; font-size: 12pt; color: #000000"><div>Of course, the moment I sent this, the 'observer effect' came to mind - so perhaps list members will be kind enough to allow me to include that as a kind of a "caveat" to my previous message...&nbsp; ;-)<br></div><div><br></div><div>&nbsp;&nbsp; https://en.wikipedia.org/wiki/Observer_effect_%28physics%29<br></div><div><br></div><div>T.<br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>foo7775@comcast.net<br><b>To: </b>"CLUE list" &lt;clue@cluedenver.org&gt;<br><b>Sent: </b>Tuesday, March 15, 2016 5:13:34 PM<br><b>Subject: </b>Re: [clue] Wireshark<br><div><br></div><div style="font-family: Arial; font-size: 12pt; color: #000000"><div>My (admittedly-incomplete) understanding is that Wireshark - in &amp; of itself - shouldn't have any effect on traffic. If you figure out cause/effect on this one, I'd be interesting in hearing about it.&nbsp; I have a theory or two, but nothing that even rises to the level of a WAG...<br></div><div><br></div><div>T.<br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>dennisjperkins@comcast.net<br><b>To: </b>"CLUE's list" &lt;clue@cluedenver.org&gt;<br><b>Sent: </b>Tuesday, March 15, 2016 3:45:30 PM<br><b>Subject: </b>Re: [clue] Wireshark<br><div><br></div><div style="font-family: Arial; font-size: 12pt; color: #000000"><div>I think I need to learn Wireshark to see what's happening.&nbsp; I don't understand why Wireshark affects things.<br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Charles Burton" &lt;charles.d.burton@gmail.com&gt;<br><b>To: </b>"CLUE's mailing list" &lt;clue@cluedenver.org&gt;<br><b>Sent: </b>Tuesday, March 15, 2016 2:56:35 PM<br><b>Subject: </b>Re: [clue] Wireshark<br><div><br></div><div dir="ltr">Spanning a port usually requires a config commit to the switch, there might have been something there.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 15, 2016 at 6:36 PM,  <span dir="ltr">&lt;<a href="mailto:dennisjperkins@comcast.net" target="_blank">dennisjperkins@comcast.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Arial;font-size:12pt;color:#000000"><div>I think he plugged the laptop into a port on the switch.<br></div><div><br></div><hr><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: </b>"Charles Burton" &lt;<a href="mailto:charles.d.burton@gmail.com" target="_blank">charles.d.burton@gmail.com</a>&gt;<br><b>To: </b>"CLUE's mailing list" &lt;<a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a>&gt;<br><b>Sent: </b>Tuesday, March 15, 2016 9:20:46 AM<br><b>Subject: </b>Re: [clue] Wireshark<div><div class="h5"><br><div><br></div><div dir="ltr">Did he span a port on the switch over to Wireshark or put it inline between the analyzer and the destination?&nbsp; <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Mar 12, 2016 at 12:50 AM, <span dir="ltr">&lt;<a href="mailto:dennisjperkins@comcast.net" target="_blank">dennisjperkins@comcast.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Arial;font-size:12pt;color:#000000"><div>I was told that one of our customers was having network issues with our analyzers, so he hooked up a laptop with Wireshark.&nbsp; Supposedly the problem went away when Wireshark was monitoring the network, which doesn't make sense to me.&nbsp; Has anyone seen anything like this?<br></div></div></div><br>_______________________________________________<br> clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br> For information, account preferences, or to unsubscribe see:<br> <a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div><br>_______________________________________________<br>clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>For information, account preferences, or to unsubscribe see:<br><a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></div></div></div><div><br></div></div></div><br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>
<br>_______________________________________________<br>clue mailing list: clue@cluedenver.org<br>For information, account preferences, or to unsubscribe see:<br>http://cluedenver.org/mailman/listinfo/clue</div><div><br></div></div><br>_______________________________________________<br>clue mailing list: clue@cluedenver.org<br>For information, account preferences, or to unsubscribe see:<br>http://cluedenver.org/mailman/listinfo/clue</div><div><br></div></div><br>_______________________________________________<br>clue mailing list: clue@cluedenver.org<br>For information, account preferences, or to unsubscribe see:<br>http://cluedenver.org/mailman/listinfo/clue</div><div><br></div></div></body></html>