xbox 360 not connecting wirelessly

[freemanmo]

I have problem to connect xbox to TP-Link WDR4300 too, but a interest thing is when I used my old wireless N router with stock firmware as a repeater, xbox immediately connected to network.

[pmerrill]

In order to track this problem down, is there anyway to see that actual packets that are being sent from the xBox to the 4300 router? If one cannot turn on debugging, is there another program one can run?

[ChadW]

Any update on this issue? I found the following older post which might address it but I just flashed back to sock firmware on my TPLink WDR4300 to get my xbox up and running again. Anyone know if this works?

http://www.gargoyle-router.com/phpbb/vi ... f=6&t=1213

[pmerrill]

It's got nothing to do with the DNS, I'm reasonably certain it's a problem with OpenWRT driver in AA 12.09. I'm preety sure it works ok with Gargoyle Stable 1.4.7.

We all will just have to wait until the next release of OpenWRT and the next release of Gargoyle to fix the problem.

Does anyone know when to expect 1.5.10 or will be be 1.6.0?

[manwinder]

i am also having the problem with the tp-link wdr4300 with a xbox 360 slim. i have tried everything, setting the ip to 192.168.0.1 like before, dns changes, static ip, upnp, port forwarding, it always sets my ip to something werid like 169.xxx.182.46, dns is left blank. also if i go manual settings it still doesn't work. it does show up on the routers page under status but never connects, ethernet works perfectly. All the other wireless computers and devices work flawlessly. But my brother should be fine using an ethernet cable (since we have a 100 foot one just for this ) but it would be nice to use wireless. i tried fixing it for a out 3 hours, no luck. But i do love the fw its sick, thanks
ps i am running 1.5.9

[ChadW]

FYI: If you're willing to live with it (until a fix comes out), switching bandwidth to B+G worked for me.

[pmerrill]

FYI: If you're willing to live with it (until a fix comes out), switching bandwidth to B+G worked for me.

Agreed, that works fine but you loose wireless N naturally. It was too ugh for me, so I went back to wireless N. I am now just waiting for the next OpenWRT release to have hopefully "fixed" the problem.

[pmerrill]

Bump...any movement on this for the tp-link 4300? Is anyone able to connect with wireless n turned on yet?

[manwinder]

Bump

[manwinder]

BUMP
any updates on this maybe openwrt update