Beta 10054, UPnP problems

[BlindWanderer]

I noticed something interesting, my nat router would inexplicably freeze every so often when running Beta 10054, I managed to get a peak at the UPnP mappings and in the address field where it should have said 192.168.10.5 it said xxx.168.10.5 where the xxx was some random junk characters... which is just odd (it was the same junk for both TCP and UDP mappings). This doesn't happen in 9704. I think a recent change in how UPnP requests are constructed has resulted in this. If this is indeed the case it should be easy to verify with a packet sniffer.

[jewelisheaven]

Or you could upload some of the packets for requests to map/unmap ports to see if it's something specific to your router? most people use mediafire.com What router do you use?

[Firon]

Can you provide wireshark captures of the UPnP stuff?

[BlindWanderer]

The box is an Aero14 ( http://www.newegg.com/Product/Product.aspx?Item=N82E16833338009 ) which is based on a waveplus.com.tw chipset. Technically the firmware can be upgraded but there aren't any upgrades. Airnet the manufacturer has changed it's name to AZiO and now sells the product with a different colored box and model number. But 20$ is 20$.

I turned everything off DHT, Local Peer Discovery and Peer Exchange. If this is an error where one module is corrupting another then it might not show up in the capture at all.

http://mailerdaemon.home.comcast.net/upnp_capture.pcap

Edit: it tends to crash when remapping the port or removing it.

[jewelisheaven]

I'm not sure but they say some changes have also been made in 10093. Could you test and post packets with that version as well?

[Firon]

10093's behavior is pretty much identical to 10054 (it's sending corrupt data), but it might be useful to get a cap from it too.