[clue] Wireshark

[foo7775 at comcast.net]

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... ;-) 

https://en.wikipedia.org/wiki/Observer_effect_%28physics%29 

T. 
----- Original Message -----

From: foo7775 at comcast.net 
To: "CLUE list" <clue at cluedenver.org> 
Sent: Tuesday, March 15, 2016 5:13:34 PM 
Subject: Re: [clue] Wireshark 

My (admittedly-incomplete) understanding is that Wireshark - in & 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. I have a theory or two, but nothing that even rises to the level of a WAG... 

T. 
----- Original Message -----

From: dennisjperkins at comcast.net 
To: "CLUE's list" <clue at cluedenver.org> 
Sent: Tuesday, March 15, 2016 3:45:30 PM 
Subject: Re: [clue] Wireshark 

I think I need to learn Wireshark to see what's happening. I don't understand why Wireshark affects things. 

----- Original Message -----

From: "Charles Burton" <charles.d.burton at gmail.com> 
To: "CLUE's mailing list" <clue at cluedenver.org> 
Sent: Tuesday, March 15, 2016 2:56:35 PM 
Subject: Re: [clue] Wireshark 

Spanning a port usually requires a config commit to the switch, there might have been something there. 

On Tue, Mar 15, 2016 at 6:36 PM, < dennisjperkins at comcast.net > wrote: 



I think he plugged the laptop into a port on the switch. 


From: "Charles Burton" < charles.d.burton at gmail.com > 
To: "CLUE's mailing list" < clue at cluedenver.org > 
Sent: Tuesday, March 15, 2016 9:20:46 AM 
Subject: Re: [clue] Wireshark 


Did he span a port on the switch over to Wireshark or put it inline between the analyzer and the destination? 

On Sat, Mar 12, 2016 at 12:50 AM, < dennisjperkins at comcast.net > wrote: 

<blockquote>

I was told that one of our customers was having network issues with our analyzers, so he hooked up a laptop with Wireshark. Supposedly the problem went away when Wireshark was monitoring the network, which doesn't make sense to me. Has anyone seen anything like this? 

_______________________________________________ 
clue mailing list: clue at cluedenver.org 
For information, account preferences, or to unsubscribe see: 
http://cluedenver.org/mailman/listinfo/clue 





_______________________________________________ 
clue mailing list: clue at cluedenver.org 
For information, account preferences, or to unsubscribe see: 
http://cluedenver.org/mailman/listinfo/clue 


_______________________________________________ 
clue mailing list: clue at cluedenver.org 
For information, account preferences, or to unsubscribe see: 
http://cluedenver.org/mailman/listinfo/clue 

</blockquote>



_______________________________________________ 
clue mailing list: clue at cluedenver.org 
For information, account preferences, or to unsubscribe see: 
http://cluedenver.org/mailman/listinfo/clue 


_______________________________________________ 
clue mailing list: clue at cluedenver.org 
For information, account preferences, or to unsubscribe see: 
http://cluedenver.org/mailman/listinfo/clue 


_______________________________________________ 
clue mailing list: clue at cluedenver.org 
For information, account preferences, or to unsubscribe see: 
http://cluedenver.org/mailman/listinfo/clue 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cluedenver.org/pipermail/clue/attachments/20160315/a9c1e1d6/attachment-0001.html