You say that with some authority, so I'll bite. I remain a bit skeptical, since by definition it's the router deciding to restart rather than an individual client dropping out, and since it's still doing it even though auto switching is turned off. It seeems a little silly to restart the entire wireless service if its going to run on the same danged channel, but..... I don't know if you have any pull with the product guys, but it would be nice to have a little more specific message - if it detects interference, maybe it could say that...
Question 1: In your opinion, is there any reason to believe that 1.31 will behave differently than 1.21 with regards to wireless restarts, given that there's no mention in the release notes? The notes themselves are pretty thin, so I could believe there are a number of additional issues and things that got tweaked, but I was hoping to be a bit more scientific about this than the current "try it and see" approach, especially when there's no way to go back.
Question 2: Assuming it is being caused by interference, is there a more scientific way to narrow down the problem? I've tried temporarily moving the router so it's in the middle of the floor, I've tried playing with the antenna orientation, and obviously support had me switch off channel switching. It seems like short of turning off every piece of equipment I own one by one, not to mention equipment owned by my neighbors, then trying every possible physical location for the router, I don't know how to tell what the channel setting or physical placement should be. I've had many, many B/G routers over the years and never had a problem. Perhaps none of them were smart enough to sense interference before, perhaps it is related to the new location which is more central in my house. Regardless, it seems like a daunting task to narrow this down without any clue as to whether interference is even the issue!