I have a .NET WCF service running on my computer (in IIS7) that communicates over secured (certificate) TCP with my client (also on my computer). Now I need to clarify if my data really is secured (encrypted). When using the Microsoft tools like Service Trace Viewer it seems like it is not.
I have installed Wireshark and have selected the correct interface (my network card). When starting the capture a lot of packages will be shown, so first I filter it by tcp then by src (my local ip address). This reduces the number of packages but when running my application (doing some calls to the service) I can´t see them in Wireshark? I am probably using wrong filters. Please help!
asked 22 Oct '10, 08:10
edited 10 Nov '10, 07:10
With both server and client on the same platform your packets will go through the loopback interface, not your network interface. Therefore you don't see them flowing out of your network connection, hence Wireshark doesn't see them.
answered 23 Oct '10, 12:09