OK then....
So what other probables are we left with? Looking for a root cause analysis here, with limited information...and suspect information...have to base the analysis on info provided. Could very well be misinformation or misinterpretation. There are bugs. They happen.
My point stands, if the iphone is truly sending these requests then it's a bug in the phone.
THAT'S THE BIG "IF". IF the trace was interpreted correctly.
There are only a few instances that I can think of where this could happen....
1) client truly is freaking out and sending all these arps
2) duke doesn't know how to read a trace
3) blah
Most always it is the client when it comes to wireless. Also known as "it's not a network problem".
The root of this analysis is the interpretation of the trace.
Slashdot Mirror
OK then.... So what other probables are we left with? Looking for a root cause analysis here, with limited information...and suspect information...have to base the analysis on info provided. Could very well be misinformation or misinterpretation. There are bugs. They happen. My point stands, if the iphone is truly sending these requests then it's a bug in the phone. THAT'S THE BIG "IF". IF the trace was interpreted correctly. There are only a few instances that I can think of where this could happen.... 1) client truly is freaking out and sending all these arps 2) duke doesn't know how to read a trace 3) blah Most always it is the client when it comes to wireless. Also known as "it's not a network problem". The root of this analysis is the interpretation of the trace.