A few weeks ago I bought an xbox one s, primarily to play system link stuff with my kids (xbox one bc + xbox 360). The two machines connected through the asus ac68r, but they wouldn't stay connected. I was experiencing buffering and connection drops, as if we were playing online but we weren't (none of us has xbl gold), and yes we were very careful to select local/system link play. In each and every case the xbox one s whether hosting or not would be the one to drop connection, from the game as well as it's backround connection to xbl. This sent me down a now week or so long journey of crap.
I started by checking router settings. When I did this I was notified of a firmware update, so I let it update hoping maybe this was the reason. After the update I went back to the xbox's to test, no deal same problem, spotty connection, buffer, disconnect. Tried one wired the other wifi, both wifi, both wired, same results. Started thinking my shiny new book end (xbox one s) was defective. Rigged up a crossover cable and what do you know.....perfect game night, all was well. But this irked me that my near $300 router couldn't do what my home made crossover cable could.
So I started running speed tests. All of my wifi clients were getting the max possible speed (with respect to each devices inherent max potential). However! All of my wired clients were only getting 3down and 3up. My QoS was set to traditional. While is was discovering this I was hit with another firmware update message, so I let it. Thinking this update might fix the problem I re-ran all the same tests. Same results, wifi clients good to go, wired clients completely crippled. Next I changed QoS from traditional to adaptive. Guess what? Wired speeds were now corrected, BUT, all the wifi clients were crippled and in some clients cases as much as down into the kbs.
Next came the thought that maybe switching to Merlins fw might help. Nope same 'mysterious' problems, adaptive QoS=crippled wireless clients, traditional QoS=crippled wired clients. I began to think, something somewhere is......backwards, or something. Then I came across this post.
Guess what? Are we surprised? When I switched back to traditional QoS and did as Zodler here suggested.....yeah man....you got it everything works correctly now. So, either QoS code is borked, the UI is borked, or the code which connects the QoS to the UI is borked or all of the above.
I seriously hate signing up for forums and joining gangs and all that sort of stuff, but in this case I just had to make an exception. This issue so insanely stupidly simple, likely easily repaired, should never have gone un-noticed, and is super critically debilitating to the network that it absolutely must be fixed. People with less patience, time, and inclination who are hit with the problems I have experienced on this journey will likely conclude that their asus router is junk and switch brands when all along it was a simple screwup that asus could definitely fix!
I have no idea if this will resolve my xbox system link issue, I'll test later and update my post with results.
Can someone with some sort of clout over at asus please draw their attention to this.
Hey Zodler, thank you so much!!!
