This is pretty much correct. I’ve done quite a bit of wireless engineering for both indoor/outdoor wifi, and long distance wireless backhauls.
Even in a completely noise-free environment, wifi is a serial, half-duplex technology. It cycles through each attached device in turn, gives them a chance to talk, then goes back through and talks to them. I believe the baseline ping in a perfect environment is 15ms or 20ms for the cheaper access points, and that is JUST from your device to the AP. I’ve seen better ones where the baseline is 3ms - but keep in mind that I haven’t done the research in a good long while.
So to say it doesn’t matter isn’t 100% accurate. What matters more is the noise environment that your wifi setup is installed in, and more critically - how is your connection from your demarc (usually a dsl/cable modem) to your provider’s backbone drain? I keep a performance monitor on mine, and it fluctuates pretty wildly at times - but in most situations I have 30ms or less to the backbone drain, and I’ve got all of my consoles hard-wired to my firewall. Only my laptops and my iPhone are wifi. Basically anything that has to be “Just In Time” on traffic should be hardwired whenever possible.
ALSO - if you’re serious about online play, ditch your commercial router and upgrade to something a bit more hardcore, like pfSense:
At one point in time, I had 6 pieces of hardware sitting around that I’d intended to sell, but literally any PC made in the last 5 years would do the trick. This is what I use, and I have it shaping all traffic in and out of my home. If it’s JiT, it gets top priority. So XBL, SIP, and Video Conferencing all get top priority, followed by SSH, with HTTP/HTTPS/FTP on another tier, and finally all P2P filesharing coming dead last. That doesn’t mean my P2P sucks, it just means that if I’m online playing a game, P2P takes a back seat to my game, and when my game is done, so long as no one is on a VOIP call or browsing the web, my P2P stuff can go nuts. Best of all, when properly configured, pfSense’s NAT implementation shows up as “Open” to XBL as opposed to “Moderate”, which even Linux’s NAT implementation shows up as. Some seriously rock-solid connectivity.
So if you want a top notch online game, the following things you want are:
-
A LOCAL DSL provider. One where if you had to, you could get the owner on the phone. Make sure you get a business-class connection with no filtering, and no firewalling upstream. DO NOT GET CABLE. I could give a whole dissertation on this, but if you’re on cable, everything else I tell you is moot depending on what your neighbors are doing. DO NOT write me off as being biased on this point. If you want a T-1 or fiber, those are decent options too, but if you’re serious about online gaming, cable will be the end of you.
-
A decent firewall with a top-notch NAT implementation, or a static IP address for your console (translation: fork over more cash to the ISP). pfSense is my personal favorite, and I’ve yet to see a better performer for the price.
-
Hard wire your consoles. Doesn’t matter if it’s 10-Base-T, 100, or 1000, but it needs to be full duplex, and hooked to a decent store and forward switch. If it’s doing cut-through at the switch, pitch it and spend the $20 it takes to get a store and forward switch. Wifi, to be blunt, just introduces too many variables.
-
Test your cables. Borrow a cable tester if you have to, since they cost about $60, but test each cable end-to-end. Just because you get connected doesn’t mean a cable isn’t damaged - it just means that error correction is taking over and doing it’s job. You waste precious ms on error correction.
-
Realize that even with the above, several factors remain outside your control. Even with the awesome NAT implementation that pfSense has, I find myself having to reboot my 360 sometimes in order to get a decent ping to specific opponents on XBL. The reasons for this can be one of many - poor matchmaking algorhythms at MS, poorly chosen routes (which can possibly be flushed by turning off your 360, flushing the states table in pfSense and then turning your 360 back on), and heck - even magical fairie pixie dust might have something to do with it. Also, if any provider between you, MS, and then MS and your opponent, and eventually between you and your opponent if the game is configured to run matches P2P is having problems, YOU are going to have problems. The only thing you can do is watch online network advisories, OR do what I told you in step one and get a local DSL provider that actually might care about such issues and fix them.
That’s about it. You can use wifi, but it has nothing to do with being a scrub if you believe wifi might impact match quality. It can and does. I am a certified network engineer, and I approve of this message.