Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[v0idi]

EDIT/NOTE: Everything has worked reasonably fine after resetting to factory settings and then updating the firmware to 1.20EU.

Hello everyone,

I recently bought a new DIR-655 router to replace my old, cheap Linksys one. Now I am having difficulties connecting to Xbox Live 360 - or more precisely, staying connected to it. My Xbox successfully connects to Live, and everything seems okay if I run the network test; After a couple of seconds (3-15 so far), however, I get disconnected again. This did not happen with the previous router - everything worked just fine without any changes to the settings (with NAT and no port forwarding at all.)

The firmware I'm using is old, yes, but the newest one has a terrible lag in DNS resolution and I'd rather use DNS relay than manually configure the DNS servers for all of the computers on my LAN as well as visiting wireless devices. And yes, I have noticed other people have been encountering problems with Live, too, but decided to post since nobody else seemed to have run into these problems with these versions of the firmware and the device.

My setup is fairly simple: I'm connected to the local university network, so I get an ethernet connection straight out of the wall - no modem needed. My DIR-655 WAN port is connected to the wall, and my Xbox is connected to one of the LAN ports. The cable is connected just fine as well - I did check, mind you. ;)
There are a couple of computers hooked up to the router as well, and they are functioning perfectly fine, but I think that should not be relevant.

I also have NAT and the SPI firewall enabled, while UPnP being disabled. I tried turning off the firewall, enabling UPnP and deactivating the filters on TCP/UDP connections, but none of these helped. I also tried forwarding the ports specified to be used by Live to the Xbox - which of course has a static-ish IP address (DHCP reservation) - but opening those ports didn't help either.

Furthermore, there do not seem to be any log entries that would appear to be related to Live, only some ICMP packets being dropped from nonexistent connections to China and such :)

As a sidenote, I originally upgraded the firmware to 1.21, then downgraded it again and built the settings from scratch.

Has anybody encountered a problem like this and solved it or should I just wait for a new firmware version which could fix the DNS relay issues and maybe this as well?

Thank you in advance,
 -v0idi


EDIT: Oops, I didn't notice there was a child board for european models.
EDIT2: No ideas? Looks as though I'll have to try upgrading/downgrading the firmware and resetting the settings again. >:/

[Lupismaximus]

I am using 1.21 and recently experienced the same problem.  I turned off the XBOX LIVe port forwarding, and it worked like a charm.

[v0idi]

Thanks for the tip! :)

I tried upgrading and dowgrading the firmware yesterday, too, but the results were somewhat confusing:
1.11: Doesn't work at all
1.11 -> 1.20: Works perfectly
1.20 -> 1.21: Doesn't work, and DNS relaying is sluggish
1.21 -> 1.20: Doesn't work.
1.20 -> 1.11: Doesn't work.
1.11 -> 1.20: Works again

Oddly, Live worked only when I upgraded the FW from 1.11 to 1.20. Settings were reset to factory defaults after each attempt and not configured further.

Looks like I'm staying at 1.20 until the DNS relay problems are solved. I'm getting some DNS resolution delays with this version, too, but I'll still have to investigate some more.

[EddieZ]

Possibly Dlink tech need to look at the part of the firmware updater. It seems that the 'cleaning up' procedure before flashing the new firmware leaves some old code intact or messed up. I've seen this happen before with BIOS firmware. It's just a hunch, but I would not be suprised.

[v0idi]

That certainly sounds likely.

I also noticed that the DNS resolution delays are at least in my case related to IPv6 address resolutions:
The client first does an DNS AAAA request for an IPv6 address, to which there is a standard answer without a resolved address (since the server doesn't have one available). After that, the client tries again with the local domain name appended, but the router doesn't answer with "No such name" (which it should since the name does not exist), so the client waits 5 seconds, tries again, and waits 5 seconds again. After timeouting enough times, the client tries again with an A request, which is then answered.

Annoying.

I think I'll post these results to the sticky DNS thread, too, if Lycan or someone else doesn't pick up on this soon enough.

[Lycan]

are these packet captures being done from Vista? or XP?

[v0idi]

Ubuntu x64. :) The same thing happens with Windows XP Pro 64bit, too.
Most applications do run fine, though, since they don't seem to be making AAAA requests; only the IPv4 A kind.

[Lycan]

hmm. i'd love a copy of the capture from the XP, (if i use ubuntu PM will say it's not vaild). If you don't have one I can grab one myself.

[v0idi]

Interestingly enough, after installing Wireshark and the PCAP service, the delay isn't there anymore on either of my Windows XP machines. Or maybe it's just the fact that it's 3 am over here
The same problem still persists on Ubuntu, though, and I can reproduce it every time.

I'll take look at this again tomorrow.

[funchords]

The firmware I'm using is old, yes, but the newest one has a terrible lag in DNS resolution and I'd rather use DNS relay than manually configure the DNS servers for all of the computers on my LAN as well as visiting wireless devices.

With FW 1.21, if you disable QOS Engine's Uplink Automatic Speed detection (and set a manual value), then your ISPs DNS servers will be sent to your clients (you won't need to manually configure the DNS servers).

[EddieZ]

With FW 1.21, if you disable QOS Engine's Uplink Automatic Speed detection (and set a manual value), then your ISPs DNS servers will be sent to your clients (you won't need to manually configure the DNS servers).

Well, it also does so with the QOS Engine's Uplink Automatic Speed detection setting enabled...or am I missing your point here?

[Lycan]

My point was he was referencing a IPv6 AAAA record look up, to my knowledge Xp shouldn't make those types of lookup attempts. Thats why the Ubuntu capture is useless for me. I need to see XP make the same attempt. That being said I could understand if ONLY Vista machines were suffering from the DNS lag issue (it would support his theory of the AAAA record lookup), but XP's are suffering as well.
Unless I'm missing something.........(which I'm known to do  )

[war59312]

You can install IPv6 on XP which would then do AAAA record lookups. Vista merely comes with it pre-installed.

[Lycan]

That again proves my point, we're seeing this on XP machines that DO NOT have IPv6 support.

[v0idi]

I'm afraid I haven't been able to reproduce the issues on the XP machine (yet) after installing Wireshark and WinPcap. Even the Xbox live problems I originally moaned about seem to be gone at the moment, so I'm somewhat reluctant to try to do anything about the issues at the moment since everything appears to finally run reasonably smoothly.

If I do experience the same delays again, I'll try to get a packet capture up, though it might require a little tinkering with a hub or a second wireless device for that to work in case WinPcap circumvents the problems.

Regardless, happy new year to you all and thanks for the help so far. ^__^