How can you use Fiddler (or equivalent) with the emulator in the Windows Phone 8 SDK when on a domain/network that uses IPSEC?

Asked 30/10, 2012 at 17:2 Answered 29/11, 2012 at 10:5

Solved fiddler hyper-v ipsec windows-phone-8

Now that the WP8 Emulator is based on Hyper-V, the old method of using Fiddler to intercept network traffic doesn't work if the network uses IPSEC.

Is there a way to use Fiddler and a WP8 emulator in such a scenario?

Unmoved answered 30/10, 2012 at 17:2 Comment(0)

I finally found the answer at http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj684580(v=vs.105).aspx

On a corporate domain, the emulator appears as a separate network device that is not joined to the domain. As a result, you may also have to get an exception from your IT department before the emulator can connect to services that are running on the domain-joined development computer.

A network security exception was required.

Unmoved answered 29/11, 2012 at 10:5 Comment(0)

Fiddler with exactly the same setup as on WP7 (https://fiddler2.com/fiddler/help/phone.asp) works absolutely fine for me.

You grab the traffic from the host system, so the guest (the WP8 emulator) has to bypass that too.

If it doesn't work let me know, but for me and others I know, it runs without any issues.

Wildermuth answered 30/10, 2012 at 20:31 Comment(7)

This works for the WP7 emulator as ships with the WP8 SDK, but doesn't work with the WP8 emulators. They do not route the traffic in the same way. – Unmoved 30/10, 2012 at 23:42

Did you try it ? It's running excactly as I described in front of me. – Wildermuth 31/10, 2012 at 8:52

yes, of course I tried it. Current thinking is that this may be an IPSEC issue. - Still investigating – Unmoved 31/10, 2012 at 9:36

That's possible. I have no IPSec/VPN or IPv6 setup here, but plain IPv4 with unencrypted and SSL/TLS encrypted traffic works as before. But I also heard from (at least) IPv6 users that they had trouble. – Wildermuth 31/10, 2012 at 10:33

The steps here: blogs.msdn.com/b/fiddler/archive/2010/10/15/… worked fine for me just now. Screenshot twitter.com/ericlaw/status/263709714196611072/photo/1/large – Merola 31/10, 2012 at 18:32

Have confirmed that this is due to IPSEC restrictions. Updated question to make this clear. – Unmoved 1/11, 2012 at 12:23

I'm on a simple home network and am still unable to get fiddler to work with the new emulator. I'm on win8, stopped the IPSEC service, firewall is off. I have decrypt https checked and have the cert installed. The cert installs on the emulator as well, after that the emulator loses connection, strange. – Indamine 6/11, 2012 at 15:22

I finally found the answer at http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj684580(v=vs.105).aspx

On a corporate domain, the emulator appears as a separate network device that is not joined to the domain. As a result, you may also have to get an exception from your IT department before the emulator can connect to services that are running on the domain-joined development computer.

A network security exception was required.

Unmoved answered 29/11, 2012 at 10:5 Comment(0)

You will probably have to use something like wireshark which works at a sub-protocol level and can therefore intercept anything.

Note that analysis won't be nearly as easy as it is in Fiddler though. Also, HTTPS connections might be impossible to analyze because of the whole man-in-the-middle attack prevention brought on by the protocol and certificates and such.

Village answered 30/10, 2012 at 18:37 Comment(1)

A protocol analyzer that sees raw packets can't do much with encrypted packets unless it has the keying material to understand them. – Pettit 13/11, 2012 at 1:45

Recommended topics

Hot tags