The replay tech has said he has read this thread. I do not need to send it to him.
That aside, I captured a replay crash with wireshark, and the information is completely ****ing useless. Absolutely nothing shows up out of the ordinary.
This could be for one of two reasons i can think of (chime in with others if you can think of them)
1) There is no unusual network activity because that is not the cause of the reboot
2) the unusual network activity is not showing up because it isn't being detected. Sometimes, even with the best gear, wireshark is unable to snoop on peer to peer tcp communications. This is one of the things that "promiscuous mode" is supposed to deal with, but hey, who knows. If i had all hubs instead of switches, this might actually fix things, but my router is a switch, so there's no real getting around this... well, maybe i could hub a computer and the two replays together... *1
You may view a picture of my wireshark output during the "incident" atwww.ericf.com/reboot.jpg
If you feel like it, pull the plug from your box and plug it back in (power, i mean). Your wireshark will look just like that.
and by "just like that", i mean it will be normal, then all of a sudden, requesting an IP, cos it just rebooted.
anyone else got any other suggestions?
Aside from some people going to modem, and some people doing WIRNS without DNNA data, i got nothing. Can anyone do these?
*1 - Here's an idea... Hub a replay, replay, and computer. that's it. No internet. See if the ****ers crash. I'll do this tomorrow!
Hey, i just realised. It isn't the fault of funky guide data. If it were guide data, then pulling the network connection out of the box wouldn't fix the problem.